expiracy/dev-workflow

Use when implementing features, fixing bugs, or changing behavior with automated tests, especially when the user requests TDD, Canon TDD, or Kent Beck's approach. Does not apply to prose edits or changes without executable behavior.

Choose appropriate tests and review coverage for changed behavior, integrations and failure modes. Use for test planning, deciding what to mock or run for real, and assessing whether checks support a correctness claim.