Sharpens and stress-tests an existing plan file through multiple codebase-grounded review passes, editing it in place and recording every finding and iteration in cross-referenced companion files. Use this skill whenever the user wants to iterate on, refine, tighten, or improve a plan — including terse commands like "iterate", "refine it", or "iterate for correctness" where a plan is present in context. Also use it when the user asks to verify, validate, or confirm feasibility of an approach (e.g., "can you verify this will work", "check this for correctness", "is this sound") — the defining signal is that the user wants critical evaluation of a proposed approach, not execution of it. Produces two companion files in an artifacts/ subfolder next to the plan: review-findings.md (every finding raised and how it was resolved) and review-iteration-history.md (round-by-round record of specialists engaged and plan changes applied). Do NOT use for implementing plan steps, generating new plans from scratch, writing test plans, code review, or bug investigation.
Install with
Claude CodeCodexCursorGitHub CopilotGemini CLI
Supported by the Atlas install prompt. Skill-specific requirements vary.
Skill stats
Skills1CategoryGeneralStars0
About this skill
Sharpens and stress-tests an existing plan file through multiple codebase-grounded review passes, editing it in place and recording every finding and iteration in cross-referenced companion files. Use this skill whenever the user wants to iterate on, refine, tighten, or improve a plan — including terse commands like "iterate", "refine it", or "iterate for correctness" where a plan is present in context. Also use it when the user asks to verify, validate, or confirm feasibility of an approach (e.g., "can you verify this will work", "check this for correctness", "is this sound") — the defining signal is that the user wants critical evaluation of a proposed approach, not execution of it. Produces two companion files in an artifacts/ subfolder next to the plan: review-findings.md (every finding raised and how it was resolved) and review-iteration-history.md (round-by-round record of specialists engaged and plan changes applied). Do NOT use for implementing plan steps, generating new plans from scratch, writing test plans, code review, or bug investigation.
Quick start
Copy the install prompt. Use the green button above this README.
Send it to your agent. Paste it into your coding agent’s chat and send.
Review the setup. Your agent checks the skill’s instructions, requirements, and installation scope.
Sharpens and stress-tests an existing plan file through multiple codebase-grounded review passes, editing it in place and recording every finding and iteration in cross-referenced companion files. Use this skill whenever the user wants to iterate on, refine, tighten, or improve a plan — including terse commands like "iterate", "refine it", or "iterate for correctness" where a plan is present in context. Also use it when the user asks to verify, validate, or confirm feasibility of an approach (e.g., "can you verify this will work", "check this for correctness", "is this sound") — the defining signal is that the user wants critical evaluation of a proposed approach, not execution of it. Produces two companion files in an artifacts/ subfolder next to the plan: review-findings.md (every finding raised and how it was resolved) and review-iteration-history.md (round-by-round record of specialists engaged and plan changes applied). Do NOT use for implementing plan steps, generating new plans from scratch, writing test plans, code review, or bug investigation.
About this listing
Category
General
Reported license
MIT
Listing language (estimated)
English
Review status
Not individually reviewed
Agent compatibility
Atlas installation supports Claude Code, Codex, and Cursor. Skill-specific dependencies and features are checked during setup.