jarvis-plan-reviewlisted

# /plan-review — 11-Section Rigorous Design Review Reviews a feature plan, RFC, or architecture doc across 11 independent dimensions. Goal: push the plan to "best-in-class" — not to rubber-stamp it. ## When to invoke - After writing a feature design doc or RFC - "Is this approach OK?" / "What did I miss?" / "Is there a better way?" - Before kicking off any nontrivial implementation ## 11 sections 1. **Problem definition** — Is the problem stated precisely? What evidence supports it being worth solving? 2. **Scope boundaries** — What is explicitly in scope, out of scope, and deferred? 3. **Architecture** — Data flow, dependencies, blast radius of failure 4. **Security** — Authentication, authorization, secrets handling, PII boundaries, threat model 5. **Observability** — Logs, metrics, alerts, on-call playbook 6. **Deployment** — Rollback strategy, gradual rollout, feature flags, dark launches 7. **Performance** — Latency, throughput, cost budget, scaling assumptions 8. **Reliability** — Failure modes, recovery paths, SLO targets 9. **Testing** — Unit, integration, regression, chaos, load 10. **Maintainability** — Code patterns, documentation, onboarding cost for new contributors 11. **Migration** — Backward compatibility, data migration, rollout/rollback ordering ## Output format For each section, the review returns: - `Pass` — meets bar - `Risk` — works but has identifiable risk → suggested mitigation - `Block` — critical gap → must address before implementation ## R