Compresses the staff/principal-engineer planning function — turning a fuzzy initiative into a written RFC/design doc, Architecture Decision Records (ADRs), three-point effort estimates, a weighted trade-off matrix, a likelihood×impact risk register, and a phased rollout/backout plan, plus a stakeholder-ready one-pager — BEFORE any code is written. Runs a gate-sequenced lifecycle (triage → framing → options → trade-off → ADRs → estimation → risk → rollout) where deterministic scripts block advancing past gaps. Use whenever the user is starting, scoping, planning, architecting, or estimating a new project, feature, migration, refactor, or initiative — even if they don't explicitly ask for a "plan" or "RFC"; especially when they say "how should I approach X", "should I use A or B", "how long will X take", or "what could go wrong with X". Also use when they want a design doc, ADR, effort estimate, trade-off analysis, risk register, rollout plan, or an exec one-pager. Right-sizes the artifact set (micro/standard/h
2026-06-23