agentme 0.35.0 → 0.35.1

package/.xdrs/agentme/bdrs/index.md

@@ -14,7 +14,7 @@ Organisational structure, team topology, and strategic alignment concepts.
 
 Project management workflow and structure for development teams.
 
-- [agentme-bdr-401](operations/401-epic-feature-story-planning.md) - **Epic / Feature / User Story planning** — Organize development work as epics, features, and user stories using XDRS plan documents
+- [agentme-bdr-401](operations/401-epic-feature-story-planning.md) - **Epic / Feature / User Story planning** — Organize development work as epics, features, and user stories using XDRS initiative documents
 - [agentme-bdr-402](operations/402-digital-product-roles.md) - **Digital product roles — organisation & cross-team** — Defines team purpose, workforce allocation, roles overview, and org-level and cross-team roles (PM, Principal Engineer, Solution Architect)
 - [agentme-bdr-403](operations/403-product-team-composition.md) - **Product team composition** — Defines team composition models, squad structure, squad dynamics, and known structural gaps for Product Teams
 - [agentme-bdr-404](operations/404-team-roles-and-specialists.md) - **Digital product roles — team & specialists** — Defines team-level roles (PO, PjM, BA, AI BA, AI Lead, AI Engineer, Tech Lead, engineers) and shared specialist roles

package/.xdrs/agentme/bdrs/operations/401-epic-feature-story-planning.md

@@ -1,6 +1,6 @@
 ---
 name: agentme-bdr-policy-401-epic-feature-user-story-planning
-description: Defines how to organize software development project management work as epics, features, and user stories using XDRS plan documents. Use when creating, reviewing, or navigating epic plans, feature milestones, or user story files.
+description: Defines how to organize software development project management work as epics, features, and user stories using XDRS initiative documents. Use when creating, reviewing, or navigating epic initiatives, feature milestones, or user story files.
 apply-to: AI coding agents and developers managing software development work in projects that follow agentme standards
 valid-from: 2026-08-28
 ---
@@ -15,7 +15,7 @@ How should software development project management work be organized within an X
 
 ## Decision Outcome
 
-**Epics are XDRS plan documents. Features are Milestones inside those plans. User stories are key tasks linked to detail files.**
+**Epics are XDRS initiative documents. Features are Milestones inside those initiatives. User stories are key tasks linked to detail files.**
 
 ### Details
 
@@ -23,19 +23,19 @@ How should software development project management work be organized within an X
 
 An epic is a group of features that together achieve a well-defined objective. Epics typically span 1–12 months.
 
-- Each epic MUST be represented as one XDRS plan document of type BDR, placed at:
-  `.xdrs/[scope]/bdrs/operations/plans/NNN-epic-slug.md`
-- The plan heading MUST follow the format: `# [scope]-bdr-plan-NNN: [Epic Title]`
-- NNN is the plan's unique number within the `[scope]/bdrs/operations/plans/` namespace, assigned sequentially per `_core-adr-policy-007`.
+- Each epic MUST be represented as one XDRS initiative document of type BDR, placed at:
+  `.xdrs/[scope]/bdrs/operations/initiatives/NNN-epic-slug.md`
+- The initiative heading MUST follow the format: `# [scope]-bdr-initiative-NNN: [Epic Title]`
+- NNN is the initiative's unique number within the `[scope]/bdrs/operations/initiatives/` namespace, assigned sequentially per `_core-adr-policy-007`.
 - The slug MUST be lowercase, hyphen-separated, and descriptive (e.g., `001-epic-improve-checkout.md`).
-- Each epic plan MUST include all required sections from `_core-adr-policy-007`: Executive Summary, Context and Problem Statement, Proposed Solution (with Expected end date), and Milestones.
-- Epic plans are ephemeral and MUST be deleted after the epic is fully implemented, per `_core-adr-policy-007`.
+- Each epic initiative MUST include all required sections from `_core-adr-policy-007`: Executive Summary, Context and Problem Statement, Proposed Solution (with Expected end date), and Milestones.
+- Epic initiatives are ephemeral and MUST be deleted after the epic is fully implemented, per `_core-adr-policy-007`.
 
 #### 02-feature-as-milestone
 
 A feature is a specific activity, tool, or functionality that contributes to the epic's objective. Features typically span 2 weeks to 6 months.
 
-- Each feature MUST be represented as one `### Milestone N: [Feature Name]` section inside the epic plan.
+- Each feature MUST be represented as one `### Milestone N: [Feature Name]` section inside the epic initiative.
 - One Milestone per Feature; do not combine unrelated features into a single Milestone.
 - Milestone sections MUST follow the structure defined in `_core-adr-policy-007`:
   - Owner, Due date, Description, optional Acceptance checklist, Key tasks, optional Risks.
@@ -47,13 +47,13 @@ A user story is a unit of work within a Feature that delivers perceivable value
 - Each user story MUST appear as a key task entry inside its parent Milestone's `**Key tasks:**` list, always as a markdown link to its detail file.
 - **Pending (not yet refined):** `- [Brief description — pending]{.assets/userstory-NNN-slug.md}` — file has `**Status:** to-be-refined`
 - **Refined:** `- [Story title]{.assets/userstory-NNN-slug.md}` — no status field in the file
-- NNN is local to the epic plan's `.assets/` folder; it restarts at 001 for each epic.
+- NNN is local to the epic initiative's `.assets/` folder; it restarts at 001 for each epic.
 - Story slugs MUST be lowercase and hyphen-separated (e.g., `userstory-001-add-login-page`).
 
 #### 04-user-story-detail-file
 
 Each refined user story MUST have a detail file placed at:
