feature-dev-mini

Automated gated feature development uses explicit stage gates and approval hooks to ensure no code is written before explicit user consent. It structures the workflow into discovery, grilling, planning, test-first implementation, and validation stages.

A test-first implementation cycle requires defining tests before coding to ensure safe, auditable changes. It enforces a structured test-or-then-implement sequence within the gated workflow to incrementally add functionality only after passing validation.

Preventing unapproved AI code generation requires explicit stage gates and approval hooks. This enforces user consent during the discovery and planning phases, stopping the AI from writing code until scope is aligned and explicitly approved.

Yes, this gated workflow supports small non-trivial feature prototyping. It allows teams to safely prototype features without leaking the risk of unapproved code, incrementally implementing only after passing explicit approval gates.

Start stepwise feature development by initiating discovery and grilling to align on scope. After this initial phase, progress to planning and gated, test-first implementation to ensure safe, auditable changes throughout the process.

You should not use a gated stepwise feature workflow for trivial changes that require no discovery or validation. It is designed for small, non-trivial features requiring explicit user consent, grilling, and test-first implementation to ensure safety.