openspec-planlisted

## Purpose The one skill that keeps GSD's native requirement-coverage machinery (plan-checker Dimension 1, the `gap-analysis` capability) working unmodified on OpenSpec-sourced requirements, by keeping `.planning/REQUIREMENTS.md` a faithful, mechanical projection of `openspec/changes/<id>/specs/` — never hand-authored once this integration is active. ## Invocation conditions - Automatically as the `plan:post` gate's `agentVerdict` check (advisory scenario-coverage report). - Directly, to force a `REQUIREMENTS.md` re-sync without waiting for the next `/gsd-plan-phase` (e.g. after `openspec-repair` updated a spec). ## Required inputs - `.planning/phases/<NN>-<slug>/<NN>-OPENSPEC-LINK.md` (must exist — this skill does nothing for phases with no linked change). ## Files read - `openspec/changes/<change_id>/specs/**/spec.md` (or `openspec/specs/**/spec.md` post-archive) - `openspec/changes/<change_id>/tasks.md` - `.planning/phases/<NN>-<slug>/<NN>-<PP>-PLAN.md` (all plans generated for the phase) - `.planning/openspec/id-registry.json` ## Files this skill may write - `.planning/REQUIREMENTS.md` — **only** the entries whose source is an OpenSpec requirement ID (tagged with a trailing `<!-- source: openspec:<change_id> -->` comment so a human-authored requirement already in the file is never overwritten or reordered). - `.planning/openspec/id-registry.json` (delegates actual ID injection to `openspec-traceability`; this skill only reads the registry, it does not assign IDs