Common Tdd

This does not comply with TDD as stated. If the implementation already exists and the plan is to add tests afterward for coverage, the skill requires stopping and resetting to a Red-Green-Refactor flow.

Correct response under this skill:

- Do not treat post-implementation coverage work as TDD.
- If the new code was written before a failing test, that code should not be considered valid TDD evidence.
- Reconstruct the work by defining the expected behavior in a failing test first.
- Verify the test fails for the expected behavioral reason.
- Re-implement only the minimum code needed to make that test pass.
- Continue one failing test at a time until the required behavior is covered.

Coverage is a verification threshold, not a substitute for the Red step. Reaching 80% after the fact does not prove the implementation was driven by tests. The compliant path is to rebuild confidence through failing-first tests, AAA structure, and incremental minimal implementation.