skills.rest
japurcell
japurcellCOMMUNITY
Explore all skills by this author →
GitHub

addy-spec-driven-development

Define a complete spec before coding to align expectations.

Updated Mar 19, 2026
Search Tags:#workflow#planning#documentation#specification#requirements#project-management
One-click install
npx skills add https://github.com/japurcell/skills --skill addy-spec-driven-development
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: addy-spec-driven-development
Source: https://github.com/japurcell/skills/tree/main/skills/addy-spec-driven-development
Command: npx skills add https://github.com/japurcell/skills --skill addy-spec-driven-development

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates a disciplined approach to product and software development by requiring a formal spec before coding, reducing ambiguity and rework.

Core Features & Use Cases

  • Enforces a four-phase workflow (Specify, Plan, Tasks, Implement) to align teams and surface assumptions early.
  • Provides structured templates for objective, scope, success criteria, and planning to guide discussions.
  • Suitable for starting new projects, large features, or architectural decisions where requirements are unclear or evolving.

Quick Start

Create a Spec document outlining objective, scope, and success criteria before starting implementation.

Frequently Asked Questions about addy-spec-driven-development

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

FAQPage Schema
What is spec-driven development and how does it reduce software rework?▼

Spec-driven development requires defining a formal specification covering objectives, scope, and success criteria before coding. This structured approach surfaces assumptions early and aligns team expectations, directly reducing ambiguity and downstream rework.

How do I write a project specification for a new feature with evolving requirements?▼

Write a project specification by working through a four-phase workflow: Specify, Plan, Tasks, and Implement. Use structured templates to document the objective, scope, boundaries, and success criteria to guide discussions and handle evolving requirements effectively.

When should I use a specification workflow instead of directly coding a new project?▼

Use a specification workflow when starting new projects, building large features, or making architectural decisions where requirements are uncertain, ambiguous, or evolving. It forces team alignment and review before implementation begins.

What is the best way to manage project planning for uncertain software requirements?▼

The best way to manage uncertain software requirements is enforcing a structured planning phase that defines boundaries and success criteria before implementation. This disciplined approach reduces ambiguity and ensures all stakeholders review expectations first.

What should be included in a software development spec to align team expectations?▼

A software development spec must include the project objective, scope, success criteria, boundaries, and a defined plan. Designing this content for formal review before implementation ensures all team members share aligned expectations.

Related Skills

Explore More Software Engineering Skills→
hilaryosbornehilaryosborne

da-planning

Define objectives and scope for data analytics project planning.

Community
Basic
Codagent-AICodagent-AI
30

design

Convert settled software requirements into approved technical design artifacts.

Official
Advanced
rik-simformrik-simform

sdlc-traceability

Automate requirements traceability maintenance across SDLC tools.

Community
Intermediate
martinffxmartinffx
39

atelier-spec-product

Conduct discovery interviews to define feature scope and requirements.

Community
Intermediate