review-to-release-workflow

What problem does it solve?

It prevents risky, unclear changes by forcing a structured codebase review, decision capture, approval-based implementation, and evidence-based release readiness.

Core Features & Use Cases

• Phase 1 Discovery (codebase → QUESTIONS.md): performs a staff/principal-engineer style audit to identify ambiguities, risks, and missing decisions, producing a detailed QUESTIONS.md decision backlog.
• Phase 2 Implementation (answered questions → approved plan → changes): reads the answered QUESTIONS.md, converts decisions into a scoped implementation plan, obtains explicit human approval, and applies only approved changes while generating IMPLEMENTATION_NOTES.md.
• Phase 3 Verification (changes → evidence → VERIFICATION.md): verifies that approved decisions were implemented correctly and that scope boundaries were respected, producing VERIFICATION.md.
• Phase 4 Release Readiness (artifacts → verdict → RELEASE_READINESS.md): assesses build, configuration, tests, deployment assumptions, operational readiness, and docs to produce a final Ready / Ready with caveats / Not ready verdict.

Quick Start

Tell the agent to run review-to-release-workflow for your repository and explicitly specify the release target (for example, production) before it begins discovery.