spec-driven-dev

Translate vague feature ideas into a formal SPEC.md contract.

231|24|Updated Apr 11, 2026

Search Tags:#workflow #planning #ai #spec #software-development #gate

Ready to run

npx skills add https://github.com/LichAmnesia/lich-skills --skill spec-driven-dev-lichamnesia

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-driven-dev
Source: https://github.com/LichAmnesia/lich-skills/tree/main/skills/spec-driven-dev
Command: npx skills add https://github.com/LichAmnesia/lich-skills --skill spec-driven-dev-lichamnesia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often begin implementing a feature before a clear contract exists, which leads to scope drift, misalignment, and costly rework across multiple files and teams.

Core Features & Use Cases

Gate-driven lifecycle: SPEC → PLAN → BUILD → TEST → REVIEW → SHIP with explicit exit criteria for each phase.
Artifact-centered governance: each phase produces a deployable artifact (e.g., SPEC.md, PLAN.md, PR descriptions, test results) that anchors agreement and traceability.
Risk reduction and collaboration: enforces deliberate progression, enabling reviewers to identify gaps early and coordinate across product, engineering, QA, and operations.

Quick Start

Create SPEC.md outlining the what, why, and acceptance criteria, then draft PLAN.md to break the work into tasks before coding.

Frequently Asked Questions about spec-driven-dev

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

FAQPage Schema

How do I prevent scope drift when coordinating AI-driven software development?▼

To prevent scope drift in AI-driven software development, translate vague feature ideas into a formal SPEC.md contract that defines what, why, and for whom before implementation begins. This contract anchors agreement and traceability across cross-file work.

What is a gate-driven workflow for software development planning?▼

A gate-driven workflow for software development planning is a six-phase lifecycle (SPEC → PLAN → BUILD → TEST → REVIEW → SHIP) with explicit exit criteria. Each phase produces a deployable artifact like SPEC.md or PLAN.md to enforce deliberate progression.

How do I start contract-first software development with a SPEC.md file?▼

To start contract-first software development, create a SPEC.md file outlining the what, why, and acceptance criteria for your feature. Then draft a PLAN.md to break the work into tasks before coding to ensure predictable planning and delivery.

Does artifact-centered governance help coordinate cross-file work across teams?▼

Artifact-centered governance helps coordinate cross-file work by anchoring each phase to a deployable artifact like SPEC.md, PLAN.md, or test results. This enables product, engineering, QA, and operations teams to identify gaps early and maintain traceability.

What should be included in a software feature SPEC to enable predictable delivery?▼

A software feature SPEC must include explicit success criteria, assumptions, and boundaries to enable predictable delivery. Outlining the what, why, and for whom ensures the formal contract prevents costly rework and misalignment.