What problem does it solve? It enforces a disciplined, gated workflow for implementing an approved BeeUI issue so changes stay within approved scope, land in the exact target worktree and branch, and ship with complete test and verification evidence instead of ad-hoc edits. ## Core Features & Use Cases - Target verification gates: Confirms working directory, branch, and git status before any edit, and stops on mismatches or unrelated pre-existing changes. - Change-level classification: Classifies work as low-risk, runtime-risk, or security-sensitive using SDLC and security docs, then derives proportional checks. - Evidence-based reporting: Produces a consolidated implementation report covering acceptance criteria, executed commands with exit codes, security review, and dependency/version status. - Use Case: After a BeeUI issue is approved and a feature branch is prepared, run this workflow to implement exactly the approved scope, run the required test suite via uv run, and return a structured report ready for review. ## Quick Start Implement the approved BeeUI issue in the specified target worktree on the expected branch and return the full implementation and verification report.