Revue de plan

Utilisez après avoir créé un plan pour identifier les lacunes, risques et questions avant l'implémentation.

Spar Skills Guide Bot
ProductiviteIntermédiaire
0022/07/2026
Claude CodeCursorWindsurf
#plan-review#critique#planning#risk-assessment

Recommandé pour


name: review-plan description: Use after creating a plan in plan mode to critique it for gaps, risks, and clarifying questions before implementation. Triggers on "review plan", "critique plan", "check my plan".

Review Current Plan

Conduct a thorough review of the plan created in the current session. Act as a meticulous technical reviewer and strategic advisor.

Prerequisites

This skill requires an active plan from plan mode. If no plan exists in context, inform the user they need to create a plan first using plan mode.

Review Dimensions

Systematically analyze the plan across:

  1. Completeness: Missing components, edge cases, error handling, dependencies not addressed
  2. Technical feasibility: Technical challenges, performance bottlenecks, architectural concerns
  3. Implementation clarity: Does each step have sufficient detail? Any ambiguity?
  4. Dependencies & prerequisites: External deps, tools, libraries, infrastructure requirements documented?
  5. Testing strategy: Testing approaches, validation criteria, quality checks defined?
  6. Documentation: Documentation requirements and knowledge transfer needs addressed?
  7. Security & compliance: Security considerations, compliance requirements noted?

(Enterprise-only dimensions — deployment/rollout, timeline realism, resource allocation/budget — were dropped for the solo-dev profile.)

Output Format

  1. Brief summary: Overall quality assessment and critical gaps (2-3 sentences max)

  2. Iterative questions: Ask clarifying questions one at a time using AskUserQuestion tool:

    • Context: What aspect you're questioning and why it matters
    • Current state: What the plan says (or doesn't say) about this
    • Impact: Why this decision matters for success
    • Provide multiple-choice options where applicable
  3. After each answer, either:

    • Ask the next critical question, or
    • Confirm the plan is comprehensive

Guidelines

  • Be direct and concise in feedback
  • Prioritize critical gaps over minor improvements
  • Focus on risks that could derail the project
  • Don't ask about things already clearly addressed in the plan
  • Stop questioning when all critical decisions are resolved

Reference Files

  • references/question-examples.md - Sample clarifying questions with context
Skills similaires