-`.xdrs/[scope]/bdrs/operations/plans/.assets/userstory-NNN-slug.md`
+`.xdrs/[scope]/bdrs/operations/initiatives/.assets/userstory-NNN-slug.md`
 
 - NNN and slug MUST match the placeholder file that was refined (extracted from its `**Story ID:**` line). For new stories without a placeholder, use the next available NNN in `.assets/` and derive the slug by kebab-casing the story title to at most 7 words.
 - The file MUST begin with a `**Story ID:** userstory-NNN-slug` line. A refined file has no `**Status:**` field; the absence of the status field indicates the story is complete.
@@ -117,7 +117,7 @@ As a [role], I want to [action], so that [benefit].
 [highly desirable — screenshots, mockups, or diagrams illustrating the feature.]
 - [attachment]
 
-**Epic plan:** [NNN-epic-slug.md](../NNN-epic-slug.md)
+**Epic initiative:** [NNN-epic-slug.md](../NNN-epic-slug.md)
 ```
 
 #### 05-detailed-specs-requirement
@@ -132,15 +132,15 @@ A user story that lacks enough detail to begin architecture, planning, or implem
 #### 06-refinement-workflow
 
 Stories MUST be refined using the `151-refine-user-story` skill. The skill:
-- Detects active epic plan documents and lists pending stories for selection.
+- Detects active epic initiative documents and lists pending stories for selection.
 - MUST run a structured 10-phase refinement process including interface/integration spec discovery.
-- MUST write the resulting detail file and update the key task link in the plan's Milestone.
-- When a story is split, MUST create placeholder files for each deferred slice and add them as pending task links in the plan.
+- MUST write the resulting detail file and update the key task link in the initiative's Milestone.
+- When a story is split, MUST create placeholder files for each deferred slice and add them as pending task links in the initiative.
 
 #### 07-ephemeral-lifecycle
 
-Epic plans and their associated user story detail files are ephemeral artifacts. Once an epic is fully implemented:
-- The epic plan document MUST be deleted.
+Epic initiatives and their associated user story detail files are ephemeral artifacts. Once an epic is fully implemented:
+- The epic initiative document MUST be deleted.
 - The `.assets/` folder and all user story detail files MUST be deleted with it.
 - The lasting outputs of an epic are the implemented code, decisions, skills, articles, and other artifacts produced during execution.
 
@@ -148,12 +148,12 @@ Epic plans and their associated user story detail files are ephemeral artifacts.
 
 Epics SHOULD be connected to one or more Tactical OKRs from `agentme-bdr-002` that represent the quarterly goals the epic is helping achieve.
 
-- The OKR reference MUST be placed in a `## OKRs` section immediately after the heading line of the epic plan document, listing each Tactical OKR by name or identifier.
+- The OKR reference MUST be placed in a `## OKRs` section immediately after the heading line of the epic initiative document, listing each Tactical OKR by name or identifier.
 - An epic without a linked Tactical OKR MUST document the reason in the `## OKRs` section (e.g., "No Tactical OKR defined for this quarter — tracked as a conscious decision").
 - The relationship is many-to-many: one Tactical OKR MAY drive multiple Epics; one Epic MAY contribute to multiple Tactical OKRs.
 
 ## References
 
-- [`_core-adr-policy-007`](../../../_core/adrs/principles/007-plan-standards.md) — Plan document standards: structure, lifecycle, and Milestone template
+- [`_core-adr-policy-007`](../../../_core/adrs/principles/007-initiative-standards.md) — Initiative document standards: structure, lifecycle, and Milestone template
 - [`agentme-bdr-002`](../principles/002-okr-framework.md) — OKR framework: Tactical OKR definition and epic connection rule
 - [`agentme-edr-skill-151`](../../edrs/principles/skills/151-refine-user-story/SKILL.md) — Refine user story skill: structured refinement workflow that produces output following this policy

package/.xdrs/agentme/edrs/principles/skills/150-refine-plan-mode/SKILL.md

@@ -8,7 +8,7 @@ description: >
   the XDRS repository even when not directly exposed in the .agents skills folder.
 metadata:
   author: flaviostutz
-  version: "2.8"
+  version: "2.9"
 ---
 
 ## Overview
@@ -254,11 +254,15 @@ Before approving execution, verify ALL items in the checklist below. If any item
 Once all items are checked or explicitly marked N/A, present a **brief scenario summary** — a short bulleted list of the most significant scenarios discovered across all phases (aim for 5–10 entries), each showing: the angle or check that surfaced it, what it revealed, and what test case was added to the plan. This makes the depth of analysis visible before handoff.
 
 If any features were placed in the **Deferred Features** list during Phase 2 Step 5 (scope split) or explicitly excluded from scope at any point, present a **Deferred Features summary** — a bulleted list of each deferred part with a one-line description of what it covers and why it was deferred. Then use `vscode_askQuestions` with:
-- **"Save to BACKLOG.md"** (recommended) — append the list under a `## Deferred Features` heading in `BACKLOG.md` at the workspace root (create the file if it does not exist), so the user can plan future implementation runs from it.
-- **"Save to a different file"** (open box) — human specifies the file path; append there instead.
+- **"Save to TODO.md"** (recommended) — append an entry under a `## Deferred Features` heading in `TODO.md` at the workspace root (create the file if it does not exist), using the Group/Part template below, so anyone can pick up the work later without losing context.
+- **"Save to a different file"** (open box) — human specifies the file path; append there instead using the same Group/Part template.
 - **"Skip — do not save"** — proceed without saving.
 This step is skipped if no features were deferred.
 
