Create structured SDD-lite spec.md files defining WHAT, WHY, and success criteria.
npx skills add https://github.com/rodacato/kwik-e-dev --skill sdd-spec-rodacato
Please help me install this Agent Skill. Skill: sdd-spec Source: https://github.com/rodacato/kwik-e-dev/tree/main/plugins/lifecycle/skills/sdd-spec Command: npx skills add https://github.com/rodacato/kwik-e-dev --skill sdd-spec-rodacato
SDD-lite step 1 writes docs/sdd/<change-name>/spec.md describing WHAT we're building, WHY, and how we'll know it's done. It establishes the first artifact in the spec → plan → tasks → apply → verify chain and is intended for substantial changes where scope or success criteria are unclear or stakeholders disagree about what "done" looks like.
Create docs/sdd/<change-name>/spec.md and begin drafting the Step 1 spec using the provided template.
High-intent search queries and answers about installing and using this skill.
Drafting a structured spec defines WHAT, WHY, and success criteria before implementation. It captures project scope and stakeholder alignment by creating a formal spec.md document to drive subsequent planning and execution.
A formal specification is needed for substantial changes with unclear scope or when stakeholders disagree on what done looks like. It establishes discovery details and open questions before any design or coding work begins.
Create a spec document by placing a spec.md file inside the docs/sdd directory. Use a defined template covering discovery, open questions, and references to guide iterative refinement through a structured drafting and review workflow.
Managing scope and success criteria is best handled by writing a structured SDD-lite spec. It captures the WHAT and HOW WE WILL KNOW details early, ensuring stakeholders agree on completion metrics before planning or coding starts.
Yes, the spec template supports iterative refinement through a structured discovery, draft spec, and review workflow. It allows you to continuously update open questions and references as project scope becomes clearer.
A formal spec document should not be used for minor changes with clear scope. It is specifically designed for substantial changes requiring stakeholder alignment, meaning trivial updates do not need this level of formal documentation.
Owl-ListenerSynthesize discovery and research into stakeholder-aligned strategic documents with experience maps and metrics.
nirukk52Automate ScreenGraph end-to-end UI validation with Playwright and .env configuration.
Ibrahim-3dDefine and maintain project context artifacts in product.md, tech-stack.md, and workflow.md.
Andy-HNUCapture and organize product requirements into actionable PRDs.
