writing-plans

@acaprino

Turn a confirmed design or spec into a comprehensive, task-by-task implementation plan. Use after brainstorming when the task involves 3+ files or multiple implementation steps. A conversation that evolved through brainstorming into a confirmed design MUST invoke this skill before writing any code, even if the user never explicitly said "write a plan". TRIGGER WHEN: (1) user says 'write a plan', 'create a plan', 'implementation plan', 'plan this', 'break this into tasks'; (2) the conversation has produced a design, spec, or set of decisions and is naturally transitioning toward implementation -- e.g., the user approved an approach, confirmed architecture choices, or said "let's do it" / "go ahead" / "proceed". DO NOT TRIGGER WHEN: user wants to brainstorm first (use brainstorming), wants to execute an existing plan (use executing-plans), or is doing a simple one-file change.