cy-tasks-tail-qa-pair

What problem does it solve?

It prevents missing verification steps by ensuring every generated task file ends with a canonical QA plan and a real-scenario QA execution pair, so work reliably closes with measurable coverage.

Core Features & Use Cases

• Auto-appends the canonical QA pair: Adds $qa-report and $qa-execution tasks to the end of every cy-create-tasks-produced _tasks.md.
• Template-mirrored task rows: Preserves the exact table column order and row dependency structure to match the Hermes template.
• UI vs non-UI coverage detection: Detects UI-bearing features (web, site packages, e2e paths) to decide whether to require Playwright-driven e2e execution, otherwise applies CLI/API/daemon cross-surface gates.
• Safety checks and no-duplication: Exits as noop if the trailing QA pair already exists correctly, repairs partial QA insertion, and refuses to edit unknown table formats.
• Artifacts and verification workflow: Creates matching task_NN.md files and enforces a checklist-based validation before finishing.

Quick Start

Use cy-tasks-tail-qa-pair immediately after cy-create-tasks finishes generating _tasks.md so it appends the missing QA plan and QA execution tasks with the correct dependencies.