Clarify feature requests into implementation-plan.md and tasks.md.
npx skills add https://github.com/DIO0550/d-market --skill spec-driven-dev-dio0550
Please help me install this Agent Skill. Skill: spec-driven-dev Source: https://github.com/DIO0550/d-market/tree/main/plugins/spec-plugin/skills/spec-driven-dev Command: npx skills add https://github.com/DIO0550/d-market --skill spec-driven-dev-dio0550
This skill helps teams convert vague feature requests into precise specifications and a clear development plan, reducing miscommunication and rework.
Describe the feature you want to implement and the skill will generate an implementation-plan.md and tasks.md.
High-intent search queries and answers about installing and using this skill.
To convert vague feature requests into an implementation plan, use interactive requirements elicitation to clarify scope and acceptance criteria. This process generates a formal implementation-plan.md containing system diagrams and a verification plan.
Creating a traceable tasks list for software development involves defining constraints and acceptance criteria from feature requests. This generates a tasks.md file to guide the development workflow, track progress, and enable staged reviews.
Interactive specifications improve the software development workflow by applying elicitation to define precise scope, reducing miscommunication and rework. This produces actionable plans and staged tasks for guiding development and reviews.
Yes, you can generate state machine and data flow diagrams during requirements planning. The elicitation workflow produces an implementation-plan.md file that includes these system diagrams alongside a comprehensive verification plan.
Spec-driven planning works with automated code review processes by generating an implementation-plan.md and tasks.md. These files enable Codex reviews and establish a traceable, staged development workflow for validating implementation against specifications.
You need formal acceptance criteria before starting implementation to clarify ambiguous feature requests into concrete specifications. Defining these constraints upfront reduces miscommunication and rework by guiding planning and staged reviews.
cshyangPlan and execute a project discovery phase to define requirements and scope.
lofidonut3Execute Speckit implementation tasks from tasks.md using a TDD workflow.
elijahmurrayCheck out pull request branches, review code changes, and apply feedback.
iqbal125Scaffold apps and libraries in an Nx workspace using generators.