+**Deferred Features entry template** — always append a new `### Group:` section per split (never merge with a same-titled prior group); a group can have as few as 1 part:
+- `### Group: [original request title] — deferred [YYYY-MM-DD]` — with **Origin:** `150-refine-plan-mode — Phase 2 Step 5`, **Original objective:** the one-sentence value of the whole request before splitting, and **Split rationale:** why it was split.
+- One `#### [part title]` subsection per deferred part, each with **Objective:** (this part's specific value), **Scope:** (bullet list of what's included), **Context captured so far:** (bullet list of key decisions/answers/constraints already gathered before deferral), and **Suggested prompt to resume:** (a ready-to-paste prompt naming plan mode and summarizing the objective and known constraints so a future session can resume without re-reading the whole conversation).
+
 Before the final gate, add a step to the implementation plan to produce a concise feature documentation file. Use `vscode_askQuestions` to ask:
 - **"Save to README.md"** (recommended) — append the documentation to `README.md` in the feature’s directory (create if absent).
 - **"Save to a different file"** (open box) — human specifies the file path.

package/.xdrs/agentme/edrs/principles/skills/150-refine-plan-mode/SKILL.test.md

@@ -1,6 +1,6 @@
 ---
 skill: 150-refine-plan-mode
-skill-version: "2.7"
+skill-version: "2.9"
 ---
 
 ## Test Scenarios
@@ -89,3 +89,27 @@ The skill flags this as a violation of the Questioning rule and the HITL require
 - [ ] Skill explicitly frames the question as a clarifying question, not a confirmation request.
 - [ ] Skill waits for the human's answer before continuing to the next angle.
 - [ ] Violation is noted if the agent attempted to self-resolve a subjective decision.
+
+### Scenario 5: Feature split — deferred parts saved to TODO.md with Group/Part detail
+
+**Trigger / Input**
+
+"Build a complete admin dashboard: user management, billing management, and audit log viewer."
+
+**Expected Behaviour**
+
+Phase 2 Step 4 surfaces roughly 24 distinct in-scope items across the three subsystems. Phase 2 Step 5 judges the request too large — it spans 3 qualitatively different concerns (user management, billing, audit) each needing independent data-model and UI design, and exceeds the ~20-item threshold — and proposes a 3-way split. The human accepts the split and picks "User management" as Part 1. Phases 1–7 run on User management only; the other two parts are recorded in the Deferred Features list. At Phase 7, the skill presents a brief one-line-per-item Deferred Features summary, then uses `vscode_askQuestions` offering "Save to TODO.md" as the recommended option. The human picks it. The skill creates (or appends to) `TODO.md` at the workspace root with a `## Deferred Features` heading containing one `### Group:` section covering both deferred parts (Billing management, Audit log viewer), with Origin/Original objective/Split rationale, and each part as its own `#### ` subsection with Objective, Scope, Context captured so far, and a Suggested prompt to resume.
+
+**Simulated Human Responses**
+1. "Accept split — start planning User management"
+2. "Save to TODO.md"
+
+**Assertions**
+
+- [ ] Skill proposes a 3-way split with a brief rationale for each part's boundary, justified by at least two of the Phase 2 Step 5 size criteria.
+- [ ] Only the chosen part (User management) is planned through Phases 1–7; the other two parts are not further elaborated beyond the deferred entry.
+- [ ] Phase 7 presents a Deferred Features summary as brief one-line bullets before asking where to save.
+- [ ] `vscode_askQuestions` offers "Save to TODO.md" as the recommended option.
+- [ ] TODO.md is created (or appended to) at the workspace root with a `## Deferred Features` heading.
+- [ ] A single `### Group:` heading covers both deferred parts, recording Origin, Original objective, and Split rationale.
+- [ ] Each deferred part appears as its own `#### ` subsection with Objective, Scope, Context captured so far, and a Suggested prompt to resume.

package/.xdrs/agentme/edrs/principles/skills/151-refine-user-story/SKILL.md

@@ -7,12 +7,12 @@ description: >
   complete, and ready for implementation.
 metadata:
   author: flaviostutz
-  version: "4.0"
+  version: "4.1"
 ---
 
 ## Overview
 
-Turns a vague request or rough draft into an implementation-ready user story by running a structured 9-phase refinement process: establishing plan context and gathering external information to ground the analysis (Phase 1), analysing the request and qualifying requirements with a scope size check (Phase 2), researching existing context and drafting a story skeleton (Phase 3), checking consistency and scope completeness (Phase 4), validating visually with a user journey diagram (Phase 5), challenging from 9 user-perspective angles (Phase 6), challenging from 8 implementer-perspective angles (Phase 7), producing a final ready-to-implement story with a readiness checklist (Phase 8), and running a final readiness double-check (Phase 9).
+Turns a vague request or rough draft into an implementation-ready user story by running a structured 9-phase refinement process: establishing initiative context and gathering external information to ground the analysis (Phase 1), analysing the request and qualifying requirements with a scope size check (Phase 2), researching existing context and drafting a story skeleton (Phase 3), checking consistency and scope completeness (Phase 4), validating visually with a user journey diagram (Phase 5), challenging from 9 user-perspective angles (Phase 6), challenging from 8 implementer-perspective angles (Phase 7), producing a final ready-to-implement story with a readiness checklist (Phase 8), and running a final readiness double-check (Phase 9).
 
 Activate when:
 - The request is vague, incomplete, or internally inconsistent.
@@ -45,21 +45,21 @@ Activate when:
 
 ---
 
-### Phase 1: Plan Document Context & Context Enrichment
+### Phase 1: Initiative Document Context & Context Enrichment
 
 Before beginning refinement, determine the working context and where output will be saved.
 
 **Inline reference — Epic / Feature / User Story structure** (self-contained; no external policy file required to run this skill):
