docs(roadmap): refresh -- add #301-#304, #305, #307, Phase 2 vBRIEF Cutover (#309+bundle); restructure phases

[MScottAdams]

Summary

Full roadmap refresh session (2026-04-13). Triaged 8 items covering 23 issues, performed stale cleanup, and restructured the phase architecture to prioritize the vBRIEF-centric model cutover.

Related Issues

Triaged (no closes -- roadmap tracking only):
#301, #302, #303, #304, #305, #307, #309, #310, #311, #312, #313, #314, #315, #316, #317, #318, #319, #320, #321, #322, #323, #324

Closed (absorbed):
#308 absorbed by RFC #309

What Changed

Phase 1 Cleanup (4 issues):

• fix(agents): tighten deft-interview routing keyword -- 'interview' collides with spec-creation intent #301 (t1.26.1): tighten deft-interview routing keyword -- bare 'interview' collides with spec-creation intent
• fix(skill): deft-interview invocation contract -- clarify embedded vs delegation usage modes #302 (t1.27.1): clarify deft-interview invocation contract -- embedded vs delegation modes
• fix(skill): deft-interview Rule 5 vs Rule 6 inconsistency -- 'ok' accepted for default but not at confirmation gate #303 (t1.28.1): fix deft-interview Rule 5 vs Rule 6 ok/confirmation-gate inconsistency
• test(skill): add regression test for deft-setup Phase 1/2 referencing deft-interview #304 (t1.29.1): regression test for deft-setup Phase 1/2 referencing deft-interview

Phase 1 Adoption Blockers (2 issues):

• perf(review-cycle): Greptile reviews are slow — investigation + optimization plan #305 (t1.30.1): Greptile review cycle bottlenecks -- 5-change optimization bundle
• fix(skill): deft-review-cycle Approach 2 capability detection gap -- agent claims to yield-poll but no start_agent available and no sleep fallback #307 (t1.31.1): deft-review-cycle Approach 2 silent failure -- add Approach 3 interactive blocking fallback

Phase 2 -- vBRIEF Architecture Cutover (new phase, 16 issues):

• RFC: vBRIEF-centric document model for Deft Directive #309 (RFC) + stories Story A: Update vbrief.md with new vBRIEF-centric document model #310-Story O: Scope lifecycle task commands (task scope:*) #324 (t2.12.1): big-bang cutover to vBRIEF-centric document model; 18 design decisions; all skills renamed deft-directive-*; ROADMAP.md becomes generated artifact
• Closed feat(vbrief): extend vBRIEF source-of-truth to all agent-generated MD artifacts (ROADMAP.md, PRD.md) #308 as absorbed by RFC RFC: vBRIEF-centric document model for Deft Directive #309

Phase restructure:

• Inserted new Phase 2 (vBRIEF Architecture Cutover) as the primary gate after Phase 1
• Shifted existing phases: Documentation & Content Fixes (Phase 3), CI/Testing (Phase 4), Distribution (Phase 5), Features (Phase 6)

Stale cleanup:

• test: add unit tests for v0.17.0 deterministic task scripts #293 (closed): removed from Phase 4 body, struck through in index, moved to Completed
• chore(spec): flip 5 stale [pending] task statuses to [completed] in SPECIFICATION.md (t1.14.1, t1.15.1, t1.18.1, t1.19.1, t1.20.1) #298 (closed): removed from Phase 1 Cleanup body, struck through in index, moved to Completed

SPECIFICATION.md: skeleton spec tasks t1.26.1-t1.31.1 (6 Phase 1 tasks) + t2.12.1 (vBRIEF RFC umbrella)
CHANGELOG.md: single batch entry for full session

Checklist

• /deft:change -- N/A (doc-only roadmap refresh, not a code change)
• CHANGELOG.md -- [Unreleased] entry added
• ROADMAP.md -- updated (this is the ROADMAP.md update)
• Tests pass locally (task check: 1053 passed, 2 xfailed)

---

Generated by Oz: https://app.warp.dev/conversation/dd7ebf91-bd4f-40a5-b26f-b6f09fca1988

[greptile-apps]

Greptile Summary

