sdd-architect

Prevent cowboy coding by enforcing a specification-driven development workflow that gates implementation behind a formal plan. This governance process requires drafting a specification and an implementation plan that must pass a review decision gate before any coding begins.

Specification-driven development is a plan-first governance workflow that halts progress until an implementation plan is approved. It satisfies requirements for a drafting phase, explicit implementation plan sections, and a decision gate to ensure safe, auditable progress.

Generate a formal specification document by describing your feature in detail to trigger the drafting phase. The process produces a spec file including goals, user stories, and technical constraints to guide development before an implementation plan is created.

An implementation plan for auditable progress requires specific sections: Goal Description, User Review Required, Proposed Changes, and Verification Plan. These sections ensure safe, governed execution before the decision gate allows implementation to begin.

You need a decision gate review whenever stakeholders request new features or changes without an existing plan, or when requirements are vague. This gate requires explicit review and approval of the specification and implementation plan before any implementation begins.

You cannot start coding immediately with ambiguous requirements because the governance workflow halts progress. It enforces a drafting phase to clarify goals, user stories, and technical constraints, followed by a mandatory decision gate requiring plan approval before implementation.