requirement-phase-mapperlisted

# Requirement Phase Mapper ## Purpose Map every active `R`/`RI` manifest ID to exactly one Plan phase with a binary exit gate; flag any ID with no phase (an orphan) or more than one phase (a duplicate). Prevents a requirement from silently falling through Plan's own phase breakdown. This is a power skill, not a lifecycle phase. It is gate-bound: it runs at every Plan Exit Gate. ## Invocation Context Use this skill when: - Plan is about to finalize its `## Phases` section and set `orchestration.status: ready-for-next-phase` - a plan revision changes which phase covers which manifest IDs Do not invoke it before the brief's Requirement Manifest and at least one Plan phase both exist. ## What To Load **Foundation** (confirm in context; load if not already present): - Root `AGENTS.md` - `workflow/router.md` - `workflow/lifecycle.md` - `workflow/rules.md` **Minimum for invocation**: - This file - `references/output-schema.md` **Before starting work**: - `references/mapping-method.md` — how phase coverage is determined from a plan's `## Phases` section - The brief's Requirement Manifest (source of the active `R`/`RI` set) - The plan's `## Phases` section, in full ## Inputs - Active `R`/`RI` IDs from the brief. - The plan's `## Phases` section. ## Refusal / Stop Conditions Stop or return a failed mapping instead of approving when: - an active `R`/`RI` ID appears in no phase's stated manifest IDs, and no phase lists a hyphenated sub-label of it (e.g. `RI5-a` covers bas