1 results for tag "quality-playbook"
Explores any codebase first (domain, architecture, specs, failure history, optional AI chat-history mining) and then generates six grounded artefacts: `quality/QUALITY.md` constitution, language-appropriate spec-traced functional tests, `RUN_CODE_REVIEW.md` with anti-hallucination guardrails, `RUN_INTEGRATION_TESTS.md`, a Council-of-Three multi-model `RUN_SPEC_AUDIT.md`, and an `AGENTS.md` bootstrap file. Designed to go beyond test-stub generators and prevent generic "coverage theatre" by tying every output to specific functions, schemas, or defensive patterns in the actual code.