S

Spec-Driven Planning

Task specification refinement pipeline with 6 stages (parallel analysis, architecture synthesis, decomposition, parallelization, verification, promotion) and quality gates

Home/Developer Tools/Spec-Driven Planning

What is it?

Note: Phases not in ACTIVE_STAGES are skipped. If SKIP_JUDGES is true, all judge steps are skipped entirely. Human checkpoints (🔍) occur after phases in HUMAN_IN_THE_LOOP_PHASES.

Input: Draft Task File (.specs/tasks/draft/*.md)
    │
    ▼
Phase 2: Parallel Analysis
    │
    ├─────────────────────┬─────────────────────┐
    ▼                     ▼                     ▼
Phase 2a:             Phase 2b:             Phase 2c:
Research              Codebase Analysis     Business Analysis
[sdd:researcher sonnet]   [sdd:code-explorer sonnet]  [sdd:business-analyst opus]
Judge 2a              Judge 2b              Judge 2c
(pass: >THRESHOLD)     (pass: >THRESHOLD)     (pass: >THRESHOLD)
    │                     │                     │
    └─────────────────────┴───────────────────

How to use it?

Key Features

  • Task specification refinement pipeline with 6 stages (parallel analysis, architecture synthesis, decomposition, parallelization, verification, promotion) and quality gates
  • Seamless integration with Claude's development workflow
  • Comprehensive guidelines and best practices for spec-driven planning
View on GitHub

GitHub Stats

Stars
Forks
Last Update
Author
NeoLabHQ
License
GPL-3.0
Version
1.0.0

Features