plan-refactor-qa

Plan QA coverage for Compozy refactor tasks before implementation.

Updated May 28, 2026
One-click install
npx skills add https://github.com/haryelramalho/skills --skill plan-refactor-qa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-refactor-qa
Source: https://github.com/haryelramalho/skills/tree/main/skills/mine/plan-refactor-qa
Command: npx skills add https://github.com/haryelramalho/skills --skill plan-refactor-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prepares refactor work for QA by gathering the relevant task artifacts, repository context, and existing tests before implementation begins, reducing missed regressions and ambiguous coverage.

Core Features & Use Cases

  • Task discovery: Resolves a refactor slug to the matching .compozy task directory and checks for close matches when the slug is ambiguous.
  • Repository-grounded analysis: Reads PRDs, tech specs, ADRs, task files, and nearby code to identify affected contracts, risks, and test surfaces.
  • QA planning handoff: Builds a regression-focused prompt for qa-report and directs it to produce Smoke, Targeted, Full, and Sanity coverage with automation annotations.
  • Use case: A developer is about to implement a refactor and needs a structured QA plan that highlights P0 and P1 flows without running tests or changing code.

Quick Start

Use the plan-refactor-qa skill with a refactor slug like billing-adjustment so it inspects the corresponding task directory and hands off a QA planning prompt to qa-report.

Frequently Asked Questions about plan-refactor-qa

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

FAQPage Schema
How do I plan QA coverage for a refactor before implementation starts?

QA coverage for a refactor is planned by resolving the task slug, reading PRDs and tech specs, and generating a regression-focused prompt for Smoke, Targeted, Full, and Sanity test levels.

What is regression-focused QA planning for refactoring tasks?

Regression-focused QA planning identifies P0 and P1 flows by analyzing task artifacts and repository code surfaces, creating structured test coverage annotations without executing tests or changing code.

How do I prepare a regression test plan from PRDs and ADRs?

Preparing a regression test plan involves reading PRDs, ADRs, and task files within the task directory to identify affected contracts and risks, then handing off a structured QA planning prompt.

Can I use task slugs to discover refactor requirements in a Compozy directory?

Task slugs map directly to the .compozy/tasks directory, allowing you to discover refactor requirements and automatically check for close matches when the provided slug is ambiguous.

Does QA planning for refactors execute tests or modify existing code?

QA planning for refactors does not execute tests or modify code; it strictly analyzes repository context and existing test surfaces to produce an annotated coverage plan for downstream reporting.

What's the best way to annotate automation status in a refactor test plan?

Annotating automation status in a refactor test plan is handled by generating a QA planning prompt that explicitly tags Smoke, Targeted, Full, and Sanity coverage levels with their automation status.