quality-stinger

Audit completed implementations against source plan documentation and generate severity-classified findings reports.

72|28|Updated May 23, 2026
One-click install
npx skills add https://github.com/legioncodeinc/that-git-life --skill quality-stinger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quality-stinger
Source: https://github.com/legioncodeinc/that-git-life/tree/main/.claude/skills/quality-stinger
Command: npx skills add https://github.com/legioncodeinc/that-git-life --skill quality-stinger

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill solves the problem of inconsistent implementation reviews by giving AI agents a repeatable process to verify completed work against its source plan documentation and identify gaps before release.

Core Features & Use Cases

  • Plan-to-Code Auditing: Compares implementation changes against PRDs, requirements, and acceptance criteria to verify completeness and alignment.
  • Structured Quality Reports: Produces severity-classified findings reports with scorecards, traceability tables, and evidence-based recommendations.
  • Use Case: A development team finishes a feature implementation and uses this Skill to confirm that every planned requirement was delivered before merging the changes.

Quick Start

Ask the quality-stinger skill to audit the completed implementation against its source plan and generate a QA findings report.

Frequently Asked Questions about quality-stinger

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

FAQPage Schema
How do I verify code implementation against a PRD before merging?

A PRD verification audit compares completed implementation changes against source plan documentation, tracing requirements and inventorying changes to identify missing requirements, mismatches, and quality issues before release.

What is traceability in code review and release readiness checks?

Traceability in code review maps planned requirements directly to implementation changes, verifying every acceptance criterion is delivered and classifying any mismatches by severity for release readiness checks.

How do I audit a GitHub implementation for missing requirements?

Auditing a GitHub implementation involves applying a structured process of plan tracing and change inventory to identify missing requirements, producing a severity-classified markdown findings report with evidence-based recommendations.

Can I generate a structured QA audit report for an AI-assisted engineering loop?

You can generate a structured QA audit report for an AI-assisted engineering loop by auditing completed work against source plans and producing severity-classified markdown findings with scorecards and traceability tables.

Does implementation review work without dependencies?

Implementation review operates without external dependencies, relying on scripts to execute a repeatable audit process that verifies implementation completeness and alignment against source plan documentation.