fable-new-issue

# fable-new-issue Delegate issue drafting to a **Fable 5** subagent, then file it from the main agent. The subagent only researches and composes — it never files, edits files, or posts to GitHub; the main agent handles filing and all follow-on actions. ## Input Same as `new-issue`: - A description of the bug/feature/task to file. - **Nothing** — derive from the current conversation. Since the subagent can't see this conversation, the main agent first writes a faithful summary of the discussed bug/design/follow-up (with any file paths or symbols already named) to a scratchpad file and hands that path to the subagent as the source description. - Optionally `owner/repo` or a repo path when the issue belongs elsewhere. ## Steps ### 1. Resolve the drafting procedure Locate the `new-issue` SKILL.md the subagent must follow — prefer the project-local copy over the global one: 1. `<repo>/.claude/skills/new-issue/SKILL.md` (if it exists) 2. `~/.claude/skills/new-issue/SKILL.md` 3. Any other install location — search by name, e.g. `ls ~/.claude/plugins/*/skills/new-issue/SKILL.md` (plugin-marketplace installs live under a plugin directory, not `~/.claude/skills/`). Record the absolute path. If none of these resolves, stop and tell the user. If the input is conversation-derived, write the scratchpad summary now (see Input). Do NOT pre-research or pre-draft the issue yourself — the subagent owns steps 1–6 of the procedure up to (but not including) the `gh issue create` call. ##...