@windyroad/itil 1.2.0 → 2.0.0-preview.1111

package/skills/manage-problem/agents/openai.yaml

@@ -0,0 +1,3 @@
+interface:
+  display_name: "WR ITIL: Manage Problem"
+  short_description: "Investigate, govern, and transition problem tickets."

package/skills/manage-rfc/SKILL.md

@@ -1,20 +1,20 @@
 ---
 name: wr-itil:manage-rfc
-description: Heavyweight RFC intake + lifecycle management following the ADR-060 Problem-RFC-Story framework. Creates new RFCs (delegates to /wr-itil:capture-rfc for the lightweight path), updates existing RFCs, transitions through proposed → accepted → in-progress → verifying → closed lifecycle, runs WSJF re-rank reviews, and refreshes docs/rfcs/README.md per the P062 / P094 contract pattern.
+description: Heavyweight RFC intake + lifecycle management following the "Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology" architecture rule Problem-RFC-Story framework. Creates new RFCs (delegates to /wr-itil:capture-rfc for the lightweight path), updates existing RFCs, transitions through proposed → accepted → in-progress → verifying → closed lifecycle, runs WSJF re-rank reviews, and refreshes docs/rfcs/README.md per the "Problem 062: `manage-problem` does not refresh `docs/problems/README.md` on single-ticket transitions; fast-path cache goes stale silently" problem / the "Problem 094: `/wr-itil:manage-problem` does not refresh `docs/problems/README.md` on ticket creation" problem contract pattern.
 allowed-tools: Read, Write, Edit, Bash, Grep, Glob, Task
 ---
 
 # Manage RFC Skill
 
-Create, update, or transition RFC tickets following the Problem-RFC-Story framework introduced by ADR-060 (accepted 2026-05-05). This skill is the heavyweight counterpart to `/wr-itil:capture-rfc` — it owns the full intake flow, lifecycle transitions, batch review, and README refresh.
+Create, update, or transition RFC tickets following the Problem-RFC-Story framework introduced by the "Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology" architecture rule (accepted 2026-05-05). This skill is the heavyweight counterpart to `/wr-itil:capture-rfc` — it owns the full intake flow, lifecycle transitions, batch review, and README refresh.
 
-**Related JTBDs**: JTBD-008 (primary — Decompose a Fix Into Coordinated Changes; this skill governs the lifecycle of decomposed work), JTBD-001 (extended scope — change-set-level governance), JTBD-101 (atomic-fix-adopter — every fix goes through an RFC per ADR-071; the RFC skills are invoked deliberately, not auto-fired, because RFC scope is direction-setting per ADR-073 — NOT because atomic fixes skip ceremony).
+**Related JTBDs**: the ": Decompose a Fix Into Coordinated Changes" user outcome (primary — Decompose a Fix Into Coordinated Changes; this skill governs the lifecycle of decomposed work), the ": Enforce Governance Without Slowing Down" user outcome (extended scope — change-set-level governance), the "Extend the Suite with New Plugins" user outcome (atomic-fix-adopter — every fix goes through an RFC per the "Every fix goes through an RFC" architecture rule; the RFC skills are invoked deliberately, not auto-fired, because RFC scope is direction-setting per the "RFC-first: a problem's fix implements its RFC; no implementation without a pre-existing RFC" architecture rule — NOT because atomic fixes skip ceremony).
 
 ## Output Formatting
 
-When referencing RFC IDs, problem IDs, ADR IDs, or JTBD IDs in prose output, always include the human-readable title on first mention. Use the format `RFC-006 (Decision homing implementation)`, not bare `RFC-006`. Tables with separate ID and Title columns are fine as-is.
+When referencing RFC IDs, problem IDs, ADR IDs, or JTBD IDs in prose output, always include the human-readable title on first mention. Use the format `the ": Implement + — re-home RFC decisions to ADRs and make RFC-first unconditional" release design (Decision homing implementation)`, not bare `the ": Implement + — re-home RFC decisions to ADRs and make RFC-first unconditional" release design`. Tables with separate ID and Title columns are fine as-is.
 
-**Brief-before-ID discipline at `AskUserQuestion` surfaces (P350).** When this skill emits an `AskUserQuestion` (transition-trigger ambiguity, scope-expansion approval, problem-trace ratification), the question/option/description text MUST inline what each referenced artefact is and what is at stake BEFORE naming it by ID. `RFC-NNN` / `P-NNN` / `ADR-NNN` / `JTBD-NNN` references are audit-trail annotations, NEVER carriers of meaning — the user reads the prompt without project filesystem access (mobile clients, accessibility tooling, notification surfaces) and cannot follow links. Every option's substance MUST be self-contained in the briefing prose + option `label` and `description`; IDs may appear ONLY after a self-contained explanation. Mirrors the canonical `/wr-architect:create-adr` Step 5 § 5a Rule 3 ("No IDs as explainers"). See also session memory `feedback_brief_before_id.md`.
+**Brief-before-ID discipline at `AskUserQuestion` surfaces (the "agent surfaces decisions to user using opaque IDs (P-numbers, ADR-numbers, JTBD-numbers) without explaining what they mean — empathy gap" problem).** When this skill emits an `AskUserQuestion` (transition-trigger ambiguity, scope-expansion approval, problem-trace ratification), the question/option/description text MUST inline what each referenced artefact is and what is at stake BEFORE naming it by ID. `RFC-NNN` / `P-NNN` / `ADR-NNN` / `JTBD-NNN` references are audit-trail annotations, NEVER carriers of meaning — the user reads the prompt without project filesystem access (mobile clients, accessibility tooling, notification surfaces) and cannot follow links. Every option's substance MUST be self-contained in the briefing prose + option `label` and `description`; IDs may appear ONLY after a self-contained explanation. Mirrors the canonical `/wr-architect:create-adr` Step 5 § 5a Rule 3 ("No IDs as explainers"). See also session memory `feedback_brief_before_id.md`.
 
 ## RFC Lifecycle
 
