Writes behavior specifications with acceptance criteria for spec-driven development changes.
npx skills add https://github.com/nico0695/ai-tools --skill sdd-spec-nico0695
Please help me install this Agent Skill. Skill: sdd-spec Source: https://github.com/nico0695/ai-tools/tree/main/sdd/sdd-v2/skills/sdd-spec Command: npx skills add https://github.com/nico0695/ai-tools --skill sdd-spec-nico0695
spec.md covering change summary, in-scope behavior, acceptance criteria, non-goals, edge cases, and verification targets. - SDD v2 workflow integration: Reads proposal.md, explore.md, and state.yaml from an openspec change directory and updates the change state, with rules for running in parallel with the design phase. - Objective-aware guidance: Adapts spec depth for new features, bug fixes, refactors, and planner-style changes, with a quality bar requiring verifiable acceptance criteria. - Use Case: After approving a proposal for a new API rate-limiting feature, run this phase to generate a spec.md that defines exact expected behavior, regression expectations, and non-goals before any design or implementation begins. ## Quick Start Run the sdd-spec phase for the current openspec change to generate a behavior specification with acceptance criteria from the existing proposal.High-intent search queries and answers about installing and using this skill.
Start from the approved proposal, define what the change must do and what success looks like, then capture specific acceptance criteria, non-goals, and edge cases. Keep the spec implementation-agnostic so later verification can audit behavior against it.
A spec defines behavior, scope, and acceptance criteria without internal implementation detail, while a design doc covers technical choices. This phase explicitly avoids devolving into a design doc or task list.
Yes, the spec phase may run in parallel with the design phase once proposal.md exists. If a design already exists, keep the spec behavioral and do not rewrite technical choices unless the proposal itself changed.
Use blocked when acceptance criteria cannot be defined safely without a user checkpoint. Use partial when the spec is usable but still needs one or more behavioral decisions resolved.
Yes, but scoped to the fix: define the corrected behavior and regression expectations. For refactors, keep the spec light but explicit when behavior must remain stable.
NSObjectsCapture change intent, scope boundaries, and success criteria in a proposal document.
josephneumannVerify implementation, run quality gates, update documentation, and close a beads task.
scanadyDesign behavioral nudges using choice architecture and dual-process theory.
jacksonlee-twDecomposes specifications into ordered, verifiable implementation tasks with acceptance criteria.