goal-planner

# Goal Planner ## Purpose Create a clear goal contract for standard or deep frontend work before implementation begins. This skill exists to prevent ambiguous or large requests from turning into unfocused coding. It defines what the user wants, what is in scope, what is out of scope, which constraints apply, and what observable conditions mean the task is done. ## When To Use Use this skill only after `AGENTS.md` and `common/prompt-intent-routing-rules.md` classify the task as `Standard Workflow` or `Deep Workflow`. Use this skill when: - the user asks for a multi-file feature; - the user asks for a new screen, flow, or frontend capability; - the user asks for architecture, greenfield project creation, or broad redesign; - the request is ambiguous enough that implementation would require guessing the goal; - the task needs a compact goal before execution planning; - the task needs a durable goal contract because work may span multiple slices. ## When Not To Use Do not use this skill for `Lightweight Workflow` prompts, including: - one small bug; - one obvious typo; - one obvious type error; - one small styling adjustment; - one isolated component change; - one direct file-scope edit; - one local refactor with clear boundaries. Do not use this skill to implement code, install tools, scaffold projects, rewrite architecture, or perform visual QA. If a lightweight task reveals hidden scope, escalate first using `common/prompt-intent-routing-rules.md`, then use this sk...