@@ -26,23 +26,23 @@ When referencing RFC IDs, problem IDs, ADR IDs, or JTBD IDs in prose output, alw
 | **Verifying** | `.verifying.md` | Work shipped, awaiting verification | All tasks complete; release marker present in `## Verification` |
 | **Closed** | `.closed.md` | Verified; RFC complete | User confirms verification; driving problem(s) Closed or trace-bounded-escape applies |
 
-Each transition is a `git mv` + Edit + restage + README refresh + commit per ADR-014.
+Each transition is a `git mv` + Edit + restage + README refresh + commit per the "Governance Skills Commit Their Own Completed Work" architecture rule.
 
 ## I1 enforcement at lifecycle transitions
 
-Per ADR-060 § Decision Outcome line 97 + § Confirmation criteria 1+2:
+Per the "Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology" architecture rule § Decision Outcome line 97 + § Confirmation criteria 1+2:
 
 | Transition | I1 enforcement |
 |------------|---------------|
 | capture-time (`/wr-itil:capture-rfc`) | **Hard-block** on missing/malformed/unresolved problem-trace. Deny logged to `logs/rfc-capture-denials.jsonl`. |
 | `proposed → accepted` | Hard-block if any `problems:` entry is no longer resolvable (deleted ticket file). Architect+JTBD re-review gate fires here. |
-| `accepted → in-progress` | **Hard-block** (irreversible state per ADR-060 line 97) if any traced problem is missing or orphan (Closed/Parked allowed only via `Refs: RFC-<NNN>` retro-pattern; bounded-escape carve-out applies to retrospective RFCs only — see capture-rfc Step 2 rationale). |
+| `accepted → in-progress` | **Hard-block** (irreversible state per the "Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology" architecture rule line 97) if any traced problem is missing or orphan (Closed/Parked allowed only via `Refs: RFC-<NNN>` retro-pattern; bounded-escape carve-out applies to retrospective RFCs only — see capture-rfc Step 2 rationale). |
 | `in-progress → verifying` | **Hard-block** (irreversible state) — same rules as `→ in-progress`. |
-| `verifying → closed` | **Advisory-with-escalation**: if driving problem is Closed/Parked AND no still-open trace exists, emit warning naming the trace history; proceed if user confirms (or AFK fallback per ADR-013 Rule 6). This is the bounded escape per ADR-060 line 97 — closing an RFC whose driving problem was already closed is the legitimate retrospective-completion path. |
+| `verifying → closed` | **Advisory-with-escalation**: if driving problem is Closed/Parked AND no still-open trace exists, emit warning naming the trace history; proceed if user confirms (or AFK fallback per the "Structured User Interaction for Governance-Skill Decisions" architecture rule Rule 6). This is the bounded escape per the "Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology" architecture rule line 97 — closing an RFC whose driving problem was already closed is the legitimate retrospective-completion path. |
 
 ## WSJF Prioritisation (RFC-level Phase 1)
 
-Per ADR-060 § Decisions Resolved: WSJF placement is **RFC-level for Phase 1**. Story-level WSJF is structurally impossible without story-mapping infrastructure (Phase 2 deferred).
+Per the "Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology" architecture rule § Decisions Resolved: WSJF placement is **RFC-level for Phase 1**. Story-level WSJF is structurally impossible without story-mapping infrastructure (Phase 2 deferred).
 
 **WSJF = (Severity × Status Multiplier) / Effort**
 
@@ -86,7 +86,7 @@ The argument shape determines the operation:
 - **`list`** → display (Step 8).
 - **Anything else** → halt with stderr directive directing the user to capture-rfc for new RFCs.
 
-The lightweight + heavyweight split per ADR-032 + ADR-010 amended Skill Granularity rule means manage-rfc does NOT host new-RFC creation inline. Capture-rfc owns the intake; manage-rfc owns lifecycle.
+The lightweight + heavyweight split per the "Governance skill invocation patterns — foreground + background with deferred-question resumption" architecture rule + the "Rename `wr-problem` Plugin to `wr-itil`" architecture rule amended Skill Granularity rule means manage-rfc does NOT host new-RFC creation inline. Capture-rfc owns the intake; manage-rfc owns lifecycle.
 
 ### 6. Update flow (bare `RFC-<NNN>`)
 
@@ -102,28 +102,28 @@ Apply the update — typical edits:
 - Adding `## Related` entries.
 - Updating `decision-makers` or `adrs` frontmatter when ADRs are referenced mid-RFC execution.
 
