plan-critic
Challenge a proposed implementation plan before execution: scope, dependency order, PR slicing, risk, test adequacy, operational readiness. Use when the user asks to review, critique, or stress-test a
Files1
View on GitHubSKILL.mdskills/plan-critic/SKILL.md
GitHubPlan Critic
Challenge an implementation plan before anyone executes it.
Input collection
If missing, ask for:
- Plan text to review (required)
- Source document (RFC URL/path) if available
- Constraints (time, risk tolerance, no-behavior-change, testing limits)
Review checklist
Evaluate and report on:
- Scope clarity (in/out, non-goals, hidden expansion risk)
- Dependency order (technical and process dependencies)
- PR slicing quality (too broad, too coupled, conflict-prone)
- Risk coverage (runtime regressions, migration risk, rollback viability)
- Test adequacy (targeted tests, hotspot checks, missing integration/E2E)
- Decision traceability (explicit decisions vs assumptions)
- Operational readiness (release approach, feature flags, observability/support)
- Contract safety (does any step change an externally consumed surface without the
contract-guardtreatment?)
Output format (exact order)
- Verdict (
Go,Go with changes, orNo-go) - Critical Gaps (must-fix)
- Important Improvements (should-fix)
- Revised PR Sequence (if needed)
- Minimum Test Gate
- Approval Questions
Rules
- Be direct and evidence-based.
- Prefer minimal changes to make the plan executable.
- Flag assumptions explicitly.
- If the plan is already solid, say so and keep only minor improvements.