review-plan

Harden implementation plans with simplification and adversarial review before coding.

1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/spinlockdevelopment/dev-setup --skill review-plan-spinlockdevelopment
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-plan
Source: https://github.com/spinlockdevelopment/dev-setup/tree/main/plugins/spindev-core/skills/review-plan
Command: npx skills add https://github.com/spinlockdevelopment/dev-setup --skill review-plan-spinlockdevelopment

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Development plans generated by planning assistants can drift in scope, duplicate work, miss tests, or hide risky assumptions; this Skill hardens those plans before implementation by running structural simplification, an adversarial cross-model review, and by batching long plans into checkpointed review units so reviews are meaningful and actionable.

Core Features & Use Cases

  • Simplification pass: Detects DRY/YAGNI/scope creep, granularity issues, missing tests, and repeated work and produces concrete revision suggestions.
  • Adversarial cross-model review: Invokes codex adversarial-review verbatim to challenge assumptions and surface design risks that same-model self-review misses.
  • Checkpoint injection & parallel tracks: For long or multi-track plans, inserts checkpoint blocks and supports one worktree per parallel track so reviews stay scoped and reproducible.
  • Use case: After a plan is generated by superpowers:writing-plans, run this Skill to get a triaged set of edits, commit-safe revisions, and checkpoint markers so implementers can execute with batched code-quality reviews.

Quick Start

Run /review-plan on the generated plan to get simplification suggestions, adversarial findings, and optional checkpoint injection.

Frequently Asked Questions about review-plan

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

FAQPage Schema
How do I prevent design drift in implementation plans before coding?

To prevent design drift, you can harden implementation plans by running structural simplification checks and adversarial cross-model reviews to catch scope creep and risky assumptions before any code is written.

What is an adversarial cross-model review for a development plan?

An adversarial cross-model review uses a different model to critique a plan's assumptions and surface design risks that same-model self-review often misses, ensuring the implementation strategy is robust.

How do I add checkpoint reviews to a long git implementation plan?

You can add checkpoint reviews to a long implementation plan by injecting checkpoint blocks and using one git worktree per parallel track, batching the plan into scoped and reproducible review units.

Does reviewing a plan require git commits and codex access?

Yes, hardening a plan requires the ability to commit the plan to git and access to /codex:review and /codex:adversarial-review to execute the simplification and adversarial critique steps.

What is the best way to simplify a development plan and remove duplicated work?

The best way to simplify a development plan is to run a DRY and YAGNI simplification pass that detects scope creep, missing tests, and repeated work, then applying the user-approved edits to the committed plan.

Can I use worktrees to review parallel tracks in a multi-track plan?

Yes, you can use one worktree per parallel track in a multi-track plan to keep checkpoint reviews scoped and reproducible, ensuring each track is evaluated independently before implementation.