-**Do NOT add a "Considered Options / Alternatives Rejected" section to the RFC body.** Per ADR-070 (RFCs hold no independent decisions), every contested choice among ≥ 2 viable options is recorded as an ADR (inheriting the ADR-064 confirm gate + ADR-066 oversight marker) and referenced in the RFC's `adrs:` frontmatter — never re-argued in the RFC body. An RFC carries only scope, decomposition (sequencing/breakdown of already-decided work), and traces. The ADR-052 behavioural lint hard-fails any RFC body that contains a rejected-alternatives block without a matching `adrs:` reference.
+**Do NOT add a "Considered Options / Alternatives Rejected" section to the RFC body.** Per the "RFCs hold no independent decisions" architecture rule (RFCs hold no independent decisions), every contested choice among ≥ 2 viable options is recorded as an ADR (inheriting the ": Architect emits a Needs-Direction verdict; the main agent owns the AskUserQuestion" architecture rule confirm gate + the ": Human-oversight marker + `/wr-architect:review-decisions` drain for recorded decisions" architecture rule oversight marker) and referenced in the RFC's `adrs:` frontmatter — never re-argued in the RFC body. An RFC carries only scope, decomposition (sequencing/breakdown of already-decided work), and traces. The "Behavioural-tests-default for skill testing" architecture rule behavioural lint hard-fails any RFC body that contains a rejected-alternatives block without a matching `adrs:` reference.
 
-#### README refresh on conditional update (P094 mirror)
+#### README refresh on conditional update (the "Problem 094: `/wr-itil:manage-problem` does not refresh `docs/problems/README.md` on ticket creation" problem mirror)
 
 If the update changed any ranking-bearing field (Status, Severity-via-problems, Effort, WSJF), regenerate `docs/rfcs/README.md` in-place reflecting the new ranking and stage it in the same commit. If the edit touched only `## Summary`, `## Scope`, `## Tasks`, `## Related`, or other non-ranking sections, skip the refresh.
 
-**Mechanism** mirrors P094 in `manage-problem` Step 6 — render not re-rank; trust other RFC files' stored WSJF; consume only the post-edit RFC's WSJF for the ranking table.
+**Mechanism** mirrors the "Problem 094: `/wr-itil:manage-problem` does not refresh `docs/problems/README.md` on ticket creation" problem in `manage-problem` Step 6 — render not re-rank; trust other RFC files' stored WSJF; consume only the post-edit RFC's WSJF for the ranking table.
 
 ### 7. Status transitions
 
-Each transition is a `git mv` + Edit + `git add` (P057 staging trap) + README refresh + commit.
+Each transition is a `git mv` + Edit + `git add` (the "Problem 057: `git mv` + Edit + `git add` staging-ordering trap drops content edits from the commit" problem staging trap) + README refresh + commit.
 
 **Pre-flight checks before each transition**:
 
 | Transition | Checks |
 |------------|--------|
-| `proposed → accepted` | All `problems:` entries resolve. Architect re-review PASS. JTBD re-review PASS. `## Scope` populated (not "deferred"). `## Tasks` decomposed (≥ 1 task; not just deferred placeholder). **`stories:` non-empty — run `wr-itil-check-rfc-has-stories <rfc-file>`; hard-block on non-zero exit (empty `stories: []` or missing).** Per **ADR-089** the empty-stories fallback is removed: an atomic fix is an RFC with exactly one full story; an empty `stories:` is permitted only on a `proposed`/draft RFC before the fix is scoped, never at `accepted`. **Every listed story approved — run `wr-itil-check-rfc-stories-ratified <rfc-file> [stories-root] [maps-root]`; hard-block on non-zero (any listed story names no story map, or names one that is unratified or has drifted).** Per **ADR-103** a story's approval is its map's, so the remedy is always to ratify the MAP — a story carries no oversight marker of its own. Composes with the has-stories gate (has-stories checks ≥1 exists, this checks each is approved). |
+| `proposed → accepted` | All `problems:` entries resolve. Architect re-review PASS. JTBD re-review PASS. `## Scope` populated (not "deferred"). `## Tasks` decomposed (≥ 1 task; not just deferred placeholder). **`stories:` non-empty — run `wr-itil-check-rfc-has-stories <rfc-file>`; hard-block on non-zero exit (empty `stories: []` or missing).** Per **the "Every RFC has at least one story" architecture rule** the empty-stories fallback is removed: an atomic fix is an RFC with exactly one full story; an empty `stories:` is permitted only on a `proposed`/draft RFC before the fix is scoped, never at `accepted`. **Every listed story approved — run `wr-itil-check-rfc-stories-ratified <rfc-file> [stories-root] [maps-root]`; hard-block on non-zero (any listed story names no story map, or names one that is unratified or has drifted).** Per **the "A release row is the RFC, and the map is the approval surface" architecture rule** a story's approval is its map's, so the remedy is always to ratify the MAP — a story carries no oversight marker of its own. Composes with the has-stories gate (has-stories checks ≥1 exists, this checks each is approved). |
 | `accepted → in-progress` | First commit referencing `Refs: RFC-<NNN>` exists OR is being authored in this same commit. I1 hard-block on missing/orphan trace. |
 | `in-progress → verifying` | All `## Tasks` checked. `## Verification` section drafted (release marker, user-side check, trace closure path). I1 hard-block on missing/orphan trace. |
