openspec-triagelisted

Triage an exploration report into real GitHub Issues. This is the mandatory bridge between `opsx:explore` (open-ended thinking, produces a report, never scaffolds a change) and `opsx:propose` (scaffolds a change around a real Issue). See `openspec/NOTAIRE-ADAPTATIONS.md` for why this step exists: `scripts/validate-sdlc-plan.sh` mechanically rejects a proposal whose Issue number does not resolve to a real, open GitHub Issue, so a report entry that never went through triage cannot reach Gate 1. This skill is project-owned, not generated by the `openspec` CLI. It is not touched by `openspec update` and does not appear in `skills-lock.json`. **Do not implement anything in this skill.** Its only output is a candidate-issue markdown file and, once the user confirms, real GitHub Issues. No code, no OpenSpec change scaffolding. ## When to use this skill - The user has an exploration report (from `opsx:explore`, or any markdown file under `openspec/` listing candidate features/gaps) and wants to move toward implementation. - The user asks to turn a report, a backlog, or "the gaps we found" into issues. - `opsx:propose` is about to scaffold a change and the Issue it would reference does not exist yet. ## Steps 1. **Identify the source report.** Ask for the path if not given. Read it in full — do not summarize from a partial read, the candidate list must be traceable back to every entry in the report. 2. **Extract one candidate per feature/gap**, close to the shape