convoke-agents 3.2.0 → 3.3.0

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

@@ -1,18 +1,18 @@
 ---
 name: 'step-r-02-rescore'
-description: 'Walk through backlog items one at a time for rescoring with RICE adjustments'
+description: 'Walk lane items one at a time for RICE rescoring, lane-aware (Bug / Fast / Initiative)'
 nextStepFile: '{project-root}/_bmad/bme/_enhance/workflows/initiatives-backlog/steps-r/step-r-03-update.md'
-outputFile: '{planning_artifacts}/initiatives-backlog.md'
+outputFile: '{planning_artifacts}/convoke-note-initiative-lifecycle-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 2: Lane 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.
+Walk through the selected lane items one at a time, presenting current scores and lane-specific context (Bug status, Fast Lane RICE, Initiative stage + artifacts), and allow the user to rescore, confirm, or skip each item. Track all decisions for the update step.
 
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
@@ -24,17 +24,17 @@ Walk through backlog items one at a time, presenting current scores and provenan
 
 ### 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
+- ✅ Present items faithfully with all current data — do not editorialize unless user invokes A
 - ✅ The user decides what changes to make — you calculate, display, and record
-- ✅ Compare adjusted scores against calibration examples for consistency
+- ✅ Lane-aware: bugs emphasize risk-vs-cost, Fast Lane emphasizes effort, Initiative Lane includes Stage + Artifacts context
 
 ### 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 delete or promote/demote items between lanes (lane changes require separate qualification — noted for future item)
 - 🚫 FORBIDDEN to auto-advance without user input — ALWAYS halt and wait
-- 💬 Approach: present one item, wait for decision, record result, advance
+- 💬 Approach: present one item with its lane context, wait for decision, record result, advance
 
 ## EXECUTION PROTOCOLS:
 - 🎯 Follow the MANDATORY SEQUENCE exactly
@@ -42,10 +42,10 @@ Walk through backlog items one at a time, presenting current scores and provenan
 - 💾 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
+- Available context: `walk_scope` from step-r-01 (ordered list of lane items), 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)
+- Limits: Do NOT write to backlog, do NOT change item lanes
+- Dependencies: step-r-01-load.md (loaded items + scope)
 
 ## MANDATORY SEQUENCE
 
@@ -53,22 +53,45 @@ Walk through backlog items one at a time, presenting current scores and provenan
 
 ### 1. Initialize Walkthrough State
 
