ss-sdd-implementing-plans

Sequential SDD implementation is orchestrated by dispatching a fresh implementer subagent per plan task, which prevents context pollution and maintains TDD discipline throughout the feature branch.

Task dispatch executes plan tasks sequentially using inline task text, maintaining idempotent stage state via a tasks map, and applying atomic state and todo updates to track per-task completion accurately.

Running implementation on main or master branches is blocked by hard safety gates, which mandate branch selection safety, forbid committing state.json, and require a dedicated feature branch.

A cross-cutting code-quality review is a mandatory final stage analyzing the full branch diff, looping up to a capped limit to address issues and ensure overall code quality before marking completion.

A committed plan is required before starting state management for implementation, as the Skill initializes or syncs state.json task statuses idempotently and dispatches implementation tasks only after the plan is committed.

Sequential execution matters for implementation orchestration because it ensures isolated task processing with fresh subagents, enforces hard safety gates, and performs atomic state updates to maintain progress integrity.