qa-tracker-us-closure

What problem does it solve?

When a project's QA-TRACKER.md shows P0 user stories marked NONE or PARTIAL for test coverage, shipping features with full test attribution is blocked. Performing test closure in a single large commit loses per-user-story audit trails, violating ship-gate requirements for traceability.

Core Features & Use Cases

• 6-step per-US test closure rhythm: Audit source code, write invariant-focused tests, run full regression suites, sync the QA tracker, commit, and verify no reverts for each user story individually.
• Flexible test sourcing: Supports both deriving test logic from inline route code and importing exported helper functions for more stable test suites.
• Docs-only retro follow-up registration: Register sprint retro follow-up tasks directly to the QA tracker without writing code, using T-ID naming and NONE-HOLD markers for deferred work.
• Use Case: Ideal for software teams using the US ↔ Test mapping tracker pattern (e.g. PM-System, CRM-System) that need to close P0 test gaps during sprints while maintaining full audit trails for ship gates.

Quick Start

Use the qa-tracker-us-closure skill to close out all NONE/PARTIAL P0 user story test gaps in your project's QA-TRACKER.md file, following the per-US commit cadence and 5-spot tracker sync rules.