spec-based-development

Orchestrates subagent pipelines to implement finalized specification bundles with locked design contracts.

3|Updated Aug 3, 2026
One-click install
npx skills add https://github.com/gen4recomp/gen4recomp --skill spec-based-development-gen4recomp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-based-development
Source: https://github.com/gen4recomp/gen4recomp/tree/main/.agents/skills/spec-based-development
Command: npx skills add https://github.com/gen4recomp/gen4recomp --skill spec-based-development-gen4recomp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Implementing a large, multi-deliverable design specification by hand risks drifting from the pinned research baseline, violating reuse and architecture contracts, inventing commit messages, and leaking planning vocabulary into production code. This Skill enforces disciplined, contract-faithful execution of finalized spec bundles through isolated subagent pipelines. ## Core Features & Use Cases - Contract-locked orchestration: Interprets Locked, Preferred, and Discretionary spec text, validates bundle completeness, and stops rather than guessing when sections or baselines are missing. - Dependency-safe subagent pipelines: Creates isolated worktrees per deliverable, runs acceptance-first authoring, TDD implementation, verification gates, and provider-contract checks before integration. - Exact history and final review: Preserves verbatim per-deliverable commit messages, audits requirement coverage, runs a single integrated design review plus branch review, and fast-forwards the protected target only after everything is green. - Use Case: Given a SPEC.md plus deliverables/D01-D05 markdown files describing a multi-part feature, dispatch this Skill to implement every deliverable in dependency order with controlled deviations and a clean, review-verified branch. ## Quick Start Ask the agent to implement the finalized spec bundle at the given path using the spec-based-development workflow, keeping the target branch untouched until final review passes.

Frequently Asked Questions about spec-based-development

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

FAQPage Schema
How do I implement a multi-deliverable spec with AI subagents?

Provide a SPEC.md plus deliverables/Dxx-*.md files and let the orchestrator validate the bundle, create isolated worktrees, and dispatch fresh subagents per deliverable. Each deliverable runs acceptance authoring, TDD implementation, verification gates, and an exact prescribed commit before integration.

What is acceptance-first development in a spec pipeline?

Acceptance scenarios are authored before any production code, and the expected failing red state must be observed for the right reason. Implementations then make those frozen tests pass without weakening them, alongside required lower-level tests.

Can the implementation deviate from the locked specification?

Only through an approved deviation recorded in a ledger with evidence and authority. Subagents may propose deviations but never approve them; material changes to behavior, architecture, or public surface require human approval.

Why must the target HEAD match the spec research commit?

Exact file and symbol recipes in the spec were researched at one pinned revision, so drift invalidates them. If the target HEAD differs from the research commit, the workflow stops instead of reinterpreting the spec against a nearby revision.

What are the limitations of spec-based orchestration?

It requires a complete, finalized design-heavy bundle with literal commit messages and a valid dependency graph; incomplete sections, TODO placeholders, or templated commits cause it to stop. It also never pushes branches or opens PRs unless separately requested.