qa-test-management

QA test management automates consistent naming (QA-YYYYMMDD-###-feature-name.md), organized directory structure (draft, active, executed, archived), and enforced status transitions (DRAFT → ACTIVE → EXECUTED → ARCHIVED). This ensures traceability, prevents disorganization, and maintains clear test lifecycle tracking across your quality assurance process.

QA tests require essential metadata: Test ID, Feature, Application, URL, Status, and Priority. The Skill enforces these fields and establishes PRD traceability links, enabling you to connect tests directly to Product Requirements Document sections and maintain audit-ready documentation of test-to-requirement relationships.

Yes. The Skill enforces strict status transitions and validates workflow progression, automatically applying naming conventions and directory placement as tests move through draft, active, executed, and archived states. You can log execution results, capture evidence, and apply archival rules without manual state management.

Standardized documentation is essential for test traceability and team collaboration. This Skill applies required metadata fields and naming conventions to eliminate ambiguity, ensure consistent test organization, and make execution history and evidence capture retrievable across your QA lifecycle.

The Skill establishes PRD traceability by including requirement linkage in test metadata, enabling you to connect each test case to specific Product Requirements Document sections and create bidirectional traceability for compliance and impact analysis.

The Skill implements standardized archival rules that move executed or obsolete tests to the archived directory while preserving execution history and evidence. This maintains a clean active test set while keeping historical records for audit and reference purposes.