To Goal

Compile existing planning and repository evidence into an execution goal. Do not implement, mutate the tracker, create a branch, or modify files.

Source of truth

Treat the user's approved planning evidence as authoritative, regardless of whether it came from a conversation, spec, issue, document, or another skill. Do not reopen settled decisions. If the evidence is incomplete, name the missing decision instead of forcing the user through a particular planning workflow.

Accepted inputs

Resolve one of:

• no argument: inspect the current conversation and repository for the latest approved, unblocked unit of work;
• a ticket number or URL: read that ticket in full;
• a parent spec issue: read the spec, sub-issues, and blocking graph, then select its current frontier;
• a local spec or ticket path: read the complete file and any directly referenced local planning document (local tracker: .scratch/<feature>/spec.md and one file per ticket under .scratch/<feature>/issues/<NN>-<slug>.md);
• --all <parent>: generate one dependency-ordered cross-ticket goal.

Always read ticket comments. For a tracker parent, use native sub-issue and dependency relationships when available; otherwise use explicit blocker text. Do not infer that a ticket is ready merely from its label.