spec-driven-development-suite

Coordinate spec-driven development workflows across project phases using local documents.

64|2|Updated Feb 8, 2018
One-click install
npx skills add https://github.com/yuki-yano/dotfiles --skill spec-driven-development-suite
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-driven-development-suite
Source: https://github.com/yuki-yano/dotfiles/tree/main/.agents/skills/spec-driven-development-suite
Command: npx skills add https://github.com/yuki-yano/dotfiles --skill spec-driven-development-suite

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end lifecycle of spec-driven development within a project, unifying steering, requirements, design, tasks, and implementation to avoid context switching.

Core Features & Use Cases

  • Steering & governance: Aligns project goals by centralizing steering documents and spec progress tracking.
  • In-repo execution: Reads and updates local docs (spec.json, requirements.md, design.md, tasks.md) to progress through the workflow.
  • End-to-end activation: When users request "design from specs" or "validate implementation", coordinates across phases and maintains audit trails.

Quick Start

Initialize a new spec-driven project and follow the guided prompts to generate spec.json and requirements.md.

Frequently Asked Questions about spec-driven-development-suite

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

FAQPage Schema
How do I coordinate spec-driven development across requirements, design, and implementation phases?

This suite coordinates spec-driven development workflows by reading and updating local documents to drive phase progression from steering and requirements to design, tasks, and implementation, ensuring traceability across the project.

What is the best way to maintain traceability across steering documents and project tasks?

Traceability is maintained by reading local steering materials and spec documents to drive next actions, producing task artifacts and updating progress within the project repository automatically.

How do I generate a spec.json file and requirements.md for a new project?

Initialize a new spec-driven project in your repository and follow the guided prompts to generate spec.json and requirements.md, establishing foundational steering documents for governance.

Can I validate implementation progress against design specs stored in my repository?

You can validate implementation by requesting phase coordination, which reads local design.md and tasks.md documents to ensure artifact updates and traceability against established project specifications.

Does spec-driven development require external tools or can it run entirely within my repo?

Spec-driven development workflows can run entirely within your repository by operating on local documents to produce spec.json and task artifacts, avoiding context switching across external platforms.