speckit-test-hardening

To add regression tests after acceptance without reopening the build, apply targeted test hardening to verify prerequisite evidence and add the smallest useful test artifact around risky boundaries. This reduces real risk by focusing only on narrow, high-value coverage.

Test hardening in a spec-kit workflow is adding focused regression protection for completed implementations after acceptance and simplification. It chooses the smallest useful test artifact or records an N/A rationale to reduce real risk.

To document test hardening decisions in progress.md, record the commands run, verification results, reviewed risk areas, and the next required stage. Include an N/A rationale if you skip adding a test artifact.

You should skip adding regression coverage when the test hardening review determines optional extra coverage is not worthwhile. Record an N/A rationale in progress.md explaining why the reviewed risk areas do not require a new test artifact.

Yes, you can use test hardening for bugfixes and contract boundaries in spec-kit workflows. It adds or adjusts the smallest useful test artifact around a risky boundary, bugfix, or contract to prevent future regressions.

Yes, test hardening requires prerequisite evidence before adding a smoke test. It verifies existing implementation evidence from the completed feature to determine whether optional extra coverage is worthwhile and safe to add.