Generates a detailed system specification from a project's scope and README files.
npx skills add https://github.com/zabuuq/sdd-plugin --skill spec-zabuuq
Please help me install this Agent Skill. Skill: spec Source: https://github.com/zabuuq/sdd-plugin/tree/main/plugins/sdd/skills/spec Command: npx skills add https://github.com/zabuuq/sdd-plugin --skill spec-zabuuq
This Skill turns your PRD and scope into a detailed, architecture-grade technical specification that reduces ambiguity and accelerates implementation.
##/### sections so downstream sprint planning can load the right context.docs/spec.md, and updates or creates CLAUDE.md and AGENTS.md so agents have stable project instructions.Run the command /sdd:spec after you have created docs/scope.md and docs/prd.md, and answer the single-question interview prompts to produce docs/spec.md.
High-intent search queries and answers about installing and using this skill.
To convert a PRD into a technical specification, you load existing project scope and PRD files, run a guided multi-step interview, and generate a structured spec document covering architecture, data models, and deployment guidance.
Spec-driven development maps architecture to PRD epics by proposing each technical component with specific interfaces, contracts, and data shapes matched to the corresponding epic requirements in the generated specification.
To generate a buildable technical specification, you need to create your project scope and PRD markdown files first, then execute the generation command and answer single-question interview prompts to refine the output.
Yes, the workflow updates or creates CLAUDE.md and AGENTS.md alongside the main specification document, ensuring that downstream agents have stable, cross-referenced project instructions for subsequent build steps.
Technical specification generation requires a guided multi-step interview to deepen context through successive rounds, ensuring the final architecture, file structure, and data models precisely reflect the project scope and reduce ambiguity.
The best way to structure documentation for sprint planning is to generate deeply nested section headers with granular component subsections and documentation URLs, allowing context loading for specific build tasks.
JotJuniorConduct structured discovery interviews to capture project context into briefing documents.
AimeerrhythmCreate risk-aware implementation plans from specs with ECW domain context.
luongnv89Generate and audit CLAUDE.md and AGENTS.md configuration files.
sunnypatneediDecompose a feature into system components with interfaces and data flows.