-Set up tracking for the walkthrough:
+Set up tracking:
 - `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)
+- `total_items` = count from `walk_scope`
+- `rescored_items` = [] — items with changed composite score
+- `confirmed_items` = [] — items explicitly confirmed or C'd without changes
+- `skipped_items` = [] — items skipped
 
-### 2. Present Current Item
+### 2. Present Current Item (Lane-Aware)
 
-Display the current item with all scoring data:
+Display the current item with lane-specific context:
 
-> **Item [current_index] of [total_items] — [Category Name]**
+**If Bug Lane item:**
+
+> **Item [current_index] of [total_items] — §2.2 Bug Lane**
+>
+> **[ID]: [Description]** — Score: [composite]
+> R:[reach] I:[impact] C:[confidence]% E:[effort]
+> *Status: [Open/In Fix/In Review/Shipped]*
+> *Portfolio: [portfolio]*
+> *Linked Follow-up: [fastLaneID or initiativeID, if any]*
+
+**If Fast Lane item:**
+
+> **Item [current_index] of [total_items] — §2.3 Fast Lane**
 >
-> **[ID]: [Title]** — Score: [composite]
+> **[ID]: [Description]** — Score: [composite]
 > R:[reach] I:[impact] C:[confidence]% E:[effort]
-> *Provenance: [current provenance text]*
+> *Status: [Backlog/In Story/In Sprint/Shipped]*
+> *Portfolio: [portfolio]*
+
+**If Initiative Lane item:**
+
+> **Item [current_index] of [total_items] — §2.4 Initiative Lane**
+>
+> **[ID]: [Description]** — Score: [composite]
+> R:[reach] I:[impact] C:[confidence]% E:[effort]
+> *Stage: [Qualified / In Pipeline / Ready / In Sprint / Done]*
+> *Portfolio: [portfolio]*
+> *Artifacts: [artifacts indicator, e.g., "D, P✓, A, IR, E" or "ADR only" or "—"]*
 
 ### 3. Present Per-Item Menu
 
@@ -90,21 +113,23 @@ Display:
 > **[A] Advanced Elicitation** — Deeper scoring analysis
 > **[P] Party Mode** — Multi-perspective discussion
 > **[C] Continue** — Apply changes and advance to next item
+>
+> *Note: Changing an item's lane, stage, portfolio, or status is NOT done in Review mode. If this item's lane no longer fits, raise a new intake via Triage mode.*
 
 #### 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 `R [value]`: Validate value is integer 1-10. Update Reach for current item. Recalculate composite: Score = (R × I × 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 A: Execute `{advancedElicitationTask}` for deeper scoring analysis of this item. When finished, redisplay.
+- IF P: Execute `{partyModeWorkflow}` for multi-perspective discussion. When finished, redisplay.
 - 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 scores were changed:** Record old and new composite scores. Add to `rescored_items` with lane name, item ID, old R/I/C/E, new R/I/C/E, old composite, new composite. Advance.
+  - **If NO scores were changed:** Treat as confirmed (same as K). Advance.
 - 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:
@@ -130,12 +155,17 @@ Display walkthrough summary:
 > **Confirmed:** [N] items
 > **Skipped:** [N] items
 > [If early exit: **Unvisited:** [N] items]
+>
+> **Rescored breakdown by lane:**
+> - §2.2 Bug Lane: [n]
+> - §2.3 Fast Lane: [n]
+> - §2.4 Initiative Lane: [n]
 
 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
+- `rescored_items` (each with lane name, ID, old and new R/I/C/E, old and new composites)
+- 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
+### ✅ SUCCESS: Each lane item presented with lane-specific context (status / stage / artifacts), user given per-item decision, score adjustments recalculated correctly, all decisions tracked by lane, results passed to step-r-03
+### ❌ SYSTEM FAILURE: Items auto-advanced without input, lane context missing, scores not recalculated after adjustment, decisions not tracked, lane changes attempted, items modified in backlog file
 **Master Rule:** Skipping steps is FORBIDDEN.

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

@@ -1,16 +1,16 @@
 ---
 name: 'step-r-03-update'
-description: 'Apply rescores to backlog, regenerate prioritized view, present completion summary'
-outputFile: '{planning_artifacts}/initiatives-backlog.md'
+description: 'Apply rescores in-place to lane tables, re-sort touched lanes, update Change Log, present completion summary'
+outputFile: '{planning_artifacts}/convoke-note-initiative-lifecycle-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 3: Backlog Update — Apply Rescores Lane-Aware
 
 ## 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.
+Validate backlog structure, apply rescored items in-place in their lane tables (§2.2 Bug / §2.3 Fast / §2.4 Initiative), re-sort only the lanes that were touched, update the Change Log, and present a completion summary before returning to the T/R/C menu.
 
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
@@ -22,17 +22,18 @@ Validate backlog structure, apply rescored items in-place, regenerate the priori
 
 ### 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
+- ✅ Preserve all existing content outside of the rescored rows and the sort order of their lanes
+- ✅ **Part 1 (Lifecycle Process) must not be modified** — it's semi-static documentation
+- ✅ **§2.1 Intakes and §2.5 Absorbed must not be modified** — Review does not touch them
+- ✅ Re-sort only the touched lanes — untouched lanes keep their current row order
 
 ### 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
+- 🎯 Focus on validation, safe in-place updates, lane-specific re-sort, and completion reporting
+- 🚫 FORBIDDEN to delete or add rows (add = Triage, remove = Absorb via separate flow)
+- 🚫 FORBIDDEN to modify items that were confirmed or skipped
+- 🚫 FORBIDDEN to change items' lane / portfolio / stage / status (Review only rescores RICE)
+- 🚫 FORBIDDEN to modify Part 1, §2.1, or §2.5
+- 💬 Approach: validate first, update rescored rows in-place, re-sort touched lanes, summarize
 
 ## EXECUTION PROTOCOLS:
 - 🎯 Follow the MANDATORY SEQUENCE exactly
@@ -40,10 +41,10 @@ Validate backlog structure, apply rescored items in-place, regenerate the priori
 - 💾 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)
+- Available context: `rescored_items` from step-r-02 (with lane, ID, old+new scores), existing backlog, format spec
+- Focus: Structural validation, in-place update, per-lane re-sort, Change Log, completion summary
+- Limits: Do NOT rescore, re-extract, add items, or change lane metadata
+- Dependencies: step-r-02-rescore.md (rescored + confirmed + skipped results)
 
 ## MANDATORY SEQUENCE
 
@@ -51,80 +52,70 @@ Validate backlog structure, apply rescored items in-place, regenerate the priori
 
 ### 1. Pre-Write Validation
 
-Load `{outputFile}` (existing backlog) and validate structural integrity:
+Load `{outputFile}` and validate per format spec:
 
-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
+1. **Frontmatter present**
+2. **Part 1 anchor exists** (not inspected for content)
+3. **Part 2 H3 anchors** — `### 2.1` through `### 2.5` in correct order
+4. **Lane table column counts** — Bug (10), Fast (9), Initiative (10)
+5. **Change Log section** — `## Change Log` H2 exists
 
