agentsclimarketplace

Sdd draft spec

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

Trigger: draft spec, borrador de spec, SDD delta spec interview. Interview, then draft delta specs with scenarios; plan-only, write on approval.From its SKILL.md

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

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, 600 tokens by cl100k_base, as published. Nobody here has run it

Activation Contract

Use when drafting OpenSpec capability specs from an approved proposal or direct SDD behavior interview.

Hard Rules

  • Follow the grilling skill: one question at a time, recommendation attached, stop and wait; read discoverable proposal/spec context first.
  • 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: read-only codebase access; no code edits, builds, installs, tests, or state changes. Only write planning .md files after explicit approval.
  • One file per capability: specs/{capability}/spec.md. In .ai/orchestrator/changes/, new and modified capabilities both use delta sections; new behavior goes under ADDED Requirements.
  • Requirements use RFC 2119; scenarios use WHEN/THEN. Describe WHAT, not HOW. Keep under 650 words per domain.
  • When delegated by grill, return the approved draft and do not write files; the orchestrator owns the single write step.

Decision Gates

SituationAction
Standalone and proposal exists on diskRead it first.
No proposalInterview directly or offer to run proposal drafting first.
Implementation detail appearsPark it as a design note; keep spec behavioral.
Existing requirement changesUse MODIFIED and restate the whole requirement.
Requirement removed or renamedInclude Reason and Migration.

Execution Steps

  1. Read assets/delta-spec-template.md, assets/capability-spec-template.md, references/question-bank.md, and references/delta-semantics.md as needed.
  2. Build the capability list from proposal Capabilities or interview.
  3. For each capability, draft an OpenSpec change delta; use ADDED for new capability behavior and MODIFIED only for replacement behavior.
  4. Interview for observable requirements, scenarios, edge cases, removals, and renames.
  5. Present each spec or batch for approval; revise until approved.
  6. If standalone and approved, ask before writing .ai/orchestrator/changes/{change-name}/specs/{capability}/spec.md.

Output Contract

Return approved/unapproved status, capability files, spec drafts, parked design notes, and open questions. If a referenced skill cannot be resolved by name in the current runtime, say so instead of silently continuing.

References

  • assets/delta-spec-template.md
  • assets/capability-spec-template.md
  • references/question-bank.md
  • references/delta-semantics.md
  • grilling skill
  • native-question-ux skill

Attribution

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

What ships with it: 4 files

2.9 KB alongside SKILL.md

Keep looking

Skills are one crate of 611,178. 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.