-- **Epic** — A plan document at `[scope]/bdrs/operations/plans/NNN-epic-slug.md`. Represents a group of features toward a well-defined objective (1–12 months). Heading: `# [scope]-bdr-plan-NNN: [Epic Title]`.
-- **Feature** — A `### Milestone N: [Feature Name]` section inside the epic plan. One Milestone per Feature. Duration: 2 weeks – 6 months.
+- **Epic** — An initiative document at `[scope]/bdrs/operations/initiatives/NNN-epic-slug.md`. Represents a group of features toward a well-defined objective (1–12 months). Heading: `# [scope]-bdr-initiative-NNN: [Epic Title]`.
+- **Feature** — A `### Milestone N: [Feature Name]` section inside the epic initiative. One Milestone per Feature. Duration: 2 weeks – 6 months.
 - **User Story** — A key task inside a Milestone, always as a link: `- [Brief description]{.assets/userstory-NNN-slug.md}`. Pending stories append ` — pending` to the link text and have `**Status:** to-be-refined` in the file. Refined stories have the full title. Duration: < 2 weeks; stories exceeding this MUST be split.
-- **User story detail file** — `.assets/userstory-NNN-slug.md` inside the epic plan's `.assets/` folder. NNN restarts at 001 per epic. Filenames always lowercase.
+- **User story detail file** — `.assets/userstory-NNN-slug.md` inside the epic initiative's `.assets/` folder. NNN restarts at 001 per epic. Filenames always lowercase.
 
 **Step 1 — Detect XDRS scope**
 
 Scan the workspace for a `.xdrs/` directory. Proceed to Step 2a, 2b, or 2c based on what is found.
 
-**Step 2a — Plan document explicitly provided or referenced:**
+**Step 2a — Initiative document explicitly provided or referenced:**
 1. Parse all `### Milestone` sections (Features) and collect all task entries that link to `.assets/userstory-*.md` files.
 2. For each linked file, read it and check for `**Status:** to-be-refined`. Collect only those as pending stories.
 3. Use `vscode_askQuestions` to list all pending stories (by their link text and file name) plus a "New story — I will describe it" option.
@@ -68,16 +68,16 @@ Scan the workspace for a `.xdrs/` directory. Proceed to Step 2a, 2b, or 2c based
    - Use the placeholder's title and notes as the subject for Phase 2.
 5. If the user picks "New story", ask which Milestone to place it in; offer to add the Milestone if it does not exist. The slug and NNN for the new story are assigned in Phase 8.
 
-**Step 2b — XDRS scope found but no plan document provided:**
-1. Search for files matching `*/bdrs/operations/plans/*-epic-*.md`.
-2. Use `vscode_askQuestions` to ask the user to: pick an existing epic plan, create a new epic plan, or start fresh (no plan context).
-3. If an existing plan is picked, proceed as Step 2a.
-4. If **create a new epic plan** is chosen, run a guided Q&A using `vscode_askQuestions` to collect: Epic Title, one-sentence objective, Expected end date (YYYY-MM-DD), and name of the first Feature/Milestone. Then:
+**Step 2b — XDRS scope found but no initiative document provided:**
+1. Search for files matching `*/bdrs/operations/initiatives/*-epic-*.md`.
+2. Use `vscode_askQuestions` to ask the user to: pick an existing epic initiative, create a new epic initiative, or start fresh (no initiative context).
+3. If an existing initiative is picked, proceed as Step 2a.
+4. If **create a new epic initiative** is chosen, run a guided Q&A using `vscode_askQuestions` to collect: Epic Title, one-sentence objective, Expected end date (YYYY-MM-DD), and name of the first Feature/Milestone. Then:
    - Derive the epic slug by kebab-casing the title, keeping at most 7 words.
-   - Determine the epic NNN by scanning `[scope]/bdrs/operations/plans/` for existing plan files and using the next available number (start at 001).
-   - Create the file at `.xdrs/[scope]/bdrs/operations/plans/NNN-epic-slug.md` with the required `_core-adr-policy-007` sections:
+   - Determine the epic NNN by scanning `[scope]/bdrs/operations/initiatives/` for existing initiative files and using the next available number (start at 001).
+   - Create the file at `.xdrs/[scope]/bdrs/operations/initiatives/NNN-epic-slug.md` with the required `_core-adr-policy-007` sections:
      ```markdown
-     # [scope]-bdr-plan-NNN: [Epic Title]
+     # [scope]-bdr-initiative-NNN: [Epic Title]
 
      ## Executive Summary
      [To be completed.]
@@ -98,8 +98,8 @@ Scan the workspace for a `.xdrs/` directory. Proceed to Step 2a, 2b, or 2c based
 
      **Key tasks:**
      ```
-   - Proceed as Step 2a (the new plan is now the active plan context, Milestone 1 is the target).
-5. If "start fresh" is chosen, continue to Phase 1 Step 3 (Context Enrichment) with no active plan context; Phase 8 will handle deferred stories.
+   - Proceed as Step 2a (the new initiative is now the active initiative context, Milestone 1 is the target).
+5. If "start fresh" is chosen, continue to Phase 1 Step 3 (Context Enrichment) with no active initiative context; Phase 8 will handle deferred stories.
 
 **Step 2c — No XDRS scope found:**
 Skip Phase 1 Steps 1–2. Proceed directly to Phase 1 Step 3 (Context Enrichment). Phase 8 will ask where to save output.
@@ -130,7 +130,7 @@ Before beginning analysis, gather factual context about the system, process, or
 
 ---
 
-**Plan context record:** note the active plan file path (or none), the target Milestone name, and the Context Summary from Step 3; carry these into Phase 8.
+**Initiative context record:** note the active initiative file path (or none), the target Milestone name, and the Context Summary from Step 3; carry these into Phase 8.
 
 ---
 