Doc-only roadmap refresh: adds 6 new Phase 1 issues (#301–#305, #307) and a new Phase 2 vBRIEF Architecture Cutover block (#309+#310–#324), restructures the phase numbering, adds 7 skeleton spec tasks (t1.26.1–t1.31.1, t2.12.1), and moves #293/#298 to Completed.

• A bare - **#301** entry on ROADMAP.md line 15 duplicates the complete entry on line 16 — this is the exact anti-pattern prohibited by the project's roadmap-refresh conventions (deft-roadmap-refresh skill: clarify cleanup convention — remove from phase body, do not strike through in place #196) and should be deleted.
• ## Phase 4 is missing its descriptive title after the restructure; the PR description names it "CI/Testing" but the header wasn't updated to match the other phases.

Confidence Score: 4/5

Safe to merge after removing the duplicate #301 stub and optionally adding the Phase 4 title; no code changes are involved.

One P1 finding (duplicate bare #301 entry violates the project's own anti-pattern rule) keeps this at 4 rather than 5; the remaining two findings are P2 style/consistency items.

ROADMAP.md — duplicate entry on line 15 and missing Phase 4 title on line 104.

Important Files Changed

Filename	Overview
ROADMAP.md	Phase restructure, 6 new Phase 1 items, new Phase 2 vBRIEF block, and stale cleanup — but introduces a duplicate bare #301 entry, a Phase 4 header missing its descriptive title, and #308 absent from the Open Issues Index.
CHANGELOG.md	Single batch "Roadmap Refresh (2026-04-13)" entry under [Unreleased] correctly following the one-batch-per-session convention; counts and descriptions are consistent with ROADMAP.md and SPECIFICATION.md content.
SPECIFICATION.md	Seven new skeleton spec tasks added (t1.26.1–t1.31.1 and t2.12.1), all marked [pending] with placeholder acceptance criteria; task IDs, issue traces, and descriptions are internally consistent with ROADMAP.md entries.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    P1["Phase 1 -- Bug Fixes & Issue Resolution\n#301 #302 #303 #304 (Cleanup)\n#305 #307 (Adoption Blockers)"]
    P2["Phase 2 -- vBRIEF Architecture Cutover NEW\nRFC #309 + Stories #310-#324\n(5 Tiers)"]
    P3["Phase 3 -- Documentation & Content Fixes\n(was Phase 2)"]
    P4["Phase 4 -- CI/Testing\n(was Phase 3)"]
    P5["Phase 5 -- Package Distribution & Install UX\n(was Phase 4)"]
    P6["Phase 6 -- CLI Overhaul & New Features\n(was Phase 5)"]
    P1 --> P2
    P2 --> P3
    P3 --> P4
    P4 --> P5
    P5 --> P6
    T1["Tier 1: Foundation\n#310 #311 #312 #323 #324"]
    T2["Tier 2: Framework Docs\n#313"]
    T3["Tier 3: Skills (swarm)\n#314-#319"]
    T4["Tier 4: CLI + Tests\n#320 #321"]
    T5["Tier 5: Post-cutover\n#322"]
    P2 --> T1 --> T2 --> T3 --> T4 --> T5

Loading

Prompt To Fix All With AI

This is a comment left during a code review.
Path: ROADMAP.md
Line: 15

Comment:
**Stale duplicate `#301` entry**

Line 15 is a bare `- **#301**` with no description — the complete entry follows immediately on line 16. This duplicates the same issue number, which violates the project's own anti-pattern rule against duplicate roadmap entries (see `#196` / `skills/deft-roadmap-refresh`). Readers and automated tooling scanning for `#301` will encounter two rows, the first of which has no useful content.

```suggestion
```

How can I resolve this? If you propose a fix, please make it concise.

---

This is a comment left during a code review.
Path: ROADMAP.md
Line: 104

Comment:
**Phase 4 missing descriptive title**

After the phase restructure the old Phase 3 (CI/Testing) became Phase 4, but the header was not updated to include a name. Every other phase has one — `## Phase 3 -- Documentation & Content Fixes`, `## Phase 5 -- Package Distribution & Install UX`, `## Phase 6 -- CLI Overhaul & New Features`. The PR description itself names this phase "CI/Testing", so the fix is straightforward.

```suggestion
## Phase 4 -- CI/Testing
```

How can I resolve this? If you propose a fix, please make it concise.

---

This is a comment left during a code review.
Path: ROADMAP.md
Line: 484

Comment:
**#308 not tracked in Open Issues Index**

`#308` was absorbed by RFC `#309` and closed, but there is no row for it in the Open Issues Index table. By the established convention (see `#196`) absorbed/closed issues should be struck through with a disposition note. All other absorbed issues (`#101`, `#201`, `#271`, `#85`) are present in the index. A row like the following should be added:

```
| ~~#308~~ | ~~vBRIEF architecture prep -- absorbed by RFC #309~~ | closed -- absorbed by #309 |
```

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (1): Last reviewed commit: "docs(roadmap): refresh -- add #301, #302..." | Re-trigger Greptile}

[greptile-apps]

Stale duplicate #301 entry

Line 15 is a bare - **#301** with no description — the complete entry follows immediately on line 16. This duplicates the same issue number, which violates the project's own anti-pattern rule against duplicate roadmap entries (see #196 / skills/deft-roadmap-refresh). Readers and automated tooling scanning for #301 will encounter two rows, the first of which has no useful content.

Suggested change

### Cleanup

Prompt To Fix With AI

This is a comment left during a code review.
Path: ROADMAP.md
Line: 15

Comment:
**Stale duplicate `#301` entry**

Line 15 is a bare `- **#301**` with no description — the complete entry follows immediately on line 16. This duplicates the same issue number, which violates the project's own anti-pattern rule against duplicate roadmap entries (see `#196` / `skills/deft-roadmap-refresh`). Readers and automated tooling scanning for `#301` will encounter two rows, the first of which has no useful content.

```suggestion
```

How can I resolve this? If you propose a fix, please make it concise.