-| `verifying → closed` | User explicitly confirms (or AFK Rule 6 fallback for evidence-based close per ADR-022 / ADR-044 framework-resolved silent dispatch). I1 advisory-with-escalation if driving problems Closed/Parked. |
+| `verifying → closed` | User explicitly confirms (or AFK Rule 6 fallback for evidence-based close per the "Problem lifecycle — add a Verification Pending status between Known Error and Closed" architecture rule / the "— Decision-Delegation Contract: when agents act on the framework vs ask the user" architecture rule framework-resolved silent dispatch). I1 advisory-with-escalation if driving problems Closed/Parked. |
 
-If any pre-flight fails: report which checks failed; do NOT proceed; offer `AskUserQuestion` for direction-setting decisions (e.g., "scope still says deferred — populate now or park the transition?") only when the resolution is genuinely user-direction territory per ADR-044.
+If any pre-flight fails: report which checks failed; do NOT proceed; offer `AskUserQuestion` for direction-setting decisions (e.g., "scope still says deferred — populate now or park the transition?") only when the resolution is genuinely user-direction territory per the "— Decision-Delegation Contract: when agents act on the framework vs ask the user" architecture rule.
 
 #### Transition mechanics
 
@@ -133,46 +133,46 @@ git mv docs/rfcs/RFC-<NNN>-<slug>.<old-status>.md docs/rfcs/RFC-<NNN>-<slug>.<ne
 git add docs/rfcs/RFC-<NNN>-<slug>.<new-status>.md
 ```
 
-**P057 staging trap rule**: re-stage explicitly after the Edit tool runs. `git mv` alone stages only the rename, not subsequent content edits.
+**the "Problem 057: `git mv` + Edit + `git add` staging-ordering trap drops content edits from the commit" problem staging trap rule**: re-stage explicitly after the Edit tool runs. `git mv` alone stages only the rename, not subsequent content edits.
 
-#### Auto-transition detection (P378/RFC-030 Piece 2; ADR-060 line 292)
+#### Auto-transition detection (the "RFC lifecycle is not self-maintaining — it leans on human memory" problem/the ": RFC lifecycle self-maintenance" release design Piece 2; the "Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology" architecture rule line 292)
 
-`proposed → in-progress` is **detected** by `itil-commit-trailer-transition-advisory.sh` (PostToolUse:Bash; the shared RFC+story commit-trailer trigger): when the first non-capture commit carrying `Refs: RFC-<NNN>` lands while the RFC is still `proposed`/`accepted`, the hook emits a stderr advisory. Per ADR-014 the hook does NOT perform the `git mv` (that would land outside the commit grain) — this skill (or an AFK orchestrator acting on the advisory) performs the transition. Mirrors the manage-story draft→in-progress trigger; both share the one hook. (This closes the "future commit-trailer-trigger hook (deferred)" that manage-rfc and manage-story both named but never built.)
+`proposed → in-progress` is **detected** by `itil-commit-trailer-transition-advisory.sh` (PostToolUse:Bash; the shared RFC+story commit-trailer trigger): when the first non-capture commit carrying `Refs: RFC-<NNN>` lands while the RFC is still `proposed`/`accepted`, the hook emits a stderr advisory. Per the "Governance Skills Commit Their Own Completed Work" architecture rule the hook does NOT perform the `git mv` (that would land outside the commit grain) — this skill (or an AFK orchestrator acting on the advisory) performs the transition. Mirrors the manage-story draft→in-progress trigger; both share the one hook. (This closes the "future commit-trailer-trigger hook (deferred)" that manage-rfc and manage-story both named but never built.)
 
-#### Render the `## Commits` section (P378/RFC-030 Piece 1; ADR-085)
+#### Render the `## Commits` section (the "RFC lifecycle is not self-maintaining — it leans on human memory" problem/the ": RFC lifecycle self-maintenance" release design Piece 1; the "The RFC `## Commits` section is a git-log-derived view, rendered skill-side" architecture rule)
 
-On every transition AND every `review` (Step 9), render the affected RFC's `## Commits` section from git history — it is a derived view (`git log --grep "Refs: RFC-NNN"`), NOT stored per-commit, so it must be regenerated skill-side (a PostToolUse hook can't write it without breaking the ADR-014 commit grain). Invoke the helper before staging the RFC file:
+On every transition AND every `review` (Step 9), render the affected RFC's `## Commits` section from git history — it is a derived view (`git log --grep "Refs: RFC-NNN"`), NOT stored per-commit, so it must be regenerated skill-side (a PostToolUse hook can't write it without breaking the "Governance Skills Commit Their Own Completed Work" architecture rule commit grain). Invoke the helper before staging the RFC file:
 
 ```bash
 wr-itil-update-rfc-commits-section docs/rfcs/RFC-<NNN>-<slug>.<status>.md
 git add docs/rfcs/RFC-<NNN>-<slug>.<status>.md
 ```
 
