← ClaudeAtlas

issue-intakelisted

Use when the ready-issue queue is low or a delivery wave is closing, when a defect/finding surfaces mid-session (runtime failure, review discovery, repeated manual step), or when deciding whether an observation deserves a GitHub issue. Also use when authoring any issue body.
fagemx/edda · ★ 34 · AI & Automation · score 75
Install: claude install-skill fagemx/edda
# Issue Intake Keep the delivery queue fed with issues that are worth doing and machine-ready — without the operator. Every issue this engine ships is born in the format parallel-wave Layer 1 judges: **named surface + machine-checkable doneWhen**. The body contract lives once in [templates.md](templates.md) — issue-create and fleet-epic-split emit the same shape and only point here; no parallel body formats. Composes with fleet-orchestrate (discovery rail) and parallel-wave (delivery). ## Sources — check in this order | Source | Trigger | Cost | |---|---|---| | Review exhaust | every review round's FOLLOW-UP ISSUE findings | free | | Runtime scars | any failure the pipeline itself hits (stale transitions, misclassification, lost state, timeout patterns) | free | | Self-improvement | any manual controller step repeated ≥2 times becomes a roadmap candidate | free | | Scheduled recon | ready queue < 3 at wave close → run a read-only campaign (charter: fixed object, rotating lenses — correctness / concurrency / data-loss / false-green tests; one reviewer per cell) | paid | | Epic split | operator-signed goal → fleet-epic-split into atomic issues | paid, operator-gated | A finding observed mid-session is filed (or parked as a candidate) **in the same session** — findings that stay in the transcript are lost. ## Promotion ladder candidate → verified finding → draft → **ready**. Never skip a rung. | To reach | Requires | |---|---| | verified finding | expected vs actual on a