# Plan Review Scope

> Challenges implementation scope before detailed engineering review.

- Skill: `christopheralphonse/plan-review-scope` (Agent Skill)
- Install (CLI): `npx skillmds@latest add christopheralphonse/plan-review-scope`
- Raw SKILL.md: https://api.skillmd.com/api/skills/christopheralphonse/plan-review-scope/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: ChristopherAlphonse (https://skillmd.com/u/christopheralphonse)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/christopheralphonse/plan-review-scope

---


# 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:

1. What existing code, flows, services, or UI already solve part of this problem?
2. What is the minimum complete change that achieves the stated goal?
3. Does the plan touch more than 8 files or introduce more than 2 new classes/services?
4. Does the plan create duplicated flows instead of reusing existing ones?
5. Does it defer bounded work that should be included now, such as error handling, tests, or observability?
6. 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``