plan-tasklisted

Use BEFORE writing code for any multi-file or non-trivial change. Reads the relevant CLAUDE.md files, surfaces blind spots and architecture-moving questions, and emits a short plan that becomes the contract the work is graded against. Skip for one-line fixes, typos, and pure-docs edits.
NAVNAV221/ai-native-codebase · ★ 1 · Data & Documents · score 72

Install: claude install-skill NAVNAV221/ai-native-codebase

# Plan Task The cheapest bug to fix is the one you catch before the first edit. This skill runs a short unknowns pass and produces a plan, so the change is scoped on purpose rather than discovered halfway through. ## Steps 1. **Read the map.** Open the root `CLAUDE.md` and the `CLAUDE.md` of every directory the change will touch. Note the conventions that apply. 2. **Surface unknowns.** Write down what you don't yet know: unclear requirements, ambiguous edge cases, decisions that move the architecture. Ask the human about the ones that would change the approach - don't silently default them. 3. **Name the risk shape.** What class of bug does a change like this usually ship? (schema drift, an unhandled async path, a missing call-site, a broken migration.) Plan a check for it. 4. **Emit the plan.** A short `## Plan` block: the goal, the files you expect to touch, the order, and "done when" criteria. Keep it to what a reviewer could hold you to. ## Output A `## Plan` block in the conversation. It is a contract, not prose - every later step should trace back to a line in it.