mcpField
S
spec-driven

spec-driven

github.com/adeonirDevelopment8303 installsUpdated today
Repository

About spec-driven

spec-driven is a development skill that guides feature work through specification, design, task breakdown, implementation, optional validation, and archiving. It scales the process to the change, allowing mechanical edits to skip the phases.

Key features

  1. 01Phase-based feature workflow
  2. 02Triage change scope before planning
  3. 03Create specification and design artifacts
  4. 04Break work into implementation tasks
  5. 05Optional UAT and manual archiving

Use cases

  1. 01Plan a feature from a PRD
  2. 02Turn a design into implementation tasks
  3. 03Implement tasks in planned slices
  4. 04Run UAT on a running application

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/adeonir/agent-skills --skill spec-driven

After installing, type/spec-drivenin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

README.md
agents/
openai.yaml
instructions/
archive.md
design.md
implement.md
specify.md
tasks.md
validate.md
references/
acceptance-criteria.md
commit-conventions.md
discovery.md
discriminator.md
memory.md
ordering.md
research-cache.md
simplicity.md
slicing.md
untrusted-content.md
scripts/
lint_artifact.py
select_tasks.py

Details

From the project README

Spec-Driven Development

Feature development in phases. Light by default; weight only where the change pays for it.

Triggers

  • Specify ("plan feature", "spec this", "from PRD", "modify feature", "discuss how to build") → specify.md
  • Design ("design this feature", "technical design", "plan the build") → design.md
  • Tasks ("create tasks", "break into tasks", "task breakdown") → tasks.md
  • Implement ("implement task T-1", "implement T-1 to T-4", "implement slice S-1", "execute tasks", "implement everything") → implement.md
  • Validate / UAT ("run UAT", "manual testing", "validate flows") → validate.md
  • Archive ("archive feature", "archive this spec") → archive.md

Workflow

specify → design → tasks → implement → [validate] → [archive]
   └────────┴────────┴──────────┴──────────┴ a mechanical change skips all of this: one-liner → branch → implement inline

Specify's triage decides the path: a mechanical change with zero load-bearing decisions becomes a one-liner straight to inline implement on its own branch, and a prompt carrying outcomes that ship separately becomes one feature per outcome. Everything else produces the artifacts and runs the phases in turn. Verify is mental, per task, inside implement — never a user phase. Validate is optional UAT on the running application. Archive is manual housekeeping for a feature in any state, never automatic or suggested.

Comments

Markdown supported