-If ALL checks pass, proceed directly to step 3 (Apply Rescores).
+If ALL checks pass, proceed to step 3.
 
 ### 2. Mismatch Handling
 
-If ANY validation check fails, present the specific mismatch(es):
+If ANY validation check fails:
 
 > **Pre-Write Validation — Structural Mismatch Detected**
 >
-> [List each failed check with details]
+> [List each failed check]
 >
 > **[Y] Yes, proceed anyway**
 > **[X] Abort and return to menu**
 
-**ALWAYS halt and wait for user input.**
+**ALWAYS halt and wait.**
 
-- 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
+- IF Y: Continue to step 3.
+- IF X: Display "Aborting backlog update." then load, read, and execute `{workflowFile}`.
+- IF any other input: Display "Please select **Y** or **X**." then redisplay.
 
-### 3. Apply Rescores
+### 3. Apply Rescores In-Place
 
-For each rescored item from step-r-02:
+For each item in `rescored_items`:
 
-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
+1. **Find the item** — Locate the row in the correct lane table (§2.2 / 2.3 / 2.4) by matching the item ID.
+2. **Update RICE columns** — Replace R, I, C, E, and composite Score values in the row.
+3. **Preserve everything else** — Do not modify Description, Portfolio, Status, Stage, Artifacts, Linked Follow-up, or any non-RICE column.
+4. **Optional rescore provenance** — If the Description cell has capacity, append a subtle note: ` [rescored YYYY-MM-DD: X.X→Y.Y]`. Skip if the cell would exceed readable length.
 
 **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
+- Only update items whose composite score actually changed.
+- Confirmed and skipped items remain completely unchanged — no modification, no note.
+- Do NOT modify rows not in `rescored_items`.
 
-### 4. Regenerate Prioritized View
+### 4. Re-Sort Touched Lanes
 
-Rebuild the `## Prioritized View (by RICE Score)` table from scratch:
+For each lane that had at least one rescored item:
 
-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
+1. Collect all rows in that lane's table.
+2. Sort by composite RICE score **descending**.
+3. Tiebreak: (1) Confidence higher first, (2) insertion order newer first.
+4. Rewrite the lane's table body with the sorted rows.
 
-Table format (6 columns):
-```
-| Rank | # | Initiative | Score | Track | Category |
-|------|---|-----------|-------|-------|----------|
-```
+**Do NOT re-sort lanes that were not touched** — preserve their current order. This keeps `git diff` minimal for lanes the session didn't review.
 
-### 5. Add Changelog Entry
+### 5. Add Change Log Entry
 
-Prepend a new row to the `## Change Log` table (newest first):
+Prepend a new row to `## Change Log`:
 
 ```
-| YYYY-MM-DD | Review: Rescored [N] items, confirmed [N], skipped [N]. |
+| YYYY-MM-DD | Review: Rescored [N] items — Bug: [n], Fast: [n], Initiative: [n]. Confirmed: [N], skipped: [N][, unvisited: N]. Lanes re-sorted: [list]. |
 ```
 
-### 6. Update Last Updated Date
+### 6. Update Frontmatter
 
-Set the metadata header `Last Updated` field to the current date (YYYY-MM-DD format).
+- Do NOT modify the `created` date.
+- Frontmatter `status` stays as-is (typically `active`).
 
 ### 7. Completion Summary & Return to Menu
 
@@ -133,14 +124,19 @@ After successful write, display:
 > **Review Complete**
 >
 > **Items rescored:** [N]
-> **Items confirmed:** [N]
-> **Items skipped:** [N]
-> [If early exit: **Items unvisited:** [N]]
+>   - §2.2 Bug Lane: [n]
+>   - §2.3 Fast Lane: [n]
+>   - §2.4 Initiative Lane: [n]
+> **Confirmed:** [N]
+> **Skipped:** [N]
+> [If early exit: **Unvisited:** [N]]
+>
+> **Lanes re-sorted:** [list, e.g., "Fast Lane, Initiative Lane"]
 >
