spec-driven-dev-v2

Coordinate long-running software development across multiple sessions by using a three-level Project, Sprint, and Task hierarchy with per-task state tracking and worktree isolation to ensure consistent progress.

A spec-driven development workflow for multi-day features uses a structured Project to Task hierarchy, enforcing per-task isolation, review loops, and governance checks to maintain state and context across sessions.

Manage per-task state and worktree isolation by storing progress in JSON files and running each task in a clean checkout, enabling safe rollbacks and structured review rounds with context packs.

You can enforce governance checks and code boundaries during task orchestration by applying governance-as-code rules, utilizing scripts and linting to verify boundaries before approving review cycles.

The best way to structure feedback cycles for isolated tasks is using a review round-loop that provides reasoning-blind reviewers with a context pack briefing to validate changes before approval.

Avoid using a multi-session task orchestration state machine for short-lived or single-session feature development, as the overhead of project hierarchies, worktree isolation, and governance checks outweighs the benefits.