cy-tasks-tail-qa-pair

Append canonical QA plan and execution tasks to generated _tasks.md files.

182|8|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/compozy/agh --skill cy-tasks-tail-qa-pair
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cy-tasks-tail-qa-pair
Source: https://github.com/compozy/agh/tree/main/.agents/skills/cy-tasks-tail-qa-pair
Command: npx skills add https://github.com/compozy/agh --skill cy-tasks-tail-qa-pair

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about cy-tasks-tail-qa-pair

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I append QA verification steps to generated task files?▼

Missing QA verification steps are appended by adding canonical QA report and execution task rows to the end of generated `_tasks.md` files, ensuring work reliably closes with measurable release readiness coverage.

When do I need Playwright e2e tests for task generation pipelines?▼

Playwright e2e tests are required when the pipeline detects UI-bearing features like web or site packages, otherwise CLI, API, or daemon cross-surface validation gates are sufficient for coverage.

How do I ensure dependency wiring correctness when adding QA tasks?▼

Dependency wiring correctness is ensured by preserving the exact table column order and sequential task ID structure to match the canonical Hermes tail-template row format when appending QA pairs.

Does the QA pair append tool work with unknown markdown table formats?▼

The tool does not work with unknown table formats, strictly refusing to edit unrecognized structures while exiting as a noop if the trailing QA pair already exists correctly.

What is the best way to repair partial QA insertion in task files?▼

Repair partial QA insertion by detecting incomplete trailing QA pairs and fixing them to satisfy the canonical checklist-based validation structure before finishing the task generation workflow.