-> **New Top 3 Positions:**
-> 1. [#ID] [title] — Score: [X.X]
-> 2. [#ID] [title] — Score: [X.X]
-> 3. [#ID] [title] — Score: [X.X]
+> **Top 3 across touched lanes (post-sort):**
+> 1. [#ID] [title] — Score: [X.X] — Lane: [lane]
+> 2. [#ID] [title] — Score: [X.X] — Lane: [lane]
+> 3. [#ID] [title] — Score: [X.X] — Lane: [lane]
 
 Then return to the T/R/C menu:
 
@@ -149,6 +145,6 @@ Then return to the T/R/C menu:
 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
+### ✅ SUCCESS: Validation performed, only rescored items updated in-place with RICE changes, confirmed/skipped items untouched, only touched lanes re-sorted (untouched lanes preserved), Part 1 / §2.1 / §2.5 untouched, Change Log updated with per-lane counts, completion summary displayed, menu re-presented
+### ❌ SYSTEM FAILURE: Rows added or removed, items' lane/stage/status modified, Part 1 or §2.1 or §2.5 altered, untouched lanes re-sorted unnecessarily, Change Log missing lane breakdown, provenance added to confirmed/skipped items
 **Master Rule:** Skipping steps is FORBIDDEN.

package/_bmad/bme/_enhance/workflows/initiatives-backlog/steps-t/step-t-01-ingest.md

@@ -2,14 +2,14 @@
 name: 'step-t-01-ingest'
 description: 'Accept text input — review transcript, meeting notes, or any findings source'
 nextStepFile: '{project-root}/_bmad/bme/_enhance/workflows/initiatives-backlog/steps-t/step-t-02-extract.md'
-outputFile: '{planning_artifacts}/initiatives-backlog.md'
+outputFile: '{planning_artifacts}/convoke-note-initiative-lifecycle-backlog.md'
 ---
 
 # Step 1: Ingest Review Findings
 
 ## STEP GOAL:
 
-Accept the Product Owner's text input (review transcript, meeting notes, audit output, or any findings source) and prepare it for extraction in the next step.
+Accept the user's text input (review transcript, meeting notes, audit output, party mode output, or any findings source) and prepare it for extraction in the next step.
 
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
@@ -26,19 +26,19 @@ Accept the Product Owner's text input (review transcript, meeting notes, audit o
 
 ### Step-Specific Rules:
 - 🎯 Focus ONLY on accepting and preserving input text
-- 🚫 FORBIDDEN to extract findings, classify, or score in this step — that is step-t-02's job
-- 🚫 FORBIDDEN to truncate, summarize, or skip any part of the input regardless of length (FR46)
+- 🚫 FORBIDDEN to extract findings, classify, log, or qualify in this step — those are later steps' job
+- 🚫 FORBIDDEN to truncate, summarize, or skip any part of the input regardless of length
 - 💬 Approach: brief prompts, minimal overhead, get to the content quickly
 
 ## EXECUTION PROTOCOLS:
 - 🎯 Follow the MANDATORY SEQUENCE exactly
-- 📖 Load existing backlog if present — it will be needed for overlap detection in step-t-02
+- 📖 Load existing backlog if present — it will be needed for overlap detection and for appending in later steps
 
 ## CONTEXT BOUNDARIES:
 - Available context: Enhance config (loaded by workflow.md), existing backlog file (if present)
 - Focus: Accepting user input only
-- Limits: Do NOT analyze, classify, or score input
-- Dependencies: workflow.md T dispatch (completed in Story 1.3)
+- Limits: Do NOT analyze, classify, or qualify input
+- Dependencies: workflow.md T dispatch
 
 ## MANDATORY SEQUENCE
 
@@ -46,16 +46,16 @@ Accept the Product Owner's text input (review transcript, meeting notes, audit o
 
 ### 1. Check for Existing Backlog
 
-Check if an existing backlog file exists at `{planning_artifacts}/initiatives-backlog.md`.
+Check if an existing backlog file exists at `{outputFile}`.
 
-- **If found:** Load it silently — it will be used for overlap detection in step-t-02. Briefly note to the user: "Existing backlog loaded — overlap detection will be available during extraction."
-- **If not found:** Note silently — step-t-02 will skip overlap detection. Briefly note: "No existing backlog found — a new one will be created."
+- **If found:** Load it silently — it will be used for overlap detection in step-t-02 and for writes in step-t-04. Briefly note to the user: "Existing lifecycle backlog loaded — overlap detection against current Intakes and lane items will be available during extraction."
+- **If not found:** Note silently — step-t-02 will skip overlap detection. Briefly note: "No existing backlog found. Note: Triage cannot create a new backlog — use Create mode [C] for that. Triage will still extract findings but the final update step will require an existing file."
 
 ### 2. Prompt for Text Input
 
 Display:
 
-> **Triage Mode — Paste your review findings below.**
+> **Triage Mode — Paste your findings below.**
 >
 > Accepted formats: review transcripts, meeting notes, audit outputs, party-mode outputs, code review findings, retrospective notes, or any text containing actionable observations.
 >
@@ -65,7 +65,7 @@ Display:
 
 - Accept the user's complete text input
 - Preserve it exactly as provided — do not modify, reformat, or summarize
-- Process the **entire** input regardless of length (FR46)
+- Process the **entire** input regardless of length
 - Confirm receipt: "Received [N] lines of input. Ready to extract findings."
 
 ### 4. Present MENU OPTIONS