@deftai/directive-content 0.105.0 → 0.107.0

package/strategies/interview.md

@@ -94,15 +94,15 @@ See `strategies/map.md` for standalone behavior.
 - ! Previously-run strategies MUST display with a run count (e.g., `Research (ran 1×)`)
 - ! No strategy is ever removed from the gate — users can re-run any strategy
 - ! Run counts are read from `completedStrategies` in
-  [`./vbrief/plan.vbrief.json`](../vbrief/vbrief.md#strategy-chaining-fields)
+  [`./xbrief/plan.xbrief.json`](../vbrief/vbrief.md#strategy-chaining-fields)
 
 ### State Tracking
 
 - ! On completion of a preparatory strategy, update `completedStrategies` in
-  `./vbrief/plan.vbrief.json`: increment `runCount`, append artifact paths
+  `./xbrief/plan.xbrief.json`: increment `runCount`, append artifact paths
 - ! Append all new artifact paths to the flat `artifacts` array
 - ! The next strategy and eventual spec generation MUST load all artifacts
-  listed in `plan.vbrief.json`
+  listed in `plan.xbrief.json`
 - ! On brownfield **Add scope** or **Update project definition**, load existing
   PROJECT-DEFINITION identity and preparatory artifacts before asking questions
 
@@ -578,7 +578,7 @@ diff only on the second pass or when the user explicitly asks for it.
 
 ### State Preservation
 
-- ! All `completedStrategies` and `artifacts` in `plan.vbrief.json` MUST be
+- ! All `completedStrategies` and `artifacts` in `plan.xbrief.json` MUST be
   preserved across revisions
 - ! The chaining gate will show updated run counts reflecting the full session history
 

package/strategies/map.md

@@ -50,7 +50,7 @@ Mapping produces artifacts that feed into planning so the agent **follows existi
 
 ! Before writing output artifacts, follow the [Preparatory Guard](./artifact-guards.md#preparatory-guard-light).
 
-Produce a single `vbrief/proposed/{project}-codebase-map.vbrief.json` with four narratives:
+Produce a single `xbrief/proposed/{project}-codebase-map.xbrief.json` with four narratives:
 
 ! After emitting this scope vBRIEF, surface the GitHub-issue tracking hint from [emit-hints.md](./emit-hints.md) — name all three patterns (none / `--umbrella` / `--per-vbrief`).
 
@@ -105,9 +105,9 @@ Produce a single `vbrief/proposed/{project}-codebase-map.vbrief.json` with four
 
 ### Artifact Registration (both modes)
 
-- ! On completion, register artifacts in `./vbrief/plan.vbrief.json`:
+- ! On completion, register artifacts in `./xbrief/plan.xbrief.json`:
   - Update `completedStrategies`: increment `runCount` for `"map"`,
-    append artifact path (`vbrief/proposed/{project}-codebase-map.vbrief.json`)
+    append artifact path (`xbrief/proposed/{project}-codebase-map.xbrief.json`)
   - Append the path to the flat `artifacts` array
 - ! The mapping narratives MUST inform subsequent strategies and spec generation:
   - `Conventions` -> implementation constraints
@@ -130,7 +130,7 @@ Mapping complete. Here's what I found:
   - Conventions: [brief summary]
   - Concerns: [brief summary]
 
-Artifact: vbrief/proposed/{project}-codebase-map.vbrief.json
+Artifact: xbrief/proposed/{project}-codebase-map.xbrief.json
 
 What would you like to do next?
 
@@ -141,7 +141,7 @@ What would you like to do next?
 ```
 
 - ! Present the narrative summary before offering options
-- ! If the user chooses a strategy, invoke it (the artifact persists in `vbrief/proposed/`)
+- ! If the user chooses a strategy, invoke it (the artifact persists in `xbrief/proposed/`)
 - ! If the user chooses "done", confirm the artifact location and exit cleanly
 - ~ Recommend option 1 (interview) when the user's goal is to build or extend
 - ~ Recommend option 4 (done) when the user's goal is exploration or onboarding
@@ -173,7 +173,7 @@ Before an interview — analysis-first, then spec:
 Map this codebase, then use the interview strategy to plan [feature].
 ```
 
-Or set in PROJECT-DEFINITION.vbrief.json narratives:
+Or set in PROJECT-DEFINITION.xbrief.json narratives:
 ```json
 "Strategy": "strategies/map.md"
 ```

package/strategies/probe.md

@@ -73,46 +73,50 @@ Walk the decision tree depth-first. For each unresolved branch:
 
 ! Before writing output artifacts, follow the [Preparatory Guard](./artifact-guards.md#preparatory-guard-light).
 
-### Mechanical guard (`scripts/probe_session.py`)
+### Mechanical guard (`deft probe-session`)
 
 Probe completion is enforced mechanically — not by prose alone. A per-clone
 session file at `.deft/probe-session.json` records whether the session is still
 `interrogate` or `complete`, plus the probe `target`, `currentBranch`, and
 `resolvedDecisions`.
 
+**Waiver (#3556):** The probe skill keeps the no-artifact guard and does not
+require `deft probe-session`. This strategy names `deft probe-session`.
+Silence is not agreement.
+
 - ! At probe start, record the session:
-  `uv run python scripts/probe_session.py start --target <scope>`
+  `deft probe-session start --target <scope>`
 - ! While interrogating, record locked/deferred/risk-accepted decisions and
   branch focus with `record` / `set-branch` subcommands as branches resolve
 - ! Before writing probe output or registering `completedStrategies.probe`,
   mark the session complete:
-  `uv run python scripts/probe_session.py complete`
+  `deft probe-session complete`
 - ! Immediately before artifact or plan registration, run the guard:
-  - `uv run python scripts/probe_session.py guard-artifact --path vbrief/proposed/{scope}-probe.vbrief.json`
-  - `uv run python scripts/probe_session.py guard-plan-registration`
+  - `deft probe-session guard-artifact --path xbrief/proposed/YYYY-MM-DD-{scope}-probe.xbrief.json`
+  - `deft probe-session guard-plan-registration`
 - ⊗ Write probe artifacts or update `completedStrategies.probe` while the
   session state is still `interrogate` — the guard exits non-zero with an
   actionable recovery message
 
 **Recovery when the guard blocks handoff:** continue interrogation until the
 [transition criteria](#transition-criteria-probe-complete) are met, record
-decisions with `probe_session.py record`, run `probe_session.py complete`,
-then retry the guard before writing artifacts or updating `plan.vbrief.json`.
+decisions with `deft probe-session record`, run `deft probe-session complete`,
+then retry the guard before writing artifacts or updating `plan.xbrief.json`.
 
-`{scope}` is the project name from `PROJECT-DEFINITION.vbrief.json`, or the
+`{scope}` is the project name from `PROJECT-DEFINITION.xbrief.json`, or the
 feature/component name if probing a sub-scope. Use the same value consistently
 throughout the session. Examples: `my-app-probe`, `auth-probe`.
 
-- ! Produce a `vbrief/proposed/{scope}-probe.vbrief.json` scope vBRIEF with three mandatory narratives:
+- ! Produce a `xbrief/proposed/YYYY-MM-DD-{scope}-probe.xbrief.json` scope xBRIEF with three mandatory narratives:
   - `LockedDecisions` — what was resolved and why (when the lock is an intentional under-build, include dual-path graduation fields: `now`, `later`, `graduationRef`, `trigger`, `status` — see [Graduation (Now+Later)](#graduation-nowlater-when-locking-an-under-build-2899))
   - `SurfacedRisks` — concerns raised, even if not fully resolved
   - `DeferredDecisions` — explicitly acknowledged items with justification
 - ! Each entry in a narrative includes: **question asked**, **answer given**, **status** (locked / deferred / risk-accepted)
-- ! This vBRIEF is injected into all downstream work: planning, execution, verification
-- ! Persist significant decisions as vBRIEF narratives on the relevant plan items
-- ⊗ Write probe output to a hand-authored markdown file — use vBRIEF narratives for token-efficient, machine-consumable agent consumption (mirrors the [discuss](./discuss.md) and [research](./research.md) output contracts so the chaining-gate flow-through guarantee is mechanical, not aspirational)
+- ! This xBRIEF is injected into all downstream work: planning, execution, verification
+- ! Persist significant decisions as xBRIEF narratives on the relevant plan items
+- ⊗ Write probe output to a hand-authored markdown file — use xBRIEF narratives for token-efficient, machine-consumable agent consumption (mirrors the [discuss](./discuss.md) and [research](./research.md) output contracts so the chaining-gate flow-through guarantee is mechanical, not aspirational)
 
-! After emitting the probe scope vBRIEF to `vbrief/proposed/`, surface the GitHub-issue tracking hint from [emit-hints.md](./emit-hints.md) — name all three patterns (none / `--umbrella` / `--per-vbrief`).
+! After emitting the probe scope xBRIEF to `xbrief/proposed/`, surface the GitHub-issue tracking hint from [emit-hints.md](./emit-hints.md) — name all three patterns (none / `--umbrella` / `--per-vbrief`).
 
 ## Graduation (Now+Later) when locking an under-build (#2899)
 
@@ -142,15 +146,15 @@ Glossary naming for Graduation is owned by sibling work (#2907); this section is
 
 ## Then: Chaining Gate
 
-After the probe is complete and `vbrief/proposed/{scope}-probe.vbrief.json` is
+After the probe is complete and `xbrief/proposed/YYYY-MM-DD-{scope}-probe.xbrief.json` is
 written, return to the [chaining gate](./interview.md#chaining-gate).
 
-- ! On completion, register artifacts in `./vbrief/plan.vbrief.json`:
+- ! On completion, register artifacts in `./xbrief/plan.xbrief.json`:
   - Update `completedStrategies`: increment `runCount` for `"probe"`,
-    append artifact path (`vbrief/proposed/{scope}-probe.vbrief.json`)
+    append artifact path (`xbrief/proposed/YYYY-MM-DD-{scope}-probe.xbrief.json`)
   - Append the path to the flat `artifacts` array
 - ! Return to [interview.md Chaining Gate](./interview.md#chaining-gate)
-- ! The `LockedDecisions`, `SurfacedRisks`, and `DeferredDecisions` narratives from `vbrief/proposed/{scope}-probe.vbrief.json` MUST flow
+- ! The `LockedDecisions`, `SurfacedRisks`, and `DeferredDecisions` narratives from `xbrief/proposed/YYYY-MM-DD-{scope}-probe.xbrief.json` MUST flow
   into subsequent strategies and spec generation:
   - Locked decisions become constraints in the specification
   - Surfaced risks become NFRs or explicit acceptance criteria
@@ -174,4 +178,4 @@ written, return to the [chaining gate](./interview.md#chaining-gate).
 - ⊗ Using codebase exploration as a substitute for asking the user about deliberate design choices
 - ⊗ Stopping when the conversation feels comfortable — stop when no new branches emerge
 - ⊗ Ending after probe without chaining back to the gate (chained mode; in standalone context, returning to the invoking strategy's menu satisfies the completion requirement per the [standalone-context rule](#then-chaining-gate))
-- ⊗ Writing probe output to a plain markdown file (`{scope}-probe.md`) instead of the canonical `vbrief/proposed/{scope}-probe.vbrief.json` scope vBRIEF — plain markdown bypasses the [Preparatory Guard](./artifact-guards.md#preparatory-guard-light) and breaks the downstream-consumer flow-through guarantee
+- ⊗ Writing probe output to a plain markdown file (`{scope}-probe.md`) instead of the canonical `xbrief/proposed/YYYY-MM-DD-{scope}-probe.xbrief.json` scope xBRIEF — plain markdown bypasses the [Preparatory Guard](./artifact-guards.md#preparatory-guard-light) and breaks the downstream-consumer flow-through guarantee

package/strategies/rapid.md

@@ -10,7 +10,7 @@ Quick prototyping workflow -- v0.20 date-prefixed story vBRIEF output with minim
 
 **Ceremony dial (#3214):** when `plan.policy.ceremonyDial` (or session inputs) selects depth `rapid` — default for S-task × frontier model on a project-shaped session — session ritual / gate depth follows this light path. See `task policy:show --field=ceremonyDial`. Non-project sessions select `minimal` and compose the #3014 minimal AGENTS profile research pointer instead.
 
-**v0.20 note (s5-migrate-speckit-rapid-enterprise / #1166):** Rapid now emits only the canonical v0.20 shape (date-prefixed story vBRIEFs in proposed/, full PROJECT-DEFINITION.vbrief.json via task project:render, seeded lifecycle folders, no legacy specification.vbrief.json). See the dedicated ## v0.20 Output Shape section and the canonical contract `strategies/v0-20-contract.md` (s1-contract of #1166).
+**v0.20 note (s5-migrate-speckit-rapid-enterprise / #1166):** Rapid now emits only the canonical v0.20 shape (date-prefixed story vBRIEFs in proposed/, full PROJECT-DEFINITION.xbrief.json via task project:render, seeded lifecycle folders, no legacy specification.vbrief.json). See the dedicated ## v0.20 Output Shape section and the canonical contract `strategies/v0-20-contract.md` (s1-contract of #1166).
 
 Legend (from RFC2119): !=MUST, ~=SHOULD, ≉=SHOULD NOT, ⊗=MUST NOT, ?=MAY.
 
@@ -38,7 +38,7 @@ Legend (from RFC2119): !=MUST, ~=SHOULD, ≉=SHOULD NOT, ⊗=MUST NOT, ?=MAY.
 
 ! Describe the prototype goal in one sentence: what are you trying to learn or prove?
 
-- ! Record the goal in a new date-prefixed story vBRIEF written to `vbrief/proposed/YYYY-MM-DD-<kebab-slug>.vbrief.json` (e.g. as the plan title or a brief narrative in the v0.6 schema). Use today's date for the prefix and a descriptive slug.
+- ! Record the goal in a new date-prefixed story vBRIEF written to `xbrief/proposed/YYYY-MM-DD-<kebab-slug>.xbrief.json` (e.g. as the plan title or a brief narrative in the v0.6 schema). Use today's date for the prefix and a descriptive slug.
 - ~ Include a time-box if applicable (e.g. "4-hour spike")
 - ⊗ Skip this step -- even throwaway work needs a clear objective
 
@@ -54,11 +54,11 @@ Legend (from RFC2119): !=MUST, ~=SHOULD, ≉=SHOULD NOT, ⊗=MUST NOT, ?=MAY.
 
 ! Before writing output artifacts, follow the guards in [artifact-guards.md](./artifact-guards.md) (Preparatory Guard for proposed/ scope items; Spec-Generating Guard for PROJECT-DEFINITION).
 
-! Write a slim story scope vBRIEF to `vbrief/proposed/YYYY-MM-DD-<kebab-slug>.vbrief.json` -- no PRD, no approval gate. Decompose the rapid plan into one or more focused, buildable story vBRIEFs (v0.6 schema) rather than a monolithic legacy spec.
+! Write a slim story scope vBRIEF to `xbrief/proposed/YYYY-MM-DD-<kebab-slug>.xbrief.json` -- no PRD, no approval gate. Decompose the rapid plan into one or more focused, buildable story vBRIEFs (v0.6 schema) rather than a monolithic legacy spec.
 
 - ! Use the Light path from [interview.md](./interview.md) unconditionally
 - ! Mark `plan.status` as `draft` (not `approved`) to signal prototype quality
-- ! After the proposed/ vBRIEF(s) are written, invoke `task project:render` (from repo root) to generate/refresh the complete `vbrief/PROJECT-DEFINITION.vbrief.json`
+- ! After the proposed/ vBRIEF(s) are written, invoke `task project:render` (from repo root) to generate/refresh the complete `xbrief/PROJECT-DEFINITION.xbrief.json`
 - ~ Keep tasks coarse-grained -- 3-5 tasks is typical for a spike
 - ⊗ Generate a PRD or require approval -- rapid skips both
 - ⊗ Hand-author `SPECIFICATION.md` directly -- it is a rendered derivative only (see v0.20 Output Shape)
@@ -86,9 +86,9 @@ Legend (from RFC2119): !=MUST, ~=SHOULD, ≉=SHOULD NOT, ⊗=MUST NOT, ?=MAY.
 
 ## Output Artifacts
 
-- `vbrief/proposed/YYYY-MM-DD-*.vbrief.json` (one or more) -- lightweight story scope vBRIEF(s) with `draft` status (primary artifact; date-prefixed per v0.20 contract)
-- `vbrief/PROJECT-DEFINITION.vbrief.json` -- complete project gestalt + items registry (via `task project:render` invoked by Rapid)
-- `vbrief/{proposed,pending,active,completed,cancelled}/` -- all five lifecycle folders seeded
+- `xbrief/proposed/YYYY-MM-DD-*.xbrief.json` (one or more) -- lightweight story scope vBRIEF(s) with `draft` status (primary artifact; date-prefixed per v0.20 contract)
+- `xbrief/PROJECT-DEFINITION.xbrief.json` -- complete project gestalt + items registry (via `task project:render` invoked by Rapid)
+- `xbrief/{proposed,pending,active,completed,cancelled}/` -- all five lifecycle folders seeded
 - (optional derivative) `SPECIFICATION.md` -- read-only human-readable export (includes deprecated-redirect sentinel; via `task spec:render` if invoked)
 - Prototype code (may be discarded)
 - Findings summary (inline in the proposed/ vBRIEF or as a separate note)
@@ -97,7 +97,7 @@ Legend (from RFC2119): !=MUST, ~=SHOULD, ≉=SHOULD NOT, ⊗=MUST NOT, ?=MAY.
 
 ## Fits into Chaining Gate
 
-Rapid is a **spec-generating** strategy. Selecting it at the chaining gate produces date-prefixed story vBRIEF(s) in `vbrief/proposed/` (and refreshes `vbrief/PROJECT-DEFINITION.vbrief.json` via `task project:render`) and moves directly to implementation. There is no chaining back to preparatory strategies. See the v0.20 Output Shape section below for the exact contract.
+Rapid is a **spec-generating** strategy. Selecting it at the chaining gate produces date-prefixed story vBRIEF(s) in `xbrief/proposed/` (and refreshes `xbrief/PROJECT-DEFINITION.xbrief.json` via `task project:render`) and moves directly to implementation. There is no chaining back to preparatory strategies. See the v0.20 Output Shape section below for the exact contract.
 
 ---
 
@@ -126,11 +126,11 @@ Rapid lightens cold ceremony only. The **positive verification content** of the
 
 This strategy has been migrated to the full v0.20 output shape so rapid-generated projects are accepted by the build skill Pre-Cutover Detection Guard with zero errors on first attempt (resolves the rapid row from the #1166 inconsistency table and the s5 story acceptance criteria).
 
-- ! Seed the five lifecycle folders under `vbrief/` if any are missing: `proposed/`, `pending/`, `active/`, `completed/`, `cancelled/`.
-- ! Emit story scope items exclusively as date-prefixed scope vBRIEFs: `vbrief/proposed/YYYY-MM-DD-<kebab-slug>.vbrief.json` (use the run's creation date for the prefix; choose descriptive slugs). Decompose the rapid plan into one or more focused, buildable story vBRIEFs (v0.6 schema) rather than a monolithic legacy spec.
-- ! After the proposed/ stories are written, invoke `task project:render` (run from the repo root) to generate/refresh the complete `vbrief/PROJECT-DEFINITION.vbrief.json` (items registry is derived from the lifecycle folders).
+- ! Seed the five lifecycle folders under `xbrief/` if any are missing: `proposed/`, `pending/`, `active/`, `completed/`, `cancelled/`.
+- ! Emit story scope items exclusively as date-prefixed scope vBRIEFs: `xbrief/proposed/YYYY-MM-DD-<kebab-slug>.xbrief.json` (use the run's creation date for the prefix; choose descriptive slugs). Decompose the rapid plan into one or more focused, buildable story vBRIEFs (v0.6 schema) rather than a monolithic legacy spec.
+- ! After the proposed/ stories are written, invoke `task project:render` (run from the repo root) to generate/refresh the complete `xbrief/PROJECT-DEFINITION.xbrief.json` (items registry is derived from the lifecycle folders).
 - ⊗ Never emit `vbrief/specification.vbrief.json` (or any legacy dual-write).
-- ~ `SPECIFICATION.md` at the project root, if produced at all, must be only a read-only derivative (e.g. via `task spec:render` after the vbriefs exist) that includes the v0.20 deprecated-redirect sentinel. The source of truth is the vbrief/ lifecycle stories + PROJECT-DEFINITION.
+- ~ `SPECIFICATION.md` at the project root, if produced at all, must be only a read-only derivative (e.g. via `task spec:render` after the vbriefs exist) that includes the v0.20 deprecated-redirect sentinel. The source of truth is the xbrief/ lifecycle stories + PROJECT-DEFINITION.
 - ! Before writing any proposed/ stories or PROJECT-DEFINITION, follow the guards in [artifact-guards.md](./artifact-guards.md) (Preparatory Guard for scope items in proposed/; Spec-Generating Guard for PROJECT-DEFINITION).
 - ! Final output tree must pass the deterministic v0.20 strategy output validation gate (s2-deterministic-gate) and the build Pre-Cutover Detection Guard with zero warnings/errors. See full acceptance in the s5 vBRIEF and the 1166 decomposition.
 - ! Cite the canonical contract `strategies/v0-20-contract.md` (s1-contract) for the exact shape and the per-strategy table row.
@@ -143,9 +143,9 @@ This strategy has been migrated to the full v0.20 output shape so rapid-generate
 
 | Artifact | Purpose | Created By |
 |----------|---------|------------|
-| `vbrief/proposed/YYYY-MM-DD-*.vbrief.json` (one or more) | Focused story scope items (date-prefixed per vbrief convention and v0.20 contract) | Rapid |
-| `vbrief/PROJECT-DEFINITION.vbrief.json` | Project identity gestalt + complete scope items registry | `task project:render` (invoked by Rapid) |
-| `vbrief/{proposed,pending,active,completed,cancelled}/` | All five lifecycle folders seeded | Rapid |
+| `xbrief/proposed/YYYY-MM-DD-*.xbrief.json` (one or more) | Focused story scope items (date-prefixed per vbrief convention and v0.20 contract) | Rapid |
+| `xbrief/PROJECT-DEFINITION.xbrief.json` | Project identity gestalt + complete scope items registry | `task project:render` (invoked by Rapid) |
+| `xbrief/{proposed,pending,active,completed,cancelled}/` | All five lifecycle folders seeded | Rapid |
 | (optional derivative) `SPECIFICATION.md` | Human-readable plan (includes deprecated-redirect sentinel) | `task spec:render` (if invoked) |
 
 **Pre-v0.20 / legacy artifacts that MUST NOT be produced by this strategy:**
@@ -154,7 +154,7 @@ This strategy has been migrated to the full v0.20 output shape so rapid-generate
 - Primary handoff `SPECIFICATION.md` at project root (without sentinel)
 - Bare-named vBRIEFs in proposed/
 
-See the full table and rules in `strategies/v0-20-contract.md` (rapid row: Must Create Lifecycle Folders: Yes; Must Write PROJECT-DEFINITION: Yes; Scope vBRIEFs Location: proposed/YYYY-MM-DD-*.vbrief.json only; specification.vbrief.json: Never; SPECIFICATION.md / PROJECT.md: Omit or deprecation redirect only).
+See the full table and rules in `strategies/v0-20-contract.md` (rapid row: Must Create Lifecycle Folders: Yes; Must Write PROJECT-DEFINITION: Yes; Scope vBRIEFs Location: proposed/YYYY-MM-DD-*.xbrief.json only; specification.vbrief.json: Never; SPECIFICATION.md / PROJECT.md: Omit or deprecation redirect only).
 
 ---
 

package/strategies/research.md

@@ -47,7 +47,7 @@ Prompt:
 
 ! Before writing output artifacts, follow the [Preparatory Guard](./artifact-guards.md#preparatory-guard-light).
 
-Produce `vbrief/proposed/{feature}-research.vbrief.json` with two mandatory narratives:
+Produce `xbrief/proposed/{feature}-research.xbrief.json` with two mandatory narratives:
 
 ! After emitting this scope vBRIEF, surface the GitHub-issue tracking hint from [emit-hints.md](./emit-hints.md) — name all three patterns (none / `--umbrella` / `--per-vbrief`).
 
@@ -134,7 +134,7 @@ all trigger a hit.
 - ! Research the **current feature only** — not the entire project
 - ! Time-box research — if it takes longer than the feature, scope is wrong
 - ⊗ Research as a reason to delay execution indefinitely
-- ~ Research persists as a vBRIEF in `vbrief/proposed/`
+- ~ Research persists as a vBRIEF in `xbrief/proposed/`
 
 ---
 
@@ -143,13 +143,13 @@ all trigger a hit.
 After research is complete, return to the [chaining gate](./interview.md#chaining-gate)
 so the user can run additional preparatory strategies or proceed to spec generation.
 
-- ! On completion, register artifacts in `./vbrief/plan.vbrief.json`:
+- ! On completion, register artifacts in `./xbrief/plan.xbrief.json`:
   - Update `completedStrategies`: increment `runCount` for `"research"`,
-    append artifact path (`vbrief/proposed/{feature}-research.vbrief.json`)
+    append artifact path (`xbrief/proposed/{feature}-research.xbrief.json`)
   - Append the path to the flat `artifacts` array
 - ! Return to [interview.md Chaining Gate](./interview.md#chaining-gate)
 - ! Present the chaining gate as a blocking question and wait for a user selection before any spec generation or additional scope vBRIEF generation.
-- ! Explain at handoff that `completedStrategies` records that research ran, while `vbrief/proposed/{feature}-research.vbrief.json` remains a planning artifact in the scope lifecycle until a later strategy promotes or consumes it.
+- ! Explain at handoff that `completedStrategies` records that research ran, while `xbrief/proposed/{feature}-research.xbrief.json` remains a planning artifact in the scope lifecycle until a later strategy promotes or consumes it.
 - ! The research findings MUST inform subsequent strategies and spec generation:
   - "Don't Hand-Roll" items become constraints in the specification
   - "Common Pitfalls" become acceptance criteria or NFRs
@@ -167,7 +167,7 @@ so the user can run additional preparatory strategies or proceed to spec generat
 
 1. **Scope confirmation** -- Ask the blocking scope-confirmation prompt, wait for the user, and record scope/artifact/sensitivity inputs
 2. **Survey** -- Check existing project dependencies, official docs, and known pitfalls
-3. **Document** -- Produce `vbrief/proposed/{feature}-research.vbrief.json` with `DontHandRoll` and `CommonPitfalls` narratives
+3. **Document** -- Produce `xbrief/proposed/{feature}-research.xbrief.json` with `DontHandRoll` and `CommonPitfalls` narratives
 4. **Chain** -- Return to [interview.md Chaining Gate](./interview.md#chaining-gate), or -- if invoked from a standalone strategy (e.g. map's standalone next-step menu) -- return to the invoking strategy's menu per the [standalone-context rule](#then-chaining-gate) above
 
 ## Anti-Patterns

package/strategies/roadmap.md

@@ -6,4 +6,4 @@
 > See **[skills/deft-directive-refinement/SKILL.md](../skills/deft-directive-refinement/SKILL.md)**
 > for issue ingest, evaluation, and promotion/demotion workflows.
 >
-> Run `task roadmap:render` to regenerate `ROADMAP.md` from `vbrief/` lifecycle folders.
+> Run `task roadmap:render` to regenerate `ROADMAP.md` from `xbrief/` lifecycle folders (legacy `vbrief/` is read-accepted).