phased-qa

Verify software implementation against a phased plan using command-line evidence.

1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/hadi-technology/phased-workflow --skill phased-qa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phased-qa
Source: https://github.com/hadi-technology/phased-workflow/tree/main/skills/phased-qa
Command: npx skills add https://github.com/hadi-technology/phased-workflow --skill phased-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the gap between code implementation and production readiness by enforcing a rigorous, evidence-based verification gate that prevents false claims of completion.

Core Features & Use Cases

  • Exhaustive Verification: Performs multi-round audits of code diffs, ensuring every functional and code-based Definition of Done (DoD) is backed by fresh, verifiable command output.
  • Rationalization Prevention: Structurally forces the agent to run commands and report raw output, banning subjective language like "looks correct" or "should pass."
  • Use Case: Use this after a feature implementation to verify that the code matches the plan, adheres to project patterns, and passes all integration tests without relying on the implementer's self-reported status.

Quick Start

Trigger the phased-qa skill to perform a full verification pass against the current implementation plan.

Frequently Asked Questions about phased-qa

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

FAQPage Schema
How do I automate QA verification for phased software builds?

Automate QA verification for phased builds by enforcing evidence-based checks against a structured plan, requiring raw command-line output to validate code diffs and prevent false completion claims.

What is the best way to prevent rationalization during code review and compliance auditing?

Prevent rationalization during code review by structurally forcing the agent to run commands and report raw output, banning subjective language like "looks correct" when verifying Definition of Done items.

How do I independently verify Definition of Done items without relying on implementer self-reporting?

Independently verify Definition of Done items by performing multi-round audits of code diffs, ensuring every functional requirement is backed by fresh, verifiable command output rather than self-reported status.

Does autonomous QA work for regression testing in complex codebases?

Autonomous QA works for regression testing in complex codebases by applying systematic finding management and exhaustive command-line evidence gates to verify implementation matches the plan.

When should I use automated compliance auditing for post-implementation quality assurance?

Use automated compliance auditing for post-implementation quality assurance when you need to verify code adheres to project patterns and passes integration tests without subjective assumptions.

Why does phased QA require strict adherence to evidence-based reporting?

Phased QA requires strict adherence to evidence-based reporting to eliminate the gap between code implementation and production readiness by preventing false claims of completion through verifiable command output.