build-feature

To implement a feature end-to-end, plan-first workflow enforces creating a scoped plan document, generating a code diff, and writing tests in that exact order to ensure traceability before edits. It produces a plan, a diff, and tests sequentially.

The best way to validate feature development before landing code in src/ is evidence-based validation, enforcing that tests are shipped alongside code diffs and gated until approved to prevent premature deployments.

A plan, diff, and test pipeline works by producing a feature plan outlining scope and acceptance criteria, generating the implementation diff, and finally writing tests, ensuring changes are reviewable and testable before code edits.

Yes, you need a product brief, an ADR, or a specific user request to scope feature development. The plan-first workflow uses these inputs to define the feature scope and acceptance criteria before generating any code diffs.

You should enforce smallest-change execution and self-review during feature implementation to ensure changes are well-documented, reviewable, and testable, enforcing governance and gating to prevent deployments until approved.

A limitation of a plan-first workflow for feature development is its strict ordering: it requires producing a plan, a diff, and tests sequentially, which may not suit rapid prototyping outside architecture invariants.