quality-playbook

What problem does it solve?

It solves the problem of inconsistent and incomplete quality assurance by converting a codebase into a durable, spec-traced quality system. Instead of only running tests or performing superficial reviews, it discovers requirements from the code and available documentation, then validates those requirements via a structured audit pipeline with explicit traceability.

Core Features & Use Cases

• Spec-traced requirements and contracts: Derives testable requirements from the repository’s code and documentation evidence, producing an auditable quality constitution.
• Multi-pass verification: Runs a three-pass code review plus a multi-model “Council of Three” spec audit to find defects missed by structural review alone.
• TDD-verified fixes: Confirms and regression-tests bugs through a red-green TDD loop and produces a consolidated bug report with verified patches.

Typical use cases include self-auditing a project’s readiness for release, generating a quality system for a new repository, or performing repeatable quality engineering across languages and frameworks.

Quick Start

Run the quality-playbook on your target repository by telling an AI agent: "Run the Quality Playbook" (optionally with a hint like "self-audit" or "quality playbook").