Menu
Double check / critique implementation plan with fresh eyes
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | double-check-plan |
| description | Double check / critique implementation plan with fresh eyes |
| disable-model-invocation | true |
Great, now I want you to carefully read over the plan/spec and compare against the codebase with "fresh eyes," looking super carefully for any obvious bugs, errors, problems, issues, confusion, etc. Think through how best to implement this elegantly given our architecture and goals. Also keep in mind that this is not an MVP - so don't skip anything.
CRITICAL: This reviews and fixes the PLAN DOCUMENT ONLY. Do NOT edit, create, or modify any source code files. Only the plan/spec file itself should be edited. If you find issues in the plan, fix them in the plan. Do NOT implement the plan or write any code.
Response format:
Do not rush to a verdict. Read all relevant code first, trace through edge cases, and only then decide. I am pushing you to do a genuinely thorough review and not just lazily rubber-stamp it. Make sure you think deeply, then ultrathink some more.
$@
Orchestrates the full idea-to-ship workflow. Use when the user has a new idea, feature, or project and wants guided step-by-step progress. Triggers on "I have an idea", "let's build", "new feature", "start a project", or when the user wants to follow the complete workflow from concept to code.
Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on source code — never implements, fixes, or refactors anything itself. Use when asked to audit a codebase, find improvement opportunities (bugs, security, performance, test coverage, tech debt, migrations, DX), suggest features or where to take the project next (roadmap, product direction), or generate handoff plans for another agent to implement.
Self-driving version of grill-with-docs. Runs an auto-grill loop (auto-selects recommended options without asking) while creating ADRs and glossary entries via domain-modeling as decisions resolve. Use when the user says "auto-grill with docs", "grill and decide with docs", or invokes /grill-with-docs-auto.
Long-running iterative development loops with pacing control and verifiable progress. Uses .scratch/<plan>/ structure where each plan has a PRD.md and issues/. Use when tasks require multiple iterations, many discrete steps, or periodic reflection with clear checkpoints; avoid for simple one-shot tasks or quick fixes.
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
