plan-review-scope

Identify minimum viable scope for software plans with guardrails and decision options.

1|Updated May 7, 2026

Search Tags:#planning #decision #review #scope #guardrails #risk

Ready to run

npx skills add https://github.com/ChristopherAlphonse/calphonse-skills --skill plan-review-scope

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-review-scope
Source: https://github.com/ChristopherAlphonse/calphonse-skills/tree/main/plan-review-scope
Command: npx skills add https://github.com/ChristopherAlphonse/calphonse-skills --skill plan-review-scope

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Challenge the project plan to identify the minimum viable changes and prevent scope creep before detailed engineering begins.

Core Features & Use Cases

Guardrails-driven scope refinement: assess the breadth of changes against predefined constraints.
Decision protocol facilitation: surface options, tradeoffs, and a recommended scope with acceptance criteria.
Artifact output: delta scope, not-in-scope items, related TODOs, and risk notes.

Quick Start

Install and run the plan-review-scope skill to begin an immediate scoped review of your plan.

Frequently Asked Questions about plan-review-scope

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I prevent scope creep during a software plan review?▼

A plan scope review identifies the minimum viable changes needed for a feature or bug fix, preventing scope creep before detailed engineering begins. It assesses proposed changes against predefined guardrails to ensure focused and manageable development.

What outputs do I get from a scoped plan review?▼

A scoped plan review produces four specific outputs: accepted scope, not-in-scope items, related TODOs, and remaining risk notes. These artifacts capture decision options and tradeoffs to guide final project decision-making.

Can I use guardrails to limit changes for a bug fix plan?▼

Yes, you can apply guardrails to limit changes for a bug fix plan by constraining the scope to predefined limits such as eight files or two new classes. This refines the scope and surfaces tradeoffs for the recommended changes.

What is the best way to capture decision options for a feature change plan?▼

The best way to capture decision options for a feature change plan is to apply a decision protocol that surfaces options, tradeoffs, and a recommended scope with acceptance criteria. This locks the scope before the actual review process.

Does plan scope review work for plan amendments across different codebases?▼

Yes, plan scope review works for plan amendments across different codebases and team reviews. It applies guardrails to flag scope risks and identify the minimum viable changes needed regardless of the specific codebase or team structure.