issue-ingest

Issue Ingest Protocol

This protocol is loaded on demand by the architect runtime. The architect prompt keeps only activation, action, and hard safety constraints; the full execution details live here.

MODE: ISSUE_INGEST

Activates when: user invokes /swarm issue <url>; OR architect receives [MODE: ISSUE_INGEST issue="<url>"] signal.

Purpose: ingest a GitHub issue, localize root cause, and produce a resolution spec. The issue URL points to a GitHub issue that describes a bug, feature request, or task to be resolved.

Flags parsed from signal:

• plan=true → after spec generation, transition to MODE: PLAN (create implementation plan)
• trace=true → the issue-trace runtime hook automatically drives the standard PLAN → CRITIC-GATE → EXECUTE → commit-pr ladder (implies plan=true)
• noRepro=true → skip the reproduction step below

Phase 1: INTAKE

1. Fetch the issue body using the GitHub CLI (gh issue view <N> --repo <owner>/<repo> --json title,body,labels,assignees,comments) or web fetch.
   • If the issue cannot be fetched (404, private repo, no gh auth, or the argument resolves to a PR not an issue), report the blocked operation explicitly and do not proceed on empty intake; fall back to any pasted issue text the user provided. Closed-issue cases proceed but note the closed state.
2. Read .swarm/issue-reference.json as the authoritative source for the issue URL, owner, repo, number, and flags (plan/trace/noRepro). If absent, fall back to the URL from the mode signal string.
3. Parse the issue into a normalized Intake Note with four required fields:
   • Observed behavior: what the issue reports
   • Expected behavior: what should happen instead
   • Reproduction steps: how to trigger the issue (may be absent; flag with [NEEDS REPRO] if missing)
   • Environment: platform, version, configuration context
4. If any required field is missing and cannot be inferred from context, flag as [NEEDS REPRO].
5. Attempt a minimal reproduction of the reported issue: record the exact commands and their output. Skip this step when noRepro=true (set via --no-repro); in that case, note that reproduction was skipped and proceed on the issue text alone. When trace=true, the issue-trace engine requires reproduction evidence OR a typed --no-repro waiver before it can leave localization and transition to PLAN: after attempting reproduction, call record_issue_reproduction with the issue number, performed: true, and the recorded commands/output_summary so the gate is satisfied. A performed: false receipt is recorded but does NOT satisfy the gate.
6. Ask the user clarifying questions one at a time, max 6 per intake, when the issue text is ambiguous; otherwise flag the item with markers like [NEEDS REPRO] or [NEEDS CLARIFICATION] and proceed.
7. Exit when the Intake Note is complete or all missing fields are flagged.