ChristopherAlphonse Plan Review Scope
Challenge the plan before detailed review begins.
Guardrails
- Find the minimum complete change that achieves the stated goal.
- Do not expand or reduce scope without a user decision.
- Treat speculative future flexibility as a scope risk.
- Mark out-of-scope work explicitly.
Review Questions
Answer these from the plan and codebase:
- What existing code, flows, services, or UI already solve part of this problem?
- What is the minimum complete change that achieves the stated goal?
- Does the plan touch more than 8 files or introduce more than 2 new classes/services?
- Does the plan create duplicated flows instead of reusing existing ones?
- Does it defer bounded work that should be included now, such as error handling, tests, or observability?
- Are any existing TODOs blocking or related to this work?
Decision Protocol
If scope reduction, expansion, or a major simplification is warranted, ask one decision question with:
- Plain-English problem
- Recommendation
- 2-3 options
- Tradeoffs for each option
- Completeness score from 1-10
Once the user decides, commit to that scope for the rest of the review.
Output
Return:
- What already exists
- Scope recommendation
- Accepted scope
- NOT in scope
- Related TODOs
- Remaining scope risks
Install:
npx skills add ChristopherAlphonse/calphonse-skills --skill plan-review-scope