spec-gen-implement-story

To implement a story on a brownfield codebase safely, orient on structural risk and validate specs before coding. This ensures you select correct insertion points and verify domain model alignment to reduce drift.

Yes, existing spec-gen analysis is a required prerequisite. You need the structural context from a prior spec-gen analysis to orient risk, find insertion points, and validate specs before touching code.

Risk assessment works by orienting on the story context and structural risk before coding. It helps you find safe insertion points and ensures alignment with existing specs to minimize refactoring drift.

You should enforce a test gate immediately after coding and before running drift checks. This validates the story implementation and ensures structural alignment before verifying drift on the brownfield codebase.

The best way to validate specs is by using spec-gen structural context to orient risk and verify alignment with domain models. This validates prerequisites and finds correct insertion points before coding begins.