agentsclimarketplace
Sign in

Sdd draft design

Skill andresnator/agents-orchestrator/skills/sdd-draft-design

Trigger: draft design, borrador de diseño, SDD design interview. Explore the codebase, interview, then draft design.md; plan-only, write on approval.From its SKILL.md

Install
npx -y skills add andresnator/agents-orchestrator --skill sdd-draft-design

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.0 KB, 577 tokens by cl100k_base, as published. Nobody here has run it

Activation Contract

Use when drafting an OpenSpec design.md after proposal/spec context exists or when technical uncertainty must be resolved for SDD planning.

Hard Rules

  • MUST explore the real codebase read-only before technical questions or drafting; never guess architecture.
  • Follow the grilling skill: one question at a time, recommendation attached, stop and wait; read code for technical answers when possible.
  • Follow the native-question-ux skill for question presentation; ask one question at a time and stop after each answer.
  • Artifacts default to English; interview/summaries/gates use the user's language.
  • Plan-only: no code edits, builds, installs, tests, or state changes. Only write planning .md files after explicit approval.
  • File Changes entries must name a real file path or Create. No code bodies. Enough precision for the implementer to execute without re-deciding. Keep under 800 words.
  • When delegated by grill, return the approved draft and do not write files; the orchestrator owns the single write step.

Decision Gates

SituationAction
Technical answer is in codeRead code, then answer; do not ask.
Multiple viable approachesPresent both with tradeoffs, recommend one, and record a Decision.
Design conflicts with proposal/specSurface the conflict and resolve before drafting.
Unknown remains after explorationPut it in Open Questions; do not guess.
File path not foundUse Create only for new files; otherwise re-check.

Execution Steps

  1. Read assets/design-template.md and references/question-bank.md.
  2. Read proposal/specs if present.
  3. Silently explore affected code, patterns, interfaces, and tests read-only.
  4. Interview only for non-discoverable technical decisions.
  5. Draft design with stack & conventions (language/tool versions with evidence, code-conventions deviations), approach, decisions, data flow, file changes, contracts, tests, rollout, and open questions.
  6. Present for approval; revise until approved.
  7. If standalone and approved, ask before writing .ai/orchestrator/changes/{change-name}/design.md.

Output Contract

Return approved/unapproved status, design draft, explored evidence, decisions, unresolved questions, and write recommendation. If a referenced skill cannot be resolved by name in the current runtime, say so instead of silently continuing.

References

  • assets/design-template.md
  • references/question-bank.md
  • grilling skill
  • native-question-ux skill

Attribution

Inspired by Matt Pocock's grilling skills at https://github.com/mattpocock/skills; adapted for OpenSpec design drafting.

What ships with it: 2 files

2.1 KB alongside SKILL.md

assets/

references/

Keep looking

Skills are one crate of 326,512. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.