[feature-runner] Extract protocol strings to references/runner-output-formats.md

[orioltf]

This was generated by AI during triage.

Parent

docs/issues/feature-runner/PRD.md

What to build

Create .claude/skills/implement-feature/references/runner-output-formats.md containing all verbatim output strings that the runner emits or embeds. Remove those strings from SKILL.md and replace each with a reference to the file by name.

The verbatim strings to extract are:

1. Progress line — Implementing issue N of M: <issue title>
2. Dependency conflict error block — the four-line Feature Runner error: dependency conflict detected. message (including the two indented detail lines and the resolution instruction)
3. Failure note — the full ## Comments markdown block appended to a failing issue file (including the blockquote attribution and the bold Feature Runner failure — sentence)
4. PR body template — the heredoc body passed to gh pr create (Feature section, Resolved issues list, and the 🤖 attribution line)
5. LOOP_COMPLETE signal — the bare LOOP_COMPLETE string with a note that it must appear on its own line

Each entry in references/runner-output-formats.md should have a short heading, the exact string (in a fenced code block where multiline), and one sentence explaining when the runner emits it.

SKILL.md procedural steps should reference the file by name rather than repeating the strings inline, reducing SKILL.md by approximately 50 lines.

Acceptance criteria

• .claude/skills/implement-feature/references/runner-output-formats.md exists and contains all five strings listed above
• Each entry has a heading, a fenced code block with the exact string, and a one-sentence context note
• SKILL.md no longer contains the verbatim strings inline; each step references references/runner-output-formats.md by name instead
• The procedural logic in SKILL.md is unchanged — only the literal strings move
• SKILL.md line count is reduced to approximately 160 lines or fewer

Blocked by

#80

Comments

This was generated by AI during triage.

Agent Brief

Category: enhancement
Summary: Extract verbatim runner output strings from implement-feature SKILL.md into a dedicated references/runner-output-formats.md file.

Current behavior:
Five verbatim output strings are embedded inline inside the procedural steps of the implement-feature skill: the progress line, the dependency conflict error block, the failure note markdown block, the PR body heredoc, and the LOOP_COMPLETE signal. Updating any of these strings requires editing the step prose rather than a named reference file.

Desired behavior:
A references/runner-output-formats.md file exists inside the implement-feature skill directory alongside SKILL.md. It contains all five strings, each under a short heading, in a fenced code block, with one sentence explaining when the runner emits it. The procedural steps in SKILL.md reference the file by name instead of repeating the strings inline. Procedural logic is unchanged — only the literal strings move.

Key interfaces:

• The implement-feature skill directory structure — gains a references/ subdirectory, consistent with the new-plugin and verify-spec skills which also use references/
• references/runner-output-formats.md — new file; its five sections must exactly match the strings currently in SKILL.md (no editorial changes to the strings themselves)

Acceptance criteria:

• references/runner-output-formats.md exists in the implement-feature skill directory and contains all five strings listed in ## What to build
• Each entry has a heading, a fenced code block with the exact string, and a one-sentence context note
• SKILL.md no longer contains the verbatim strings inline; each relevant step references references/runner-output-formats.md by name
• The procedural logic in SKILL.md is unchanged — only the literal strings move
• SKILL.md line count is reduced to approximately 160 lines or fewer

Out of scope:

• Changing the content of any output string (this is a structural move only)
• Adding new output strings or removing existing ones
• Updating docs/agents/feature-runner.md (it already documents the strings in prose)

---

PRD: docs/issues/feature-runner/PRD.md
Migrated from: docs/issues/feature-runner/10-references-split.md (source removed after migration)
Touched by PRs: #25, #32