-`wr-itil-update-rfc-commits-section` is the ADR-049 `$PATH` shim for `packages/itil/scripts/update-rfc-commits-section.sh` (idempotent — a current section is a byte-stable no-op, so the `git add` is a no-op when nothing changed). This closes the never-built ADR-060 item 12; the section is honestly rendered-as-of-this-skill-run, never a false "maintained automatically" claim.
+`wr-itil-update-rfc-commits-section` is the "Plugin-bundled scripts invoked from SKILL.md resolve via `bin/` on `$PATH`" architecture rule `$PATH` shim for `packages/itil/scripts/update-rfc-commits-section.sh` (idempotent — a current section is a byte-stable no-op, so the `git add` is a no-op when nothing changed). This closes the never-built the "Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology" architecture rule item 12; the section is honestly rendered-as-of-this-skill-run, never a false "maintained automatically" claim.
 
-#### README refresh on every transition (P062 mirror)
+#### README refresh on every transition (the "Problem 062: `manage-problem` does not refresh `docs/problems/README.md` on single-ticket transitions; fast-path cache goes stale silently" problem mirror)
 
 After renaming + Editing + `git add`-ing the transitioned RFC file, regenerate `docs/rfcs/README.md` in-place reflecting the new filename set and the transitioned RFC's new Status. Stage the refreshed README with the same commit.
 
