Sdd draft proposal

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

Install

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

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 author says it does

Copied from the file, not written here

Trigger: draft proposal, borrador de propuesta, SDD proposal interview. Interview, then draft an OpenSpec proposal.md; plan-only, write on approval.

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

2.5 KB, 484 tokens by cl100k_base, as published. Nobody here has run it

Activation Contract

Use when drafting an OpenSpec proposal.md through interview-first SDD planning, either standalone or delegated by grill.

Hard Rules

Follow the grilling skill: one question at a time, recommendation attached, stop and wait; explore discoverable answers instead of asking.
Follow the native-question-ux skill for question presentation; ask one question at a time and stop after each answer.
Interview/summaries/gates use the user's language; artifacts default to English unless Spanish artifacts are explicitly requested.
Plan-only: read-only codebase access; no code edits, builds, installs, tests, or state-changing commands. Only write planning .md files after explicit approval.
When delegated by grill, return the approved draft and do not write files; the orchestrator owns the single write step.

Decision Gates

Situation	Action
Standalone and no change name	Propose a kebab-case, verb-led name and confirm.
Answer is discoverable from repo/docs	Explore read-only instead of asking.
Scope or capability list changes	Restate the new scope/capability binding and reconfirm.
Proposal exceeds 450 words	Compress before approval.

Execution Steps

Load the template in assets/proposal-template.md and relevant prompts from references/question-bank.md.
Interview for problem, users, business rules, scope, risks, success, and capability binding.
Draft proposal.md with New/Modified Capabilities as the spec contract.
Present the draft for approval; revise until approved.
If standalone and approved, ask before writing under .ai/orchestrator/changes/{change-name}/proposal.md.

Output Contract

Return change name, approved/unapproved status, proposal draft, capability binding, write recommendation, and open questions. If a referenced skill cannot be resolved by name in the current runtime, say so instead of silently continuing.

References

assets/proposal-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 proposal drafting.