fableplan

# fableplan Delegate planning to a **Fable 5** Plan subagent, then build from its plan in the main agent. The main agent does the building — the subagent only plans. ## Input The user provides a task description, and optionally a GitHub issue: - A task in prose ("fableplan adding X to Y"). - A GitHub issue reference — full URL, `#<N>`, bare `<N>`, or `owner/repo#N`. When present, the plan is also posted as an issue comment. - If neither is obvious, ask the user what to plan before dispatching. ## Steps ### 1. Resolve the GitHub issue (only if one is referenced) If the user named an issue, fetch it so the subagent plans against the real requirements, not a paraphrase: ``` gh issue view <N> --json number,title,body,url ``` For the `owner/repo#N` form (or a full URL to another repo), add `-R owner/repo` — a bare `gh issue view <N>` only resolves against the current repo. If the command fails (wrong number, no auth, no repo), stop and tell the user — never proceed by planning against your paraphrase of an issue you couldn't fetch. Record the issue number and URL — you'll need them in step 4. If no issue is referenced, skip this and step 4's posting. ### 2. Dispatch the Fable 5 Plan subagent Do not re-plan the task yourself first — the subagent owns the plan. Snapshot `git status --porcelain` before dispatching (the tree may already be dirty), then call the Agent tool with: - `subagent_type`: `Plan` - `model`: `fable` (this is the whole point of the skill — the plan m...