-Update the "Last reviewed" line on `docs/rfcs/README.md` per the **inline P134 rotation mechanism** below. The mechanism is inlined here at the execution site (not deferred via cross-reference to `manage-problem` SKILL.md Step 5) so a single-pass agent reading this Step does not silently skip the archive step. **Skipping the BEFORE-rewrite archive step destroys the displaced fragment and re-opens P331** (origin failure mode: iter-7 + iter-8 of 2026-05-30's AFK work-problems session silently skipped the equivalent rotation on `docs/problems/README.md` in 2 of 9 transition-bearing iters). The mechanism MUST execute IN ORDER:
+Update the "Last reviewed" line on `docs/rfcs/README.md` per the **inline the "`docs/problems/README.md` line 3 narrative-blob accumulator bloat — sibling to (briefing tier 3) on a different surface" problem rotation mechanism** below. The mechanism is inlined here at the execution site (not deferred via cross-reference to `manage-problem` SKILL.md Step 5) so a single-pass agent reading this Step does not silently skip the archive step. **Skipping the BEFORE-rewrite archive step destroys the displaced fragment and re-opens the "transition-problem SKILL Step 7 Last-reviewed rotation silently skipped across iters" problem** (origin failure mode: iter-7 + iter-8 of 2026-05-30's AFK work-problems session silently skipped the equivalent rotation on `docs/problems/README.md` in 2 of 9 transition-bearing iters). The mechanism MUST execute IN ORDER:
 
 1. **Read** line 3 of `docs/rfcs/README.md`: `awk 'NR==3' docs/rfcs/README.md` (`head -3 | tail -1` or `sed -n '3p'` are acceptable equivalents).
 2. **Append-if-non-empty (BEFORE step 3, not after)** — if line 3 is non-empty AND not a same-session same-verb near-duplicate of the new fragment, append the existing line 3 verbatim to `docs/rfcs/README-history.md` (created on first rotation) under a `## YYYY-MM-DD` heading. Run this BEFORE the Edit-tool rewrite in step 3 — Edit's replace pattern destroys the displaced content otherwise.
-3. **Rewrite** line 3 of `docs/rfcs/README.md` with the new fragment of form `> Last reviewed: YYYY-MM-DD **<event>** — <one-line summary>` (e.g. `RFC-<NNN> <status> — <one-line summary>`). Soft cap ≤ 1024 bytes per fragment; hard ceiling 5120 bytes per ADR-040 Tier 3 envelope.
-4. **Stage both** — `git add docs/rfcs/README.md docs/rfcs/README-history.md` so the same single commit per ADR-014 captures both files.
+3. **Rewrite** line 3 of `docs/rfcs/README.md` with the new fragment of form `> Last reviewed: YYYY-MM-DD **<event>** — <one-line summary>` (e.g. `RFC-<NNN> <status> — <one-line summary>`). Soft cap ≤ 1024 bytes per fragment; hard ceiling 5120 bytes per the "Session-start briefing surface — SessionStart hook over tiered directory + indexed README" architecture rule Tier 3 envelope.
+4. **Stage both** — `git add docs/rfcs/README.md docs/rfcs/README-history.md` so the same single commit per the "Governance Skills Commit Their Own Completed Work" architecture rule captures both files.
 
-Canonical rationale anchor: `manage-problem` SKILL.md Step 5 § Last-reviewed line discipline (P134). The discipline applies identically across `docs/problems/README.md`, `docs/rfcs/README.md`, and `docs/stories/README.md` (only the target index path differs). The cross-reference is preserved for the "why"; the "what" is inlined above for execution-time legibility per P331.
+Canonical rationale anchor: `manage-problem` SKILL.md Step 5 § Last-reviewed line discipline (the "`docs/problems/README.md` line 3 narrative-blob accumulator bloat — sibling to (briefing tier 3) on a different surface" problem). The discipline applies identically across `docs/problems/README.md`, `docs/rfcs/README.md`, and `docs/stories/README.md` (only the target index path differs). The cross-reference is preserved for the "why"; the "what" is inlined above for execution-time legibility per the "transition-problem SKILL Step 7 Last-reviewed rotation silently skipped across iters" problem.
 
 #### Reverse trace on driving problem(s) (skill-side primary surface)
 
-Per ADR-060 Phase 1 item 10 + Confirmation criterion 3 + architect Q1 verdict (skill-side primary, hook-side advisory for arbitrary commits): every transition refreshes the `## RFCs` section on each driving problem ticket inline in the same commit per ADR-014 single-commit grain.
+Per the "Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology" architecture rule Phase 1 item 10 + Confirmation criterion 3 + architect Q1 verdict (skill-side primary, hook-side advisory for arbitrary commits): every transition refreshes the `## RFCs` section on each driving problem ticket inline in the same commit per the "Governance Skills Commit Their Own Completed Work" architecture rule single-commit grain.
 
 For each `P<NNN>` in the transitioned RFC's frontmatter `problems:` list:
 
 ```bash
 for pid_token in $(awk '/^problems:/{gsub(/[][]/,"");gsub(/,/,"\n");for(i=2;i<=NF;i++)print $i;exit}' "$rfc_file"); do
   pid_num="${pid_token#P}"
-  # Dual-tolerant ticket discovery — RFC-002 migration window covers
+  # Dual-tolerant ticket discovery — the ": docs/problems/ flat layout migration — per-state subdirs + adopter auto-migration" release design migration window covers
   # BOTH flat (`docs/problems/<NNN>-<title>.<state>.md`) AND per-state
   # subdir (`docs/problems/<state>/<NNN>-<title>.md`) layouts.
   problem_file=$(ls docs/problems/${pid_num}-*.md docs/problems/*/${pid_num}-*.md 2>/dev/null | head -1)
@@ -182,7 +182,7 @@ for pid_token in $(awk '/^problems:/{gsub(/[][]/,"");gsub(/,/,"\n");for(i=2;i<=N
 done
 ```
 
-The helper (`packages/itil/scripts/update-problem-rfcs-section.sh`) is idempotent and applies lazy-empty discipline (zero traced RFCs → section absent — a structural rendering rule, not a ceremony exemption; a problem traces ≥ 1 RFC once it reaches fix-time per ADR-071 / I13). After the transition, the helper:
+The helper (`packages/itil/scripts/update-problem-rfcs-section.sh`) is idempotent and applies lazy-empty discipline (zero traced RFCs → section absent — a structural rendering rule, not a ceremony exemption; a problem traces ≥ 1 RFC once it reaches fix-time per the "Every fix goes through an RFC" architecture rule / I13). After the transition, the helper:
 - Updates the row's `Status` column to the new lifecycle status.
 - Removes the row when this transition de-traces a problem (frontmatter `problems:` edit removed the entry).
 - No-op when the table is already current (idempotent contract).
@@ -191,7 +191,7 @@ The trailer hook (`itil-rfc-trailer-advisory.sh`) sits on top of this skill-side
 
 #### Forward trace — `## Stories` body section (Phase 2)
 
-Per ADR-060 line 270 + line 296: every transition that touches the RFC body refreshes the RFC's own `## Stories` body section from its frontmatter `stories:` array. The forward-trace surface renders the ordered execution sequence as inline links to the story files, lazy-empty when `stories: []` (an RFC not decomposed into stories). The helper is the Slice 2b sibling `update-rfc-references-section.sh`:
+Per the "Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology" architecture rule line 270 + line 296: every transition that touches the RFC body refreshes the RFC's own `## Stories` body section from its frontmatter `stories:` array. The forward-trace surface renders the ordered execution sequence as inline links to the story files, lazy-empty when `stories: []` (an RFC not decomposed into stories). The helper is the Slice 2b sibling `update-rfc-references-section.sh`:
 
 ```bash
 wr-itil-update-rfc-references-section "$rfc_file" "Stories"
@@ -218,11 +218,11 @@ Batch re-rank all RFCs and refresh `docs/rfcs/README.md`.
 4. WSJF = (Severity × Status Multiplier) / Effort divisor.
 5. Update WSJF/Effort lines in the RFC file if changed.
 
-**Step 9c**: Present a WSJF-ranked table (open + accepted + in-progress only). Verifying RFCs go in a Verification Queue section sorted by Released date ASC (canonical VQ sort direction per P150). Closed RFCs go in a Closed section (cosmetic, no ranking).
+**Step 9c**: Present a WSJF-ranked table (open + accepted + in-progress only). Verifying RFCs go in a Verification Queue section sorted by Released date ASC (canonical VQ sort direction per the "docs/problems/README.md Verification Queue rendered newest-first contradicts section header "Ranked by release age, oldest first"" problem). Closed RFCs go in a Closed section (cosmetic, no ranking).
 
-**Step 9d**: For each `.verifying.md` RFC, collect in-session evidence per ADR-044 framework-resolved silent dispatch (mirrors `manage-problem` Step 9d). Concrete + unambiguous citation → close on evidence via the transition path. Ambiguous/absent → leave as Verifying.
+**Step 9d**: For each `.verifying.md` RFC, collect in-session evidence per the "— Decision-Delegation Contract: when agents act on the framework vs ask the user" architecture rule framework-resolved silent dispatch (mirrors `manage-problem` Step 9d). Concrete + unambiguous citation → close on evidence via the transition path. Ambiguous/absent → leave as Verifying.
 
-**Step 9e**: Update changed files; refresh `docs/rfcs/README.md`; refresh the `## RFCs` reverse-trace section on every problem ticket whose traced RFCs changed status or title in this batch (per ADR-060 Phase 1 item 10 + Confirmation criterion 3 — skill-side primary):
+**Step 9e**: Update changed files; refresh `docs/rfcs/README.md`; refresh the `## RFCs` reverse-trace section on every problem ticket whose traced RFCs changed status or title in this batch (per the "Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology" architecture rule Phase 1 item 10 + Confirmation criterion 3 — skill-side primary):
 
 ```bash
 # Aggregate the union of P<NNN> across all RFCs touched in this review.
@@ -232,7 +232,7 @@ for problem_file in $(printf '%s\n' "${touched_problem_files[@]}" | sort -u); do
 done
 ```
 
-The helper is idempotent — a problem ticket whose `## RFCs` table is already current emits no diff, and `git add` of an unchanged file is a no-op. Any drift gets fixed in this commit per ADR-014 single-commit grain. Commit per ADR-014:
+The helper is idempotent — a problem ticket whose `## RFCs` table is already current emits no diff, and `git add` of an unchanged file is a no-op. Any drift gets fixed in this commit per the "Governance Skills Commit Their Own Completed Work" architecture rule single-commit grain. Commit per the "Governance Skills Commit Their Own Completed Work" architecture rule:
 
 ```
 docs(rfcs): review — re-rank RFC priorities
@@ -253,9 +253,9 @@ Commit conventions per operation:
 | `verifying → closed` | `docs(rfcs): close RFC-<NNN> <title>` |
 | Review/re-rank | `docs(rfcs): review — re-rank RFC priorities` |
 
-All commit messages on RFC-bearing commits carry the `Refs: RFC-<NNN>` trailer (ADR-060 finding 8 + Phase 1 item 12).
+All commit messages on RFC-bearing commits carry the `Refs: RFC-<NNN>` trailer (the "Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology" architecture rule finding 8 + Phase 1 item 12).
 
-Satisfy the commit gate per ADR-014 — primary path delegates to `wr-risk-scorer:pipeline` subagent; fallback invokes `/wr-risk-scorer:assess-release` skill.
+Satisfy the commit gate per the "Governance Skills Commit Their Own Completed Work" architecture rule — primary path delegates to `wr-risk-scorer:pipeline` subagent; fallback invokes `/wr-risk-scorer:assess-release` skill.
 
 ### 12. Auto-release (skip in AFK orchestrator)
 
@@ -268,36 +268,36 @@ Same conditional drain as `manage-problem` Step 12: if not in an AFK orchestrato
 | New RFC creation | Out of scope; redirect to capture-rfc | Owns the lightweight path |
 | Lifecycle transitions | Owns proposed → accepted → in-progress → verifying → closed | Out of scope |
 | WSJF re-rank | Step 9 review owns batch re-rank | Out of scope |
-| README refresh | P094 / P062 inline (regenerate + stage in same commit) | Deferred (capture-time speed) |
+| README refresh | the "Problem 094: `/wr-itil:manage-problem` does not refresh `docs/problems/README.md` on ticket creation" problem / the "Problem 062: `manage-problem` does not refresh `docs/problems/README.md` on single-ticket transitions; fast-path cache goes stale silently" problem inline (regenerate + stage in same commit) | Deferred (capture-time speed) |
 | Commit grain | One commit per intake / per transition / per review | One commit per capture |
 | AskUserQuestion authority | direction-setting (transition-trigger ambiguity), deviation-approval (scope expansion mid-RFC), silent-mechanical (status renames, README refresh) | direction-setting (problem-trace), taste (title), silent-mechanical (everything else) |
 
-The two skills share the `/tmp/wr-itil-rfc-capture-grep-${SESSION_ID}` create-gate marker (sibling to `/tmp/manage-problem-grep-${SESSION_ID}`).
+New RFC documents are retired. This skill manages legacy RFC documents only; new fix proposals use release rows and stories via `/wr-itil:capture-rfc`.
 
 ## Related
 
-- **ADR-060** — Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology.
-- **P170** — driver problem ticket.
+- **the "Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology" architecture rule** — Problem-RFC-Story framework with mandatory problem-trace and unified problem ontology.
+- **the "Problem tickets strain as fixes decompose into multiple coordinated changes — need an RFC framework that ties all changes back to problems (and unifies technical with user/business problems)" problem** — driver problem ticket.
 - **`docs/plans/170-rfc-framework-story-map.md`** — Slice 2 task B5.T4 lands this skill.
-- **JTBD-008** (primary), JTBD-001 (extended scope), JTBD-101 (atomic-fix-adopter — every fix via RFC per ADR-071).
+- **the ": Decompose a Fix Into Coordinated Changes" user outcome** (primary), the ": Enforce Governance Without Slowing Down" user outcome (extended scope), the "Extend the Suite with New Plugins" user outcome (atomic-fix-adopter — every fix via RFC per the "Every fix goes through an RFC" architecture rule).
 - **`docs/rfcs/README.md`** — lifecycle index + frontmatter shape (Slice 2 B5.T1 + B5.T2 — `adc53c8`).
 - **`packages/itil/skills/capture-rfc/SKILL.md`** — sibling lightweight capture skill.
 - **`packages/itil/skills/manage-problem/SKILL.md`** — heavyweight counterpart at the problem tier; structural template for this skill.
-- **ADR-014** — single-commit governance grain.
-- **ADR-022** — lifecycle suffix-based (RFC mirrors).
-- **ADR-032** — lightweight + heavyweight split.
-- **ADR-038** — progressive disclosure; future REFERENCE.md split deferred per ADR-054.
-- **ADR-042** — above-appetite remediation and halt discipline.
-- **ADR-044** — decision delegation contract; authority classes.
-- **ADR-049** — `wr-itil-reconcile-rfcs` shim grammar (Slice 3).
-- **ADR-051** — load-bearing-from-the-start; I1 hard-block on day one.
-- **ADR-052** — behavioural-tests default; bats coverage in Slice 2 B5.T5.
-- **P057** — staging trap rule (re-stage after Edit on every transition).
-- **P062** — README refresh on transition.
-- **P094** — README refresh on conditional update.
-- **P118** — README reconciliation contract.
-- **P132** + inverse-P078 — mechanical-stage carve-outs prevent over-asking.
-- **P134** — Last-reviewed line discipline (single fragment + history archive).
-- **P138** — tie-break ladder consistency.
-- **P150** — Verification Queue sort direction.
-- **P359** — changeset holding does not withhold shipped code.
+- **the "Governance Skills Commit Their Own Completed Work" architecture rule** — single-commit governance grain.
+- **the "Problem lifecycle — add a Verification Pending status between Known Error and Closed" architecture rule** — lifecycle suffix-based (RFC mirrors).
+- **the "Governance skill invocation patterns — foreground + background with deferred-question resumption" architecture rule** — lightweight + heavyweight split.
+- **the "Progressive disclosure + once-per-session budget for UserPromptSubmit governance prose" architecture rule** — progressive disclosure; future REFERENCE.md split deferred per the "SKILL.md runtime budget policy" architecture rule.
+- **the "Auto-apply scorer remediations to reach within appetite — open action-class vocabulary" architecture rule** — above-appetite remediation and halt discipline.
+- **the "— Decision-Delegation Contract: when agents act on the framework vs ask the user" architecture rule** — decision delegation contract; authority classes.
+- **the "Plugin-bundled scripts invoked from SKILL.md resolve via `bin/` on `$PATH`" architecture rule** — `wr-itil-reconcile-rfcs` shim grammar (Slice 3).
+- **the "`@windyroad/*` plugin READMEs anchor on JTBD job IDs with load-bearing commit-hook + prose-woven framing" architecture rule** — load-bearing-from-the-start; I1 hard-block on day one.
+- **the "Behavioural-tests-default for skill testing" architecture rule** — behavioural-tests default; bats coverage in Slice 2 B5.T5.
+- **the "Problem 057: `git mv` + Edit + `git add` staging-ordering trap drops content edits from the commit" problem** — staging trap rule (re-stage after Edit on every transition).
+- **the "Problem 062: `manage-problem` does not refresh `docs/problems/README.md` on single-ticket transitions; fast-path cache goes stale silently" problem** — README refresh on transition.
+- **the "Problem 094: `/wr-itil:manage-problem` does not refresh `docs/problems/README.md` on ticket creation" problem** — README refresh on conditional update.
+- **the "`docs/problems/README.md` drifts from filesystem truth across sessions despite (refresh-on-create) and (refresh-on-transition) both Closed" problem** — README reconciliation contract.
+- **the "Agents over-ask in interactive sessions — conflating mechanical-stages with user-interactive-stages of multi-stage skill contracts (inverse-)" problem** + inverse-the "Problem 078: Assistant does not offer to capture a problem ticket when the user delivers strong-signal correction" problem — mechanical-stage carve-outs prevent over-asking.
+- **the "`docs/problems/README.md` line 3 narrative-blob accumulator bloat — sibling to (briefing tier 3) on a different surface" problem** — Last-reviewed line discipline (single fragment + history archive).
+- **the "`docs/problems/README.md` WSJF Rankings table row order doesn't match `/wr-itil:work-problems`'s tie-break selection — users assume the orchestrator is broken" problem** — tie-break ladder consistency.
+- **the "docs/problems/README.md Verification Queue rendered newest-first contradicts section header "Ranked by release age, oldest first"" problem** — Verification Queue sort direction.
+- **the "Changeset holding does not withhold shipment — held code ships with any sibling release" problem** — changeset holding does not withhold shipped code.

package/skills/manage-rfc/agents/openai.yaml

@@ -0,0 +1,3 @@
+interface:
+  display_name: "WR ITIL: Manage RFC"
+  short_description: "Manage lifecycle for legacy RFC documents."