sdd
Installation
SKILL.md
SDD Skill
Manage development progress for solo and delegated work: track the active spec, current stage, completed and remaining deliverables, blockers, verification evidence, and next action. Use the project's existing spec/task artifacts as the source of implementation progress, with concise status in the SDD log; do not create a second competing task list.
Ownership
- The project spec tool owns spec authoring, implementation mechanics, archive, and merge.
sddtracks progress and ensures each next stage's conditions are met, including arranging missing tests and fixes within the authorized task. - The current agent performs authorized work directly.
delegate, when available, governs handing a bounded job to another agent. A delegated agent returns unresolved decisions and any need for further agents to the agent that briefed it rather than starting its own dispatch tree. Neither skill requires the other. - For issue-linked work, check at meaningful stage checkpoints and before closeout whether the issue's state still reflects the result and next action; leave an accurate state unchanged. Use
issue-trackingwhen available or the project's existing tracking workflow for warranted, authorized updates, passing stage results, blockers, remaining work, and evidence links to the tracking owner. Keep verification details in the SDD log and link the primary issue; do not duplicate its task list or equate spec archival with tracker completion. If synchronization is unavailable, retain any needed update in the existing handoff record and disclose the gap. - For features and behavior changes, use
bddduring planning/spec formulation and carry its agreed scenarios into implementation and acceptance. BDD owns scenario quality, current.featurescenarios in the deterministic workflow, and scenario-to-test correspondence; the spec tool owns requirement intent/change history. SDD checks readiness using those artifacts and evidence, without copying scenarios into its task list. When the BDD reference is available, follow BDD contract/adoption boundaries, including legacy migration and OpenSpec compatibility limits. Pure refactors reuse behavior-preservation evidence; editorial changes do not need new scenario discovery. - Without
bddor its reference, use agreed existing spec scenarios in legacy projects. For new executable BDD acceptance and existing feature-driven projects, scenario-evidenced requirements default to versioned feature/bindings consumed directly or through deterministic generation, without model scenario translation or binding supply. A missing path or required unexecuted cases remain gaps; do not auto-install the skill or silently downgrade required deterministic acceptance.
Stages
spec-tool: design / proposal / plan → layout check → grill
spec-tool: implement / apply → test (blocking)
spec-tool: archive / merge-spec → review