skills.rest
jampissarandev
jampissarandevCOMMUNITY
Explore all skills by this author →
GitHub

spec-driven-development

Writes structured specifications before coding through a gated specify-plan-tasks-implement workflow.

Updated Jun 23, 2026
Search Tags:#workflow#planning#documentation#software design#specification#requirements#acceptance criteria
One-click install
npx skills add https://github.com/jampissarandev/Expense-Tracker --skill spec-driven-development-jampissarandev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/jampissarandev/Expense-Tracker/tree/main/.github/skills/spec-driven-development
Command: npx skills add https://github.com/jampissarandev/Expense-Tracker --skill spec-driven-development-jampissarandev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents wasted engineering effort caused by ambiguous or unwritten requirements by forcing a written, human-reviewed specification before any code is produced. ## Core Features & Use Cases - Four-Phase Gated Workflow: Progresses through Specify, Plan, Tasks, and Implement phases, each requiring human review before advancing. - Spec Template with Six Core Areas: Covers objective, commands, project structure, code style, testing strategy, and Always/Ask First/Never boundaries. - Assumption Surfacing and Success Criteria: Converts vague requests like "make it faster" into concrete, testable targets before implementation begins. - Use Case: When starting a new feature with unclear requirements, use this Skill to draft a spec, get it approved, break it into verifiable tasks, and only then implement. ## Quick Start Ask the AI to write a specification for the new feature before writing any code, covering objectives, commands, structure, style, testing, and boundaries.

Frequently Asked Questions about spec-driven-development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a specification before coding a new feature?▼

Follow the four-phase workflow: Specify, Plan, Tasks, Implement. Write a spec covering objective, commands, project structure, code style, testing strategy, and boundaries, then get human approval before advancing to planning and implementation.

What should a software specification document include?▼

A spec should include an objective with success criteria, executable commands, project structure, a code style example, testing strategy, and three-tier boundaries (Always do, Ask first, Never do), plus open questions needing human input.

When should I skip writing a spec?▼

Skip full specs only for single-line fixes, typo corrections, or changes with unambiguous self-contained requirements. Even simple tasks benefit from a two-line spec with acceptance criteria.

How do I handle vague requirements like make the dashboard faster?▼

Reframe vague requirements as concrete success criteria, such as LCP under 2.5 seconds on 4G or data load under 500ms, then confirm those targets with the human before implementing.

Why keep the spec updated after implementation starts?▼

The spec is a living document that must reflect decision and scope changes. Updating it first, committing it to version control, and referencing it in PRs keeps the shared source of truth accurate.

Related Skills

Explore More Software Engineering Skills→
DagimAlemayehuuDagimAlemayehuu

agentic-engineering-discovery

Validate product problems and produce an approved discovery brief before specification.

Community
Intermediate
WizarckWizarck
2

bmad-agent-dev

Executes approved development stories with test-driven implementation and acceptance criteria tracking.

Community
Intermediate
koolerkxkoolerkx

context-engineering

Load and organize project rules and specs into a context hierarchy.

Community
Advanced
80portisfound80portisfound

spike

Build throwaway prototype experiments to validate technical feasibility before committing to a build.

Community
Intermediate