writing-plans

# Writing Plans Write implementation plans that a developer with zero codebase context can follow. Plans must be evidence-backed (paths verified), mode-appropriate (not over-engineered), and executable (every step has a verification command). Before planning, verify that the user's requirements are clear enough to plan against. **Announce at start:** "I'm using the writing-plans skill to create the implementation plan." ## Gate 1: Requirements Clarity Gate Before classifying complexity, verify the request is plannable. A vague request produces a plan built on assumptions. **Fast pass-through**: If the request names specific files, describes concrete behavior changes, and has clear scope boundaries, proceed directly to Gate 2. Do not ask clarifying questions for obviously clear requests. **STOP and ASK** if any of these apply: | Trigger | What's Missing | Example | |---|---|---| | Vague action verb with no measurable outcome | Success criteria | "optimize the auth module" | | No scope boundary stated | What's in/out of scope | "refactor the codebase" | | Ambiguous target when multiple exist | Which component | "update the API" (when 5 APIs exist) | | Change type unclear (behavior vs performance vs structure) | Intent | "improve error handling" | | Backward compatibility unstated for public interface changes | Constraint | "change the response format" | **Clarification protocol:** 1. State what you understood (to confirm or correct) 2. Ask only about WHAT the user wants...