prd-v07-implementation-loop

Test-first development and traceability during EPIC builds are enforced by a deterministic Implementation Loop: load context, write a failing test, implement code, apply @implements tagging, update SoT artifacts, and validate before repeating.

An Implementation Loop for EPIC delivery is a repeating cycle of context loading, test writing, coding, tagging, SoT updates, and validation that ensures incremental progress and auditable traceability across planning, design, build, and validation phases.

Code-to-spec traceability is maintained by declaring relevant IDs with @implements and @see references in every major code unit, ensuring a persistent mapping between code, specifications, and tests.

Session state is preserved by updating Section 0 with Last Action, Stopping Point, Next Steps, and Context before ending any session, guaranteeing continuity for the next implementation cycle.

No external dependencies are required to run the test-first implementation loop, as the Skill operates independently to orchestrate context loading, coding, tagging, and SoT validation steps.

The best way to keep source of truth artifacts aligned is through continuous SoT updates within the Implementation Loop, validating that specifications, tests, and code remain synchronized after every incremental build step.