@@ -247,7 +247,7 @@ After all checks converge, use `vscode_askQuestions` (per Phase gate UI rule) wi
    - **"Add a comment or correction"** (open box) — re-run Phase 5 treating the comment as additional context, then re-present this gate.
 
 4. If the diagram reveals gaps or inconsistencies not yet surfaced, return to Phase 4 before continuing.
-5. **Save the confirmed diagram.** Write the Mermaid source to `.assets/userstory-NNN-slug-journey.md` inside the plan's `.assets/` folder (when a plan doc is active) or to `userstory-journey.md` at the workspace root otherwise. Record this path to include as a diagram attachment in `## Attachments` when Phase 8 writes the story file.
+5. **Save the confirmed diagram.** Write the Mermaid source to `.assets/userstory-NNN-slug-journey.md` inside the initiative's `.assets/` folder (when an initiative doc is active) or to `userstory-journey.md` at the workspace root otherwise. Record this path to include as a diagram attachment in `## Attachments` when Phase 8 writes the story file.
 
 ---
 
@@ -360,37 +360,39 @@ Once all items are checked or explicitly marked N/A, **produce the final result*
 
 If any stories or features were placed in the **Deferred Stories** list during Phase 2 Step 3 (scope split), or any items were recorded as named **Deferred Risks** during a Skip, present a **Deferred Items summary** — a bulleted list of each deferred item with a one-line description of what it covers and why it was deferred.
 
-**When an XDRS plan doc is active** (Phase 1 selected or created a plan): skip this prompt entirely. Deferred slices are handled as placeholder files with task links in the plan doc by the Plan document integration section below.
+**When an XDRS initiative doc is active** (Phase 1 selected or created an initiative): skip this prompt entirely. Deferred slices are handled as placeholder files with task links in the initiative doc by the Initiative document integration section below.
 
-**When no XDRS plan doc is active**: use `vscode_askQuestions` with:
-- **"Save to BACKLOG.md"** (recommended) — append the list under a `## Deferred Stories` heading in `BACKLOG.md` at the workspace root (create the file if it does not exist), so the items can be planned for future refinement runs.
-- **"Save to a different file"** (open box) — human specifies the file path; append there instead.
+**When no XDRS initiative doc is active**: use `vscode_askQuestions` with:
+- **"Save to TODO.md"** (recommended) — append an entry under a `## Deferred Stories` heading in `TODO.md` at the workspace root (create the file if it does not exist), using the template below.
+- **"Save to a different file"** (open box) — human specifies the file path; append there instead using the same template.
 - **"Skip — do not save"** — proceed without saving.
 
 This step is skipped if no stories were deferred and no Deferred Risks were recorded.
 
-### Plan document integration
+**Deferred Stories template**: new `### Group: [title] — deferred [YYYY-MM-DD]` per split (1+ parts, never merged) with **Origin**, **Original objective**, **Split rationale**; one `#### [slice title]` per slice with **Objective**, **Scope**, **Context captured so far**, **Suggested prompt to resume**.
 
-After producing the final story output, persist it according to the active plan context from Phase 1.
+### Initiative document integration
 
-**When an XDRS plan doc is active (Phase 1 selected or created a plan):**
+After producing the final story output, persist it according to the active initiative context from Phase 1.
+
+**When an XDRS initiative doc is active (Phase 1 selected or created an initiative):**
 1. Determine the NNN and slug for the story detail file:
    - **Placeholder story** (Phase 1 picked a pending story): extract the NNN and slug from the placeholder file's `**Story ID:**` line. Reuse them for the refined file.
-   - **New story** (Phase 1 chose "New story" or a new epic was created): use the next available NNN in the plan's `.assets/` folder (list existing `userstory-NNN-*.md` files, increment the highest; start at 001 if empty). Derive the slug by kebab-casing the refined `## Title`, keeping at most 7 words, e.g. `save-payment-method-future-checkouts`.
-2. Write the refined story as `.assets/userstory-NNN-slug.md` inside the plan's `.assets/` folder using the output template, including the `**Story ID:** userstory-NNN-slug` line at the top (no `**Status:**` line — absence of the status field indicates a refined story).
-3. In the plan doc, update the task entry link text in the active Milestone: change `[Brief description — pending]` to `[Refined Story Title]` (keep the same `.assets/userstory-NNN-slug.md` path). For new stories, insert a new task entry `- [Refined Story Title]{.assets/userstory-NNN-slug.md}`.
+   - **New story** (Phase 1 chose "New story" or a new epic was created): use the next available NNN in the initiative's `.assets/` folder (list existing `userstory-NNN-*.md` files, increment the highest; start at 001 if empty). Derive the slug by kebab-casing the refined `## Title`, keeping at most 7 words, e.g. `save-payment-method-future-checkouts`.
+2. Write the refined story as `.assets/userstory-NNN-slug.md` inside the initiative's `.assets/` folder using the output template, including the `**Story ID:** userstory-NNN-slug` line at the top (no `**Status:**` line — absence of the status field indicates a refined story).
+3. In the initiative doc, update the task entry link text in the active Milestone: change `[Brief description — pending]` to `[Refined Story Title]` (keep the same `.assets/userstory-NNN-slug.md` path). For new stories, insert a new task entry `- [Refined Story Title]{.assets/userstory-NNN-slug.md}`.
 4. When splitting: for each non-chosen slice, create a placeholder file at `.assets/userstory-NNN-slug.md` containing:
    - `**Story ID:** userstory-NNN-slug`
    - `**Status:** to-be-refined`
    - A `## Title` with the preliminary description of the slice.
    - A `## Notes from intake` section with any relevant context captured in this session: split rationale, relationship to the current story, any API or business details already known.
    - A `## Related` section linking to the current story being refined.
