← ClaudeAtlas

plan-with-review-pagelisted

Use before a change that touches many files, needs many steps, or has open design choices. Also use it when the user says "plan this first", "make a plan", "think this through", or "do not code yet". Explores the code read-only, finds the cause, asks the open decisions with the recommended option first, and writes one plan. The plan explains the problem, the evidence, the cause, the fix and why it works, the alternatives, the risks, and the decisions. Builds a self-contained HTML review page from a template, and checks the page with a validator. Not for checking finished work (use `verify-and-review`).
theonly1me/shadowclone · ★ 26 · Code & Development · score 85
Install: claude install-skill theonly1me/shadowclone
# Plan With a Review Page ## Use when A change touches many files, needs many steps, or has a design choice that belongs to the user. An approved plan stops work in the wrong direction. A small and clear change does not need this skill. The plan is the reference for the person who approves the work. That person may not have read the conversation, so the plan alone must let them judge the change. ## Gates 1. Are you read-only until the user approves? Before approval, write only the plan file and the review page. 2. Did you read the code, the documents, and the history before you asked? Never ask what the code can answer. 3. Did you ask in rounds until no decision was open? Each risky choice, such as a skip, a block, a fallback, or a default, belongs in a round. Each round has at most 4 questions, each with 2 to 4 options and the recommended option first. 4. Can a reader who missed the conversation judge the change from the plan alone? The plan gives the problem, the evidence, the cause, the fix, why it works, and the alternatives. 5. Does each cause have a change that removes it and a check that proves the fix? 6. Is there one plan file for this conversation, and does its page pass `scripts/validate-page.mjs` with 0 errors? ## Process ### Explore 1. Read the code that the request touches, and the instructions of the repository for that code. 2. Reproduce or observe the problem. Record each fact with its source: a `path:line`, a command and its output, or a URL. Label e