Orchestrate a 10-phase 5D Spec-Driven Development workflow producing PLAN.md, SPEC.md, and a Task List.
npx skills add https://github.com/tapania/5d-skills --skill 5d-sdd
Please help me install this Agent Skill. Skill: 5d-sdd Source: https://github.com/tapania/5d-skills/tree/main/skills/5d-sdd Command: npx skills add https://github.com/tapania/5d-skills --skill 5d-sdd
This Skill orchestrates a complete 5D Spec-Driven Development workflow to prevent wasted effort by ensuring understanding before commitment at every level, guiding teams through structured phases from orientation to reflection.
Start ORIENT to map the space, then SPAR to challenge assumptions, followed by PLAN, REFINE, SPEC, GAP ANALYSIS, TASKS, BUILD, VERIFY, and finally REFLECT.
High-intent search queries and answers about installing and using this skill.
5D spec-driven development is a structured workflow that ensures understanding before commitment across ten phases, from orientation to reflection. You need it for complex new features or initiatives requiring rigorous analysis to prevent wasted effort and rework.
To orchestrate spec-driven development, start with ORIENT to map the space, then progress through SPAR, PLAN, REFINE, SPEC, GAP ANALYSIS, TASKS, BUILD, VERIFY, and REFLECT. This sequence enforces explicit exit criteria and multi-quadrant checks for traceability.
Structured spec-driven development produces artifacts like PLAN.md, SPEC.md, and a sequenced Task List. These outputs satisfy documentation and governance needs by capturing alignment and traceability throughout product evolution.
Yes, 5D spec-driven development is designed for complex initiatives requiring structured analysis. It includes a dedicated GAP ANALYSIS phase to identify coverage gaps between specifications and planned tasks before the build phase begins.
The best way to reduce rework risk is using a spec-driven development workflow that enforces clear exit criteria across ten phases. Challenging assumptions during the SPAR phase and refining plans before specification prevents wasted effort.
You should avoid a ten-phase spec-driven development workflow for simple tasks that do not require structured analysis or multi-quadrant alignment checks. The full orchestration loop is intended for complex initiatives needing rigorous documentation and governance.
cshyangPlan and execute a project discovery phase to define requirements and scope.
caiohbfurtadoConvert PRDs and tech specs into sequenced frontend implementation tasks.
az9713Merge pull requests, deploy code, and verify production health.
YH-05Create project directories, documentation, and GitHub project boards.
