Software Plan Review

Overview

Review an existing software delivery plan with the goal of making it clearer, more complete, more correct, and more actionable for implementation. This skill complements the software-plan-creation skill, it evaluates plans that skill produces. The primary output is a structured critique that identifies strengths, weaknesses, risks, sequencing problems, and concrete improvements.

Prefer critique plus revision guidance over rewriting the full plan unless the user explicitly asks for a rewritten version.

Use this skill when the user already has a plan artifact and wants critical review rather than initial drafting. Do not use it when the main task is to write production code, create a design from scratch, review source code, or create a new plan.

Expected Plan Structure

Plans produced by the software-plan-creation skill follow this structure. Use it as the reference when checking whether sections are present and well-formed:

1. Title and Summary, what is being delivered and the value it provides
2. Design Reference, the source design name and path for traceability
3. Prerequisites, dependencies, access, open questions that must be resolved before work begins
4. Phases, numbered phases, each containing:
   • Scope, what the phase delivers
   • Tasks, numbered, concrete, actionable tasks
   • Testing, testing approach for the phase, including TDD slices when applicable
   • Exit criteria, what must be true when the phase is complete
5. Testing Strategy, overall approach covering unit, integration, and end-to-end testing; TDD guidance where applicable
6. Documentation, what documentation is needed and when
7. Risks and Mitigations, table with Risk, Impact, and Mitigation columns
8. Definition of Done, checklist of conditions for the entire plan to be considered complete

Not every plan will have all sections. Assess whether omitted sections are genuinely unnecessary or represent gaps.