fable-new-issue-looplisted

# fable-new-issue-loop Chain fable-new-issue → validate-issue-loop into one autonomous run: a Fable 5 subagent drafts the issue, the main agent files it, and the loop drives it to a reviewed PR without a human in between. **This skill is `new-issue-loop` with a different front of the chain.** Follow the `new-issue-loop` skill for the full procedure: the complete-issue rule, the input contract, the stop gate, the handoff to validate-issue-loop (explicit issue reference, `owner/repo#N` when filed cross-repo), the report format, and the Red Flags. Apply only the deltas below. ## Deltas from new-issue-loop - **Step 1, front of the chain.** Invoke the `fable-new-issue` skill (Skill tool, `skill: fable-new-issue`) in place of `new-issue`. Let it run its full process (Fable 5 subagent draft, duplicate gate, spot-check, filing) and capture the created issue number from its report. - **Step 2, stop gate.** new-issue-loop's stop gate applies with one extra row for the Fable draft; the effective table: | Condition | Action | |---|---| | fable-new-issue found an existing open issue/PR already covering it (no issue filed) | **STOP.** Report the duplicate and the offer to update/comment instead — merging scopes is a human call. | | The conversation held several distinct candidates | If one clearly converged, file it and **continue the chain with it**; the unfiled candidates go in the final report. If none clearly converged, **STOP** — report the candidates and ask which to file. Never