convoke-agents 2.3.1 → 3.0.0

package/_bmad/bme/_enhance/workflows/initiatives-backlog/steps-c/step-c-04-prioritize.md

@@ -0,0 +1,181 @@
+---
+name: 'step-c-04-prioritize'
+description: 'Generate complete backlog file with categorized items, prioritized view, and completion summary'
+outputFile: '{planning_artifacts}/initiatives-backlog.md'
+templateFile: '{project-root}/_bmad/bme/_enhance/workflows/initiatives-backlog/templates/backlog-format-spec.md'
+workflowFile: '{project-root}/_bmad/bme/_enhance/workflows/initiatives-backlog/workflow.md'
+---
+
+# Step 4: Backlog Generation, Prioritized View & Completion
+
+## STEP GOAL:
+
+Generate the complete backlog file from scratch using the scored initiatives, including all required sections, the prioritized view, provenance tags, and a changelog entry. Present a completion summary and return to the T/R/C menu.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+- 🛑 NEVER generate content without completing all mandatory sequence steps
+- 📖 CRITICAL: Read this complete step file before taking action
+- 🔄 CRITICAL: When returning to menu, read the entire workflow file
+- 📋 YOU ARE A BACKLOG OPERATIONS SPECIALIST generating a new backlog file
+
+### Role Reinforcement:
+- ✅ You are a **backlog operations specialist** — precise, structured, format-compliant
+- ✅ Generate the file exactly matching the backlog format specification — no shortcuts
+- ✅ All output must be standard markdown — no HTML, no proprietary syntax
+- ✅ Every item gets provenance, every section gets created, the prioritized view is sorted
+
+### Step-Specific Rules:
+- 🎯 Focus on file generation, provenance, prioritized view, and completion reporting
+- 🚫 FORBIDDEN to rescore items (scoring was finalized in step-c-03)
+- 🚫 FORBIDDEN to add new items not in the scored batch
+- 🚫 FORBIDDEN to modify step-c-01, step-c-02, or step-c-03
+- 💬 Approach: generate the complete file, summarize clearly, return to menu
+
+## EXECUTION PROTOCOLS:
+- 🎯 Follow the MANDATORY SEQUENCE exactly
+- 📖 Load `{templateFile}` (backlog-format-spec.md) for exact structural requirements and table formats
+- 💾 Write to `{outputFile}` as a complete new file
+
+## CONTEXT BOUNDARIES:
+- Available context: Scored initiatives from step-c-03, backlog format spec template
+- Focus: File generation, prioritized view, completion summary
+- Limits: Do NOT rescore or re-gather items
+- Dependencies: step-c-03-score.md (finalized scored initiatives with Track assignments)
+
+## MANDATORY SEQUENCE
+
+**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise.
+
+### 1. Load Format Specification
+
+Load `{templateFile}` (backlog-format-spec.md) and reference:
+- **Metadata header** format (title, Created, Method, Last Updated)
+- **Section hierarchy** — all 7 H2 sections in exact order
+- **Table formats** — Category table (10 columns), Prioritized View (6 columns), Exploration Candidates (4 columns)
+- **Item ID format** — Category prefix letter + sequential number
+- **Provenance format** — "Added from Create mode, [date]"
+
+### 2. Generate Metadata Header
+
+```markdown
+# Convoke Initiatives Backlog
+
+**Created:** [current date YYYY-MM-DD]
+**Method:** RICE (Reach, Impact, Confidence, Effort)
+**Last Updated:** [current date YYYY-MM-DD]
+```
+
+### 3. Generate RICE Scoring Guide Section
+
+Create the `## RICE Scoring Guide` section with an inline summary of the methodology:
+- Composite formula: Score = (R x I x C) / E
+- Factor scales: Reach (1-10), Impact (0.25-3), Confidence (20-100%), Effort (1-10)
+- Sort order: Descending by score, tiebreak by Confidence then insertion order
+
+### 4. Generate Backlog Section with Category Tables
+
+Create the `## Backlog` section. For each unique category in the scored items:
+
+1. Create an H3 heading: `### [Category Name]`
+2. Create a 10-column table:
+
+```markdown
+| # | Initiative | Source | R | I | C | E | Score | Track | Status |
+|---|-----------|--------|---|---|---|---|-------|-------|--------|
+```
+
+3. For each item in this category:
+   - **#:** Generate item ID using category prefix letter + sequential number within category (e.g., D1, D2, P1)
+     - Category prefix mapping: D = Documentation & Onboarding, U = Update & Migration System, T = Testing & CI, I = Infrastructure, A = Agent Quality & Consistency, P = Platform & Product Vision
+     - New categories: use the first uppercase letter of the category name that is not already in use (D, U, T, I, A, P are reserved)
+   - **Initiative:** `**[Title]** — [description]. Added from Create mode, [date]`
+   - **Source:** "Create mode"
+   - **R, I, C, E:** Individual RICE component scores (C as percentage, e.g., 70%)
+   - **Score:** Composite score, one decimal place
+   - **Track:** "Keep the lights on" or "Move the needle"
+   - **Status:** "Backlog"
+
+### 5. Generate Empty Sections
+
+Create the following sections with empty content:
+
+**Exploration Candidates:**
+```markdown
+## Exploration Candidates
+
+| # | Initiative | Source | Next Step |
+|---|-----------|--------|-----------|
+```
+
+**Epic Groupings:**
+```markdown
+## Epic Groupings
+
+*No epic groupings defined yet.*
+```
+
+**Completed:**
+```markdown
+## Completed
+
+*No completed items yet.*
+```
+
+### 6. Generate Prioritized View
+
+Create the `## Prioritized View (by RICE Score)` section:
+
+1. Collect ALL items from all category tables
+2. Sort by composite RICE score descending
+3. Tiebreak: (1) Higher Confidence first, (2) Newer insertion order first
+4. Generate sequential rank numbers starting at 1
+
+```markdown
+## Prioritized View (by RICE Score)
+
+| Rank | # | Initiative | Score | Track | Category |
+|------|---|-----------|-------|-------|----------|
+```
+
+### 7. Generate Change Log
+
+Create the `## Change Log` section with the initial creation entry:
+
+```markdown
+## Change Log
+
+| Date | Change |
+|------|--------|
+| [YYYY-MM-DD] | Create: Bootstrapped new backlog with [N] items ([list categories affected]). |
+```
+
+### 8. Write Complete File
+
+Write the complete assembled backlog to `{outputFile}`. The file must contain all 7 H2 sections in the correct order as specified by the format spec.
+
+### 9. Completion Summary & Return to Menu
+
+After successful write, display:
+
+> **Create Complete**
+>
+> **Items created:** [N]
+> **Categories:** [list category names]
+>
+> **Top 3 Positions:**
+> 1. [#ID] [title] — Score: [X.X]
+> 2. [#ID] [title] — Score: [X.X]
+> 3. [#ID] [title] — Score: [X.X]
+
+Then return to the T/R/C menu:
+
+> Loading `{workflowFile}` to return to mode selection...
+
+Load, read the entire file, and execute `{workflowFile}`.
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS:
+### ✅ SUCCESS: Complete backlog file generated with all 7 H2 sections in correct order, items placed in correct category tables with 10 columns, item IDs generated correctly, provenance tags added, prioritized view sorted and generated with 6 columns, changelog entry added, completion summary displayed with top 3, T/R/C menu re-presented
+### ❌ SYSTEM FAILURE: Missing H2 sections, wrong section order, items without provenance, wrong column counts, item IDs not generated, prioritized view not sorted, no changelog entry, no completion summary, no return to menu
+**Master Rule:** Skipping steps is FORBIDDEN.

package/_bmad/bme/_enhance/workflows/initiatives-backlog/steps-r/step-r-01-load.md

@@ -0,0 +1,120 @@
+---
+name: 'step-r-01-load'
+description: 'Load existing backlog and RICE scoring guide for Review mode walkthrough'
+nextStepFile: '{project-root}/_bmad/bme/_enhance/workflows/initiatives-backlog/steps-r/step-r-02-rescore.md'
+outputFile: '{planning_artifacts}/initiatives-backlog.md'
+templateFile: '{project-root}/_bmad/bme/_enhance/workflows/initiatives-backlog/templates/rice-scoring-guide.md'
+workflowFile: '{project-root}/_bmad/bme/_enhance/workflows/initiatives-backlog/workflow.md'
+---
+
+# Step 1: Load Backlog & Walkthrough Setup
+
+## STEP GOAL:
+
+Load the existing backlog file and RICE scoring guide, parse all active items with their current scores and provenance, and prepare for the per-item walkthrough.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+- 🛑 NEVER generate content without user input
+- 📖 CRITICAL: Read this complete step file before taking action
+- 🔄 CRITICAL: When loading next step with 'C', read the entire file
+- 📋 YOU ARE A REVIEW ANALYST loading context for rescoring
+
+### Role Reinforcement:
+- ✅ You are a **review analyst** — your job is to load and prepare data, not to modify it
+- ✅ Parse the backlog faithfully — do not reinterpret, reorder, or filter items
+- ✅ The walkthrough starts in step-r-02 — this step only loads and counts
+
+### Step-Specific Rules:
+- 🎯 Focus ONLY on loading, parsing, and counting backlog items
+- 🚫 FORBIDDEN to rescore, modify, or delete any backlog items (that is step-r-02's job)
+- 🚫 FORBIDDEN to write to the backlog file (that is step-r-03's job)
+- 🚫 FORBIDDEN to add new items (that is Triage mode's job)
+- 💬 Approach: load efficiently, confirm readiness, move on
+
+## EXECUTION PROTOCOLS:
+- 🎯 Follow the MANDATORY SEQUENCE exactly
+- 📖 Load `{templateFile}` for RICE factor definitions and scoring consistency reference
+- 📖 Load `{outputFile}` for existing backlog content
+
+## CONTEXT BOUNDARIES:
+- Available context: Existing backlog file, RICE scoring guide template
+- Focus: Data loading and preparation only
+- Limits: Do NOT modify, score, or write anything
+- Dependencies: workflow.md R dispatch (Review mode selected)
+
+## MANDATORY SEQUENCE
+
+**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise.
+
+### 0. Check Backlog File Exists
+
+Check if a backlog file exists at `{outputFile}`.
+
+- **If NOT found:** Display:
+
+  > **No backlog found at `{outputFile}`.**
+  >
+  > Review mode requires an existing backlog to walk through. Use **Triage (T)** or **Create (C)** mode first to create one.
+  >
+  > Returning to mode selection...
+
+  Then load, read the entire file, and execute `{workflowFile}` to return to T/R/C menu. **Do NOT proceed further.**
+
+- **If found:** Continue to step 1.
+
+### 1. Load Existing Backlog
+
+Load the complete file at `{outputFile}`. Preserve it in context — it will be needed for item presentation in step-r-02 and for safe update in step-r-03.
+
+### 2. Load RICE Scoring Guide
+
+Load `{templateFile}` (rice-scoring-guide.md) and internalize:
+- **Factor definitions:** Reach (1-10), Impact (0.25-3), Confidence (20-100%), Effort (1-10)
+- **Guided questions** for each factor
+- **Calibration examples** from the existing backlog
+- **Composite formula:** Score = (R x I x C) / E, where C is decimal (e.g., 70% = 0.7)
+- **Score rounding:** One decimal place for display
+
+### 3. Parse Active Backlog Items
+
+Parse all category tables **under `## Backlog`** to collect items with:
+- Item ID (e.g., D2, P4)
+- Title and description
+- Category (H3 heading name)
+- Current RICE component scores (R, I, C, E)
+- Current composite score
+- Current provenance (from Initiative description cell)
+- Current status
+
+**Do NOT include** items from `## Exploration Candidates`, `## Completed`, or other sections outside `## Backlog`.
+
+### 4. Count and Summarize
+
+Count the total number of active items collected. Display:
+
+> **Review Mode — Backlog Loaded**
+>
+> **Items found:** [N] active items across [M] categories
+> **Categories:** [list category names]
+> **Score range:** [lowest] to [highest]
+>
+> The walkthrough will present each item one at a time for review. You can rescore, confirm, skip, or exit early at any point.
+
+### 5. Present MENU OPTIONS
+
+Display: "**Select:** [C] Continue to item walkthrough"
+
+#### Menu Handling Logic:
+- IF C: Load, read the entire file, and execute `{project-root}/_bmad/bme/_enhance/workflows/initiatives-backlog/steps-r/step-r-02-rescore.md`
+- IF any other input: Display "Enter **C** to continue to the walkthrough." then redisplay menu
+
+#### EXECUTION RULES:
+- ALWAYS halt and wait for user input after presenting the menu
+- ONLY proceed to next step when user selects 'C'
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS:
+### ✅ SUCCESS: Backlog file loaded, RICE guide internalized, all active items parsed with scores and provenance, item count displayed, proceeding to step-r-02
+### ❌ SYSTEM FAILURE: Backlog not loaded, items from wrong sections included, items modified or filtered, scoring guide not loaded, missing backlog not handled gracefully
+**Master Rule:** Skipping steps is FORBIDDEN.

package/_bmad/bme/_enhance/workflows/initiatives-backlog/steps-r/step-r-02-rescore.md

@@ -0,0 +1,141 @@
+---
+name: 'step-r-02-rescore'
+description: 'Walk through backlog items one at a time for rescoring with RICE adjustments'
+nextStepFile: '{project-root}/_bmad/bme/_enhance/workflows/initiatives-backlog/steps-r/step-r-03-update.md'
+outputFile: '{planning_artifacts}/initiatives-backlog.md'
+templateFile: '{project-root}/_bmad/bme/_enhance/workflows/initiatives-backlog/templates/rice-scoring-guide.md'
+advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.md'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/bmad-party-mode/workflow.md'
+---
+
+# Step 2: Item Walkthrough & Rescoring
+
+## STEP GOAL:
+
+Walk through backlog items one at a time, presenting current scores and provenance, and allow the Product Owner to rescore, confirm, or skip each item. Track all decisions for the update step.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+- 🛑 NEVER generate content without user input at per-item prompts
+- 📖 CRITICAL: Read this complete step file before taking action
+- 🔄 CRITICAL: When loading next step with 'C', read the entire file
+- 📋 YOU ARE A RESCORING ANALYST guiding calibrated score adjustments
+
+### Role Reinforcement:
+- ✅ You are a **rescoring analyst** — systematic, evidence-based, calibration-aware
+- ✅ Present items faithfully with all current data — do not editorialize or suggest scores unless asked via A
+- ✅ The user decides what changes to make — you calculate, display, and record
+- ✅ Compare adjusted scores against calibration examples for consistency
+
+### Step-Specific Rules:
+- 🎯 Focus on per-item presentation, score adjustment, and decision tracking
+- 🚫 FORBIDDEN to write to the backlog file (that is step-r-03's job)
+- 🚫 FORBIDDEN to add new items (that is Triage mode's job)
+- 🚫 FORBIDDEN to delete or remove items from the backlog
+- 🚫 FORBIDDEN to auto-advance without user input — ALWAYS halt and wait
+- 💬 Approach: present one item, wait for decision, record result, advance
+
+## EXECUTION PROTOCOLS:
+- 🎯 Follow the MANDATORY SEQUENCE exactly
+- 📖 Reference `{templateFile}` for RICE factor scales when user adjusts scores
+- 💾 Track each item's decision: rescored (with old/new scores), confirmed, or skipped
+
+## CONTEXT BOUNDARIES:
+- Available context: Parsed backlog items from step-r-01, RICE scoring guide
+- Focus: Per-item walkthrough and rescoring only
+- Limits: Do NOT write to backlog or modify the file
+- Dependencies: step-r-01-load.md (loaded and parsed items)
+
+## MANDATORY SEQUENCE
+
+**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise.
+
+### 1. Initialize Walkthrough State
+
+Set up tracking for the walkthrough:
+- `current_index` = 1
+- `total_items` = count from step-r-01
+- `rescored_items` = [] (items with changed scores)
+- `confirmed_items` = [] (items explicitly confirmed or C'd without changes)
+- `skipped_items` = [] (items skipped)
+
+### 2. Present Current Item
+
+Display the current item with all scoring data:
+
+> **Item [current_index] of [total_items] — [Category Name]**
+>
+> **[ID]: [Title]** — Score: [composite]
+> R:[reach] I:[impact] C:[confidence]% E:[effort]
+> *Provenance: [current provenance text]*
+
+### 3. Present Per-Item Menu
+
+Display:
+
+> **Review this item:**
+>
+> **Score adjustments:**
+> - `R [value]` — Change Reach (1-10)
+> - `I [value]` — Change Impact (0.25, 0.5, 1, 2, or 3)
+> - `CF [value]` — Change Confidence (20-100%)
+> - `E [value]` — Change Effort (1-10)
+>
+> **Decisions:**
+> - `K` — Keep/confirm current score
+> - `S` — Skip this item (no review)
+> - `X` — Exit walkthrough early
+>
+> **[A] Advanced Elicitation** — Deeper scoring analysis
+> **[P] Party Mode** — Multi-perspective discussion
+> **[C] Continue** — Apply changes and advance to next item
+
+#### Menu Handling Logic:
+
+- IF `R [value]`: Validate value is integer 1-10. Update Reach for current item. Recalculate composite: Score = (R x I x C) / E. Redisplay updated item scores and menu.
+- IF `I [value]`: Validate value is one of 0.25, 0.5, 1, 2, or 3. Update Impact. Recalculate composite. Redisplay updated item scores and menu.
+- IF `CF [value]`: Validate value is integer 20-100. Update Confidence. Recalculate composite. Redisplay updated item scores and menu.
+- IF `E [value]`: Validate value is integer 1-10. Update Effort. Recalculate composite. Redisplay updated item scores and menu.
+- IF K: Mark item as **confirmed**. Add to `confirmed_items`. Advance to next item (go to step 4).
+- IF S: Mark item as **skipped**. Add to `skipped_items`. Advance to next item (go to step 4).
+- IF X: Exit walkthrough early. Go to step 5.
+- IF A: Execute `{advancedElicitationTask}` for deeper scoring analysis of this item. When finished, redisplay the current item scores and this menu.
+- IF P: Execute `{partyModeWorkflow}` for multi-perspective scoring discussion of this item. When finished, redisplay the current item scores and this menu.
+- IF C:
+  - **If scores were changed:** Record old and new composite scores. Add to `rescored_items` with: item ID, old R/I/C/E, new R/I/C/E, old composite, new composite. Advance to next item (go to step 4).
+  - **If NO scores were changed:** Treat as confirmed (same as K). Add to `confirmed_items`. Advance to next item (go to step 4).
+- IF any other input: Display "Unknown command. Use `R/I/CF/E [value]`, `K`, `S`, `X`, `A`, `P`, or `C`." then redisplay menu.
+
+#### EXECUTION RULES:
+- ALWAYS halt and wait for user input after presenting the menu
+- After EVERY score adjustment, recalculate composite, redisplay the updated item scores AND the menu
+- The user may make multiple adjustments before pressing C, K, S, or X
+- Do NOT auto-advance — every item requires explicit user input
+
+### 4. Advance to Next Item
+
+Increment `current_index`.
+
+- **If `current_index` <= `total_items`:** Go to step 2 (present next item).
+- **If `current_index` > `total_items`:** All items reviewed. Go to step 5.
+
+### 5. Walkthrough Complete — Pass Results to Update Step
+
+Display walkthrough summary:
+
+> **Walkthrough Complete**
+>
+> **Rescored:** [N] items
+> **Confirmed:** [N] items
+> **Skipped:** [N] items
+> [If early exit: **Unvisited:** [N] items]
+
+Then load, read the entire file, and execute `{project-root}/_bmad/bme/_enhance/workflows/initiatives-backlog/steps-r/step-r-03-update.md`, passing:
+- The list of rescored items (with old/new R/I/C/E and composite scores)
+- The counts of confirmed, skipped, and unvisited items
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS:
+### ✅ SUCCESS: Each item presented with full scoring data and provenance, user given per-item decision, score adjustments recalculated correctly, all decisions tracked (rescored/confirmed/skipped), results passed to step-r-03
+### ❌ SYSTEM FAILURE: Items auto-advanced without user input, scores not recalculated after adjustment, decisions not tracked, items modified in backlog file, walkthrough skipped items silently
+**Master Rule:** Skipping steps is FORBIDDEN.

package/_bmad/bme/_enhance/workflows/initiatives-backlog/steps-r/step-r-03-update.md

@@ -0,0 +1,154 @@
+---
+name: 'step-r-03-update'
+description: 'Apply rescores to backlog, regenerate prioritized view, present completion summary'
+outputFile: '{planning_artifacts}/initiatives-backlog.md'
+templateFile: '{project-root}/_bmad/bme/_enhance/workflows/initiatives-backlog/templates/backlog-format-spec.md'
+workflowFile: '{project-root}/_bmad/bme/_enhance/workflows/initiatives-backlog/workflow.md'
+---
+
+# Step 3: Backlog Update, Safety & Completion
+
+## STEP GOAL:
+
+Validate backlog structure, apply rescored items in-place, regenerate the prioritized view, and present a completion summary before returning to the T/R/C menu.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+- 🛑 NEVER generate content without user input at validation mismatch prompt
+- 📖 CRITICAL: Read this complete step file before taking action
+- 🔄 CRITICAL: When returning to menu, read the entire workflow file
+- 📋 YOU ARE A BACKLOG OPERATIONS SPECIALIST performing safe, structured writes
+
+### Role Reinforcement:
+- ✅ You are a **backlog operations specialist** — precise, non-destructive, in-place updates only
+- ✅ Preserve all existing content — never delete, overwrite, or reorder existing rows
+- ✅ The Prioritized View is the ONLY section regenerated from scratch
+- ✅ All output must be standard markdown — no HTML, no proprietary syntax
+
+### Step-Specific Rules:
+- 🎯 Focus on validation, safe in-place updates, and completion reporting
+- 🚫 FORBIDDEN to delete or reorder existing backlog items (FR18, NFR1)
+- 🚫 FORBIDDEN to add new items (that is Triage mode's job)
+- 🚫 FORBIDDEN to modify items that were confirmed or skipped — only rescored items are updated
+- 🚫 FORBIDDEN to modify step-r-01 or step-r-02
+- 💬 Approach: validate first, update safely, summarize clearly
+
+## EXECUTION PROTOCOLS:
+- 🎯 Follow the MANDATORY SEQUENCE exactly
+- 📖 Load `{templateFile}` (backlog-format-spec.md) for structural validation rules and table formats
+- 💾 Write to `{outputFile}` only after validation passes (or user overrides)
+
+## CONTEXT BOUNDARIES:
+- Available context: Rescored items from step-r-02, existing backlog file, backlog format spec template
+- Focus: Structural validation, safe in-place update, prioritized view regeneration, completion summary
+- Limits: Do NOT rescore, re-extract, or add items
+- Dependencies: step-r-02-rescore.md (rescored/confirmed/skipped results)
+
+## MANDATORY SEQUENCE
+
+**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise.
+
+### 1. Pre-Write Validation
+
+Load `{outputFile}` (existing backlog) and validate structural integrity:
+
+1. **Section heading anchors** — All 7 required H2 sections exist in correct order:
+   - `## RICE Scoring Guide`
+   - `## Backlog`
+   - `## Exploration Candidates`
+   - `## Epic Groupings`
+   - `## Prioritized View (by RICE Score)`
+   - `## Completed`
+   - `## Change Log`
+2. **Prioritized view table** — Has exactly 6 columns (Rank, #, Initiative, Score, Track, Category)
+3. **Category tables** — Each table under `## Backlog` has exactly 10 columns (#, Initiative, Source, R, I, C, E, Score, Track, Status)
+4. **Change Log section** — The `## Change Log` H2 section exists with a table
+
+If ALL checks pass, proceed directly to step 3 (Apply Rescores).
+
+### 2. Mismatch Handling
+
+If ANY validation check fails, present the specific mismatch(es):
+
+> **Pre-Write Validation — Structural Mismatch Detected**
+>
+> [List each failed check with details]
+>
+> **[Y] Yes, proceed anyway**
+> **[X] Abort and return to menu**
+
+**ALWAYS halt and wait for user input.**
+
+- IF Y: Continue to step 3 (Apply Rescores)
+- IF X: Display "Aborting backlog update." then load, read the entire file, and execute `{workflowFile}` to return to mode selection
+- IF any other input: Display "Please select **Y** or **X**." then redisplay the prompt
+
+### 3. Apply Rescores
+
+For each rescored item from step-r-02:
+
+1. **Find the item** — Locate the row in its category table under `## Backlog` by matching the item ID
+2. **Update RICE scores** — Replace R, I, C, E, and composite Score values in the row
+3. **Add rescore provenance** — Append to the Initiative description cell: `Rescored [old]->[new], Review, [date]` where [old] and [new] are the composite scores and [date] is the current session date (FR22)
+4. **Preserve everything else** — Do not modify the item's title, source, track, status, or any other content
+
+**Important:**
+- Only update items that were actually rescored (composite score changed)
+- Confirmed and skipped items remain completely unchanged — no provenance added
+- Do NOT reorder rows within category tables
+
+### 4. Regenerate Prioritized View
+
+Rebuild the `## Prioritized View (by RICE Score)` table from scratch:
+
+1. Collect ALL active items from all category tables (existing + rescored)
+2. Exclude items with Status "Done" or items in the `## Completed` section
+3. Sort by composite RICE score descending
+4. Tiebreak: (1) Higher Confidence first, (2) Newer insertion order first
+5. Generate sequential rank numbers starting at 1
+
+Table format (6 columns):
+```
+| Rank | # | Initiative | Score | Track | Category |
+|------|---|-----------|-------|-------|----------|
+```
+
+### 5. Add Changelog Entry
+
+Prepend a new row to the `## Change Log` table (newest first):
+
+```
+| YYYY-MM-DD | Review: Rescored [N] items, confirmed [N], skipped [N]. |
+```
+
+### 6. Update Last Updated Date
+
+Set the metadata header `Last Updated` field to the current date (YYYY-MM-DD format).
+
+### 7. Completion Summary & Return to Menu
+
+After successful write, display:
+
+> **Review Complete**
+>
+> **Items rescored:** [N]
+> **Items confirmed:** [N]
+> **Items skipped:** [N]
+> [If early exit: **Items unvisited:** [N]]
+>
+> **New Top 3 Positions:**
+> 1. [#ID] [title] — Score: [X.X]
+> 2. [#ID] [title] — Score: [X.X]
+> 3. [#ID] [title] — Score: [X.X]
+
+Then return to the T/R/C menu:
+
+> Loading `{workflowFile}` to return to mode selection...
+
+Load, read the entire file, and execute `{workflowFile}`.
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS:
+### ✅ SUCCESS: Pre-write validation performed, only rescored items updated in-place with correct provenance, confirmed/skipped items untouched, prioritized view regenerated with all items sorted correctly, changelog updated, completion summary displayed with top 3, T/R/C menu re-presented
+### ❌ SYSTEM FAILURE: Existing backlog content deleted/overwritten/reordered, confirmed or skipped items modified, provenance added to non-rescored items, items written without validation, prioritized view not regenerated, no completion summary, no return to menu
+**Master Rule:** Skipping steps is FORBIDDEN.