← ClaudeAtlas

release-decision-enginelisted

Aggregates all quality signals into a deterministic release decision (GO/CONDITIONAL/BLOCKED). Uses domain-specific weighted scoring. Always runs LAST in staging-uat and release-decision pipelines. Use when deciding whether a release is safe.
mytechsonamy/VibeFlow · ★ 0 · AI & Automation · score 75
Install: claude install-skill mytechsonamy/VibeFlow
# Release Decision Engine ## Phase Contract This skill runs in **DEPLOYMENT** only. Before any other step, read `vibeflow.config.json`'s `currentPhase`. If it is not DEPLOYMENT, emit: > release-decision-engine is for DEPLOYMENT phase; current is > `<phase>`. Complete TESTING gates (coverage, mutation, UAT) and run > `/vibeflow:advance` first. …and stop. The engine is read-only by design (no Write tool), so the hook never sees it, but a phase-mismatched invocation would produce a misleading verdict on incomplete inputs — the self-check catches that before any file is read. The final gate in the VibeFlow pipeline. Produces an explainable, deterministic release decision. ## Input Required: - coverage-report.md (from coverage-analyzer) - uat-raw-report.md (from uat-executor) - test-results.md (from test-result-analyzer) - Domain config (from vibeflow.config.json) - Risk tolerance (from vibeflow.config.json) Optional (improve decision quality): - invariant-matrix.md (from invariant-formalizer) - chaos-report.md (from chaos-injector) - traceability-report.md (from traceability-engine) - business-rules.md (from business-rule-validator) ## Algorithm ### Step 1: Hard Blocker Check These conditions result in IMMEDIATE BLOCKED decision (no scoring needed): 1. Any P0 requirement has < 100% test coverage 2. Any UAT P0 scenario failed 3. Any critical invariant violation exists 4. Self-contradiction detected in business rules 5. Double-entry accounting violation (financial domain)