spec-driven-development
A structured framework for software development that mandates the creation of a specification document before writing code. It enforces a four-phase gated workflow: Specify, Plan, Tasks, and Implement, requiring human validation at each stage.
Is spec-driven-development safe to install?
Review before installing: our audit of spec-driven-development's source files found 0 shell commands, 0 external URLs, file reads and writes (medium risk). Every command and URL listed appears verbatim in the skill's source. The skill requires reading and writing files to the local repository, specifically creating and updating specification documents and task lists in the tasks/ directory.
How we audit skills: our security review methodology.
Who is this skill for?
Software engineers and AI agents working on projects, features, or architectural changes where requirements are ambiguous or complex.
What can you do with it?
- Starting a new project or feature
- Clarifying ambiguous or incomplete requirements
- Managing changes that touch multiple files or modules
- Documenting architectural decisions
- Executing tasks that require more than 30 minutes of implementation time
How good is this skill?
Quality score: 5/10. The skill provides a clear, actionable, and disciplined methodology for software development. It includes specific templates and a gated workflow that effectively reduces ambiguity.
What does the skill file contain?
# Spec-Driven Development ## Overview Write a structured specification before writing any code. The spec is the shared source of truth between you and the human engineer — it defines what we're building, why, and how we'll know it's done. Code without a spec is guessing. ## When to Use - Starting a new project or feature - Requirements are ambiguous or incomplete - The change touches multiple files or modules - You're about to make an architectural decision - The task would take more than 30 minutes to implement **When NOT to use:** Single-line fixes, typo corrections, or changes where re...
Frequently asked questions
When should I skip using this skill?
Do not use this skill for single-line fixes, typo corrections, or tasks where requirements are unambiguous and self-contained.
Where should I save the generated plan and task list?
Save the plan to tasks/plan.md and the task list to tasks/todo.md. Create the tasks/ directory if it does not exist.
What should I do if requirements change during development?
Update the specification document first to reflect the new scope or decisions, then proceed with implementation.
Related skills
skill-creator
301.8KUsers who want to create, edit, or optimize AI agent skills, ranging from those new to coding to experienced developers
The skill-creator provides a structured workflow for developing, testing, and refining AI agent skills. It guides users through intent capture, skill drafting, iterative evaluation using subagents, and performance benchmarking.
github-actions-docs
264.6KDevelopers and DevOps engineers working with GitHub Actions workflows
The github-actions-docs skill provides grounded answers to GitHub Actions queries by retrieving information from official GitHub documentation. It assists with workflow syntax, security, migration, and runner configuration.
brainstorming
256.4KDevelopers and project managers who need to define requirements, architecture, and design for software projects before writing code
A structured brainstorming framework that guides users through project exploration, design proposal, and specification before implementation. It enforces a strict design-first workflow, requiring user approval for designs and documentation before transitioning to the writing-plans skill.
simple
221.4KDevelopers and project managers who need a fast, lightweight decision-making process for feature design or component creation
A structured brainstorming framework for architectural and creative tasks that guides users from discovery to decision-making through a defined process flow.