-   Assign NNNs sequentially after the highest existing one in `.assets/` (the current story's file already written by step 2 counts as existing). Insert a task entry `- [Slice description — pending]{.assets/userstory-NNN-slug.md}` in the same Milestone (or a new Milestone if the split reveals a distinct Feature). Do NOT offer BACKLOG.md for deferred slices.
-5. Add a back-link to the epic plan at the bottom of the story detail file: `**Epic plan:** [NNN-epic-slug.md]{../NNN-epic-slug.md}` (the `../` resolves from `.assets/` up to `plans/`).
+   Assign NNNs sequentially after the highest existing one in `.assets/` (the current story's file already written by step 2 counts as existing). Insert a task entry `- [Slice description — pending]{.assets/userstory-NNN-slug.md}` in the same Milestone (or a new Milestone if the split reveals a distinct Feature). Do NOT offer TODO.md for deferred slices.
+5. Add a back-link to the epic initiative at the bottom of the story detail file: `**Epic initiative:** [NNN-epic-slug.md]{../NNN-epic-slug.md}` (the `../` resolves from `.assets/` up to `initiatives/`).
 
-**When no XDRS plan doc is active ("start fresh" or no XDRS scope):**
+**When no XDRS initiative doc is active ("start fresh" or no XDRS scope):**
 - Ask the user where to save the refined story (default: `userstory-NNN-slug.md` at workspace root).
-- If split/deferred stories exist, use `vscode_askQuestions` to ask whether to add them to an existing epic plan, create a new epic plan, or save to `BACKLOG.md`. Apply the chosen action.
+- If split/deferred stories exist, use `vscode_askQuestions` to ask whether to add them to an existing epic initiative, create a new epic initiative, or save to `TODO.md` per the template in Phase 8. Apply the chosen action.
 
 ### Output Template
 
@@ -437,8 +439,8 @@ As a [role], I want to [action], so that [benefit].
 [highly desirable — screenshots, mockups, or diagrams illustrating the feature.]
 - [attachment]
 
-**Epic plan:** [NNN-epic-slug.md](../NNN-epic-slug.md)
-*(omit when no XDRS plan doc is active)*
+**Epic initiative:** [NNN-epic-slug.md](../NNN-epic-slug.md)
+*(omit when no XDRS initiative doc is active)*
 ```
 
 ---

package/.xdrs/agentme/edrs/principles/skills/151-refine-user-story/SKILL.test.md

@@ -1,6 +1,6 @@
 ---
 skill: 151-refine-user-story
-skill-version: "3.0"
+skill-version: "4.1"
 ---
 
 ## Test Scenarios
@@ -75,8 +75,8 @@ You are an agent with the `151-refine-user-story` skill loaded. The workspace ha
 6. User accepts the split and picks "Registration" as the first slice to refine.
 7. Skill restarts from Phase 1 with the narrower registration scope. The remaining 3 slices are recorded as Deferred Stories.
 8. Phases 1–7 run on the registration slice only. At Phase 8, a Deferred Items summary lists the 3 remaining slices.
-9. Because no plan doc is active, skill presents `vscode_askQuestions` asking where to save the deferred slices; user picks BACKLOG.md.
-10. Skill outputs one fully refined story (registration) and appends the 3 deferred slices to BACKLOG.md.
+9. Because no initiative doc is active, skill presents `vscode_askQuestions` asking where to save the deferred slices; user picks TODO.md.
+10. Skill outputs one fully refined story (registration) and appends the 3 deferred slices to TODO.md as a single `### Group:` section with one `#### ` subsection per slice.
 
 **Simulated Human Responses**
 1. "Registration: email + password only. Password min 8 chars, at least one digit. Email must be verified before the user can log in."
@@ -154,10 +154,10 @@ Phases 1–5 are complete. The skill is running Phase 6, angle 1 (User journey c
 
 ---
 
-### Scenario 6: Plan document with pending placeholder stories — user picks one to refine
+### Scenario 6: Initiative document with pending placeholder stories — user picks one to refine
 
 **Trigger / Input**
-You are an agent with the `151-refine-user-story` skill loaded. The user references an epic plan document at `.xdrs/_local/bdrs/operations/plans/001-epic-improve-checkout.md`. The plan contains:
+You are an agent with the `151-refine-user-story` skill loaded. The user references an epic initiative document at `.xdrs/_local/bdrs/operations/initiatives/001-epic-improve-checkout.md`. The initiative contains:
 
 ```
 ### Milestone 1: Payment Speed
@@ -173,7 +173,7 @@ You are an agent with the `151-refine-user-story` skill loaded. The user referen
 Each `.assets/userstory-*.md` file contains `**Status:** to-be-refined` plus any preliminary notes captured when the story was created.
 
 **Expected Behaviour**
-1. Skill activates Phase 0, detects the plan document, and parses all Milestone key tasks.
+1. Skill activates Phase 0, detects the initiative document, and parses all Milestone key tasks.
 2. Skill reads each linked `.assets/userstory-*.md` file and checks for `**Status:** to-be-refined`. Identifies all three as pending.
 3. Skill presents a `vscode_askQuestions` list of the three pending stories plus a "New story" option.
 4. User picks the "Reduce payment steps" story from Milestone 1.
@@ -188,27 +188,27 @@ Each `.assets/userstory-*.md` file contains `**Status:** to-be-refined` plus any
 - [ ] Output shows NNN and slug extracted from the placeholder file's `**Story ID:**` line, not from the task entry text.
 - [ ] Skill overwrites the story detail file with refined content and no `**Status:**` field after Phase 8.
 - [ ] Skill updates the Milestone 1 task entry link text to the refined story title; the file path stays the same.
-- [ ] Skill does NOT offer "Save to BACKLOG.md" for deferred items while a plan doc is active.
+- [ ] Skill does NOT offer "Save to TODO.md" for deferred items while an initiative doc is active.
 
 ---
 
-### Scenario 7: Refined story output writes asset file and updates plan Milestone link
+### Scenario 7: Refined story output writes asset file and updates initiative Milestone link
 
 **Trigger / Input**
-You are an agent with the `151-refine-user-story` skill loaded. Phase 0 has detected an active plan doc at `.xdrs/_local/bdrs/operations/plans/002-epic-onboarding.md` with Milestone 1: "First Login Experience". The user is refining a new story to be placed there.
+You are an agent with the `151-refine-user-story` skill loaded. Phase 0 has detected an active initiative doc at `.xdrs/_local/bdrs/operations/initiatives/002-epic-onboarding.md` with Milestone 1: "First Login Experience". The user is refining a new story to be placed there.
 
 After completing Phases 1–6, Phase 8 produces the final story: "Show personalised welcome screen on first login".
 
 **Expected Behaviour**
-1. Phase 8 determines the next NNN in the plan's `.assets/` folder (no existing userstory files → NNN = 001).
-2. Skill writes `.assets/userstory-001-welcome-screen-first-login.md` using the output template sections: Title, User Story, Scope, Edge Cases, Out of Scope, Constraints, Detailed Specs, Acceptance Criteria, Attachments, plus a back-link to the epic plan.
-3. Skill inserts `- [Show personalised welcome screen on first login](.assets/userstory-001-welcome-screen-first-login.md)` as a key task in Milestone 1 of the plan doc.
+1. Phase 8 determines the next NNN in the initiative's `.assets/` folder (no existing userstory files → NNN = 001).
+2. Skill writes `.assets/userstory-001-welcome-screen-first-login.md` using the output template sections: Title, User Story, Scope, Edge Cases, Out of Scope, Constraints, Detailed Specs, Acceptance Criteria, Attachments, plus a back-link to the epic initiative.
+3. Skill inserts `- [Show personalised welcome screen on first login](.assets/userstory-001-welcome-screen-first-login.md)` as a key task in Milestone 1 of the initiative doc.
 
 **Assertions**
-- [ ] Skill creates the story detail file at the correct path inside the plan's `.assets/` folder.
+- [ ] Skill creates the story detail file at the correct path inside the initiative's `.assets/` folder.
 - [ ] Output uses all required template sections including `## Constraints` and `## Detailed Specs`.
-- [ ] Output includes a back-link to the parent epic plan.
-- [ ] Plan doc's Milestone 1 key tasks section contains a markdown link entry pointing to the new file.
+- [ ] Output includes a back-link to the parent epic initiative.
+- [ ] Initiative doc's Milestone 1 key tasks section contains a markdown link entry pointing to the new file.
 - [ ] Output shows NNN as 001 (first story in this epic's `.assets/` folder).
 
 ---
@@ -224,13 +224,13 @@ You are an agent with the `151-refine-user-story` skill loaded. The workspace ha
 1. Phase 0 finds no XDRS scope and skips to Phase 1 immediately.
 2. Skill runs all phases normally.
 3. At Phase 8, after producing the final story, skill asks via `vscode_askQuestions` where to save the story file, defaulting to `userstory-001-reset-pin-via-sms.md` at the workspace root.
-4. If the story is split, the deferred slices prompt offers: add to existing epic plan, create new epic plan, or save to `BACKLOG.md`.
+4. If the story is split, the deferred slices prompt offers: add to existing epic initiative, create new epic initiative, or save to `TODO.md`.
 
 **Assertions**
-- [ ] Skill does not block or present any plan-doc questions when no XDRS scope exists.
+- [ ] Skill does not block or present any initiative-doc questions when no XDRS scope exists.
 - [ ] Skill asks for a save location with a clear default path at Phase 8.
 - [ ] Skill saves the story file to the user-confirmed path.
-- [ ] Skill triggers a destination choice for split deferred stories (not silently writing to BACKLOG.md).
+- [ ] Skill triggers a destination choice for split deferred stories (not silently writing to TODO.md).
 
 ---
 
@@ -261,23 +261,23 @@ After Phase 2 Step 1, no API endpoints, no payload structures, no documentation
 ### Scenario 10: XDRS scope active, start fresh, story split — Phase 8 asks where to put deferred slices
 
 **Trigger / Input**
-You are an agent with the `151-refine-user-story` skill loaded. Phase 0 detected an XDRS scope with two existing epic plans but the user chose "start fresh — no plan context". During Phase 2, the story is found to be too large and split into three slices. The user accepts the split and starts refining Slice 1.
+You are an agent with the `151-refine-user-story` skill loaded. Phase 0 detected an XDRS scope with two existing epic initiatives but the user chose "start fresh — no initiative context". During Phase 2, the story is found to be too large and split into three slices. The user accepts the split and starts refining Slice 1.
 
 **Expected Behaviour**
-1. Phase 0 detects XDRS scope, presents epic plan list plus "Start fresh" option, user picks "Start fresh".
+1. Phase 0 detects XDRS scope, presents epic initiative list plus "Start fresh" option, user picks "Start fresh".
 2. Phases 1–7 run normally for Slice 1.
-3. At Phase 8, because the context is "start fresh" (no active plan doc), the two deferred slices trigger a `vscode_askQuestions` prompt: "Where should the deferred story slices go?" with options: add to an existing epic plan (lists found epics), create a new epic plan, or save to BACKLOG.md.
-4. Skill applies the chosen action (e.g., creates placeholder files for the two deferred slices and inserts `- [Slice description — pending](.assets/userstory-NNN-slug.md)` task entries in the chosen epic plan, or appends descriptions to BACKLOG.md).
+3. At Phase 8, because the context is "start fresh" (no active initiative doc), the two deferred slices trigger a `vscode_askQuestions` prompt: "Where should the deferred story slices go?" with options: add to an existing epic initiative (lists found epics), create a new epic initiative, or save to TODO.md.
+4. Skill applies the chosen action (e.g., creates placeholder files for the two deferred slices and inserts `- [Slice description — pending](.assets/userstory-NNN-slug.md)` task entries in the chosen epic initiative, or appends a Group/Part entry to TODO.md).
 
 **Assertions**
-- [ ] Phase 0 presents the XDRS epic plan list even in "start fresh" mode.
-- [ ] Deferred slices do NOT go silently to BACKLOG.md when an XDRS scope is present.
+- [ ] Phase 0 presents the XDRS epic initiative list even in "start fresh" mode.
+- [ ] Deferred slices do NOT go silently to TODO.md when an XDRS scope is present.
 - [ ] Phase 8 presents a `vscode_askQuestions` destination choice for deferred slices.
-- [ ] If an epic plan is chosen, deferred slices are created as placeholder files and inserted as `- [description — pending](.assets/...)` link entries in the correct Milestone.
+- [ ] If an epic initiative is chosen, deferred slices are created as placeholder files and inserted as `- [description — pending](.assets/...)` link entries in the correct Milestone.
 
 ---
 
-### Scenario 11: Very large story split into multiple slices — no XDRS scope — deferred slices saved to BACKLOG.md
+### Scenario 11: Very large story split into multiple slices — no XDRS scope — deferred slices saved to TODO.md
 
 **Trigger / Input**
 You are an agent with the `151-refine-user-story` skill loaded. The workspace has no `.xdrs/` directory. The user says:
@@ -296,11 +296,11 @@ You are an agent with the `151-refine-user-story` skill loaded. The workspace ha
    - Slice 6: Post-purchase upsell screen
 4. Skill presents `vscode_askQuestions` asking which slice to refine first; user picks Slice 1.
 5. Phases 1–7 run on Slice 1 only. The remaining 5 slices are tracked as Deferred Stories.
-6. At Phase 8, because no plan doc is active, skill presents `vscode_askQuestions`:
-   - **"Save deferred slices to BACKLOG.md"** (recommended)
+6. At Phase 8, because no initiative doc is active, skill presents `vscode_askQuestions`:
+   - **"Save deferred slices to TODO.md"** (recommended)
    - **"Save to a different file"** (open box)
    - **"Skip — do not save"**
-7. User picks "Save deferred slices to BACKLOG.md". Skill appends the 5 deferred slices under a `## Deferred Stories` heading in `BACKLOG.md` at the workspace root (creating the file if needed), each with a one-line description and split rationale.
+7. User picks "Save deferred slices to TODO.md". Skill appends a single `### Group: [checkout flow] — deferred [date]` section under a `## Deferred Stories` heading in `TODO.md` at the workspace root (creating the file if needed), recording Origin, Original objective, and Split rationale, followed by one `#### ` subsection per deferred slice (Slices 2–6), each with its own Objective, Scope, Context captured so far, and Suggested prompt to resume.
 8. Skill outputs the refined story for Slice 1 only.
 
 **Assertions**
@@ -310,10 +310,11 @@ You are an agent with the `151-refine-user-story` skill loaded. The workspace ha
 - [ ] Only the user-selected slice (Slice 1) is refined through Phases 1–7.
 - [ ] The remaining slices appear in a Deferred Items summary at Phase 8.
 - [ ] `vscode_askQuestions` is used at Phase 8 to ask where to save deferred slices (not silently appended).
-- [ ] BACKLOG.md is created (or appended to) at the workspace root with a `## Deferred Stories` section.
-- [ ] Each deferred slice in BACKLOG.md has a one-line description and reason for deferral.
+- [ ] TODO.md is created (or appended to) at the workspace root with a `## Deferred Stories` section containing a single `### Group:` heading for this split.
+- [ ] The Group heading records the origin (151-refine-user-story, Phase 2 Step 3), the original checkout-flow objective, and the split rationale.
+- [ ] Each of the 5 deferred slices appears as its own `#### ` subsection with Objective, Scope, Context captured so far, and a Suggested prompt to resume.
 - [ ] The final output contains exactly one refined story (Slice 1), not all slices.
-- [ ] Skill does NOT offer BACKLOG.md for deferred items from an active plan doc (this scenario has no plan doc — condition satisfied).
+- [ ] Skill does NOT offer TODO.md for deferred items from an active initiative doc (this scenario has no initiative doc — condition satisfied).
 
 ---
 

package/.xdrs/agentme/index.md

@@ -27,7 +27,7 @@ The `agentme` EDRs cover project tooling and structure for each supported langua
 
 ### Business decisions
 
-The `agentme` BDRs cover software development project management practices: how to organize and track epics, features, and user stories using XDRS plan documents. See the full list in the [BDRs Index](bdrs/index.md).
+The `agentme` BDRs cover software development project management practices: how to organize and track epics, features, and user stories using XDRS initiative documents. See the full list in the [BDRs Index](bdrs/index.md).
 
 ## Type Indexes
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agentme",
-  "version": "0.35.0",
+  "version": "0.35.1",
   "description": "",
   "dependencies": {
     "filedist": "^0.39.0"