fable-validate

# fable-validate Delegate issue validation to a **Fable 5** subagent, then act on its verdict in the main agent. The subagent only validates — it never edits files or the issue; the main agent handles all follow-on actions. ## Input Same as `validate-issue`: - Full URL: `https://github.com/<owner>/<repo>/issues/<N>` - Short form: `#<N>` or bare `<N>` (current repo) - `owner/repo#N` - **Nothing** — default to the latest open issue in the current repo. ## Steps ### 1. Resolve the validation procedure and the issue Locate the `validate-issue` SKILL.md the subagent must follow — prefer the project-local copy over the global one, since a repo may customize the procedure: 1. `<repo>/.claude/skills/validate-issue/SKILL.md` (if it exists) 2. `~/.claude/skills/validate-issue/SKILL.md` 3. Any other install location — search by name, e.g. `ls ~/.claude/plugins/*/skills/validate-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 user referenced an issue, note the number/repo but do NOT fetch or pre-validate it yourself — the subagent owns steps 0–7 of the procedure, including fetching. If no issue was referenced, the subagent resolves the latest open issue itself per the procedure. ### 2. Dispatch the Fable 5 validation subagent Do not validate the issue yourself first — the subagent owns the validation. Snapshot `git status --porcelain` before...