spec-driven-development

Execute SPEC-1 workflows to create, implement, validate, and document feature specs.

1|Updated Dec 25, 2017

Search Tags:#workflow #documentation #spec-driven #specifications #traceability #SPEC-1

Ready to run

npx skills add https://github.com/mattniedelman/dotfiles --skill spec-driven-development-mattniedelman

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/mattniedelman/dotfiles/tree/main/dot_augment/skills/spec-driven-development
Command: npx skills add https://github.com/mattniedelman/dotfiles --skill spec-driven-development-mattniedelman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides feature development by following SPEC-1 driven processes from the Basic Memory specs project, enabling teams to translate specifications into concrete implementations with traceability.

Core Features & Use Cases

Spec-driven workflow: Create, discuss, implement, validate, and document a spec using the SPEC-1 methodology.
Spec management: Read, write, and update specs within the Basic Memory "specs" project to keep alignment between intent and code.
Progress tracking: Use living checklists to reflect the current state of work and decisions as tasks are completed.
Review & validation: Ensure implementation meets the spec criteria before release.

Quick Start

Create a SPEC-XX: Your Feature Name in the specs project and initiate the SPEC-1 workflow (Create, Discuss, Implement, Validate, Document).

Frequently Asked Questions about 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 guide feature implementation?▼

Spec-driven development is a workflow where a specification is created, discussed, implemented, validated, and documented before coding. It enforces a structured process to ensure traceability and alignment between project intent and concrete code implementation.

How do I implement a feature from a specification using a structured workflow?▼

To implement a feature from a specification, initiate a structured workflow by creating a SPEC-XX entry, discussing the requirements, writing the code, validating against the spec criteria, and documenting the outcomes using a living progress-tracking checklist.

How do I track progress and maintain traceability during spec implementation?▼

You track progress and maintain traceability by using living checklists that reflect the current state of work and decisions. This structured format ensures alignment between the SPEC-1 documentation and the implemented code as tasks are completed.

Can I use spec-driven development to align team discussions before coding starts?▼

Yes, spec-driven development explicitly supports team alignment by embedding a discussion phase in the workflow. Specifications are created and discussed before implementation, ensuring all stakeholders share a validated understanding of the requirements.

When should I not use a spec-driven workflow for feature development?▼

You should avoid a spec-driven workflow for rapid prototyping or exploratory tasks where requirements are highly volatile. The overhead of creating, validating, and documenting formal specifications before coding slows down iterative, undefined feature development.