What problem does it solve? It enforces a disciplined, design-spec-first process for building new features, preventing teams from writing code before requirements, design specs, and phased plans are confirmed, and ensuring every change is verified by CI before merging. ## Core Features & Use Cases - Ten-Step Gated Workflow: Strictly ordered stages from requirement confirmation, worktree creation, design spec, plan writing, TDD implementation, code sync, documentation check, lint/push, to merge cleanup, with hard gates blocking skipped steps. - Three-Subagent Parallel Reviews: Design specs, plans, and code are each reviewed by three parallel subagents covering coverage/scope, consistency/correctness, and verifiability/UI observability, with automatic fix-and-recheck loops. - State Persistence and Recovery: A JSON state file tracks current step, phase, commits, and merge status so interrupted sessions can resume without restarting from scratch. - Use Case: When adding a new UI-heavy feature to an iOS or web app, use this workflow to produce a design spec, visual prototype, test case matrix, phased TDD plans, and CI-verified commits before merging into develop. ## Quick Start Ask the assistant to start the feature development workflow for your new feature and answer the requirement questions it poses.