plan-ceo-review

To review an ambitious feature plan, enforce a structured, risk-aware evaluation workflow that mandates a Step 0 system audit, error and rescue mapping, and explicit documentation of what is not in scope before detailing architecture diagrams or deployment readiness.

Nuclear-scope planning is a structured evaluation method that enforces choosing between three modes: SCOPE EXPANSION, HOLD SCOPE, or SCOPE REDUCTION. It applies to system architecture reviews by requiring a committed single plan and a system audit before proceeding with detailed risk analysis.

To map edge cases and rescue flows during an architecture audit, you must generate comprehensive error and rescue mappings alongside ASCII architecture diagrams. This identifies potential failure points and defines recovery procedures before system activation.

Mandatory documentation artifacts for deployment readiness include explicit lists of what is NOT in scope, what already exists, the dream-state delta, comprehensive architecture diagrams, and detailed test plans to ensure a risk-aware evaluation.

You should choose scope reduction over scope expansion during a plan review when the system audit and risk analysis reveal constraints that prevent safely handling an ambitious feature set, ensuring you commit to a single, viable plan.

Yes, you can use this workflow for an existing system audit because it mandates a Step 0 system audit to evaluate what already exists, assess security considerations, and map the dream-state delta before selecting an expansion, hold, or reduction mode.