ss-sdd-coordinator

Spec-driven development workflow coordination is handled by dispatching the correct phase skills and per-task subagents at each stage, enforcing required stage ordering and approval gates from discovery through merge.

Enforcing stage gates and git safety during feature planning requires a coordination pipeline that mandates atomic stage-boundary state updates, deterministic dispatch, and strict policies like never committing state.json.

A shared state file in agent subagent workflow orchestration carries pipeline data between stages via a per-feature state file, allowing per-task subagents to access and update the current pipeline state.

Yes, this workflow orchestration approach supports architecture decisions and code changes by relying on dedicated phase skills to generate specs, plans, ADRs, and the actual code modifications.

Yes, you need dedicated phase skills to run a spec-driven feature development pipeline because the coordinator separates orchestration responsibilities from the phase skills that generate the actual specs, plans, and code.

State.json must never be committed in git safety workflows because it serves as a transient per-run state file for atomic stage-boundary updates, and committing it would pollute the repository with internal pipeline data.