docs(roadmap): add Phase 2 gap analysis stories P/Q/R/S/T

[MScottAdams]

Summary

Add 5 new stories to Phase 2 (vBRIEF Architecture Cutover) identified through gap analysis of the existing story set. Updates tier placements and Open Issues Index.

Changes

New stories added to ROADMAP.md Phase 2 tiers:

• Story R: Validation tooling for vBRIEF-centric document model #333 Story R: Validation tooling for vBRIEF-centric model (Tier 1)
• Story P: Ancillary doc updates for vBRIEF-centric model #331 Story P: Ancillary doc updates (Tier 2)
• Story Q: Go installer rewrite for deft-directive-* namespace #332 Story Q: Go installer rewrite for deft-directive-* namespace (Tier 3)
• Story S: Pre-cutover detection and backward compatibility guard #334 Story S: Pre-cutover detection and backward compatibility guard (Tier 4)
• Story T: Release and version boundary items (v0.20.0) #335 Story T: Release and version boundary items v0.20.0 (Tier 5)

Updated existing story descriptions:

• Story F (Story F: deft-directive-build, review-cycle, pre-pr (rename + update) #315): Installer scope moved to dedicated Story Q
• Story G (Story G: deft-directive-refinement (rename + rewrite from roadmap-refresh) #316): Added dependency annotation on Stories B + O
• Story C (Story C: Migration script (task migrate:vbrief) #312): Expanded migration scope (deprecation redirects, .agents/skills/ rename, content check)

Also filed (not in this PR):

• vBRIEF as source of truth for ALL .md files in Directive (schema extensions + full migration) #336 -- vBRIEF as source of truth for ALL .md files (post-Phase 2, parked for future planning)

GitHub issue updates (outside this PR):

• Story C: Migration script (task migrate:vbrief) #312 body expanded with migration additions
• Story F: deft-directive-build, review-cycle, pre-pr (rename + update) #315 body updated to remove installer scope
• RFC: vBRIEF-centric document model for Deft Directive #309 addendum comment with all new stories and dependency annotations

Checklist

• ROADMAP.md updated with new stories in correct tiers
• Open Issues Index updated with 5 new entries
• All 5 new issues filed on GitHub (Story P: Ancillary doc updates for vBRIEF-centric model #331-Story T: Release and version boundary items (v0.20.0) #335)
• Existing issues Story C: Migration script (task migrate:vbrief) #312, Story F: deft-directive-build, review-cycle, pre-pr (rename + update) #315 updated
• RFC RFC: vBRIEF-centric document model for Deft Directive #309 addendum comment posted

---

Conversation

[greptile-apps]

Greptile Summary

This PR adds 5 gap-analysis stories (P–T, issues #331–#335) to the Phase 2 vBRIEF Architecture Cutover roadmap, updates descriptions for Stories C, F, and G, and adds 5 entries to the Open Issues Index. All changes are documentation-only in ROADMAP.md.

Confidence Score: 5/5

Safe to merge — documentation-only change with no code impact.

All five new story entries are internally consistent, the Open Issues Index rows are correctly numbered and formatted, and the existing story description updates accurately reflect scope movement. Both inline comments are P2 suggestions about sequencing nuances, not correctness blockers.

No files require special attention.

Important Files Changed

Filename	Overview
ROADMAP.md	Adds 5 new Phase 2 stories (P/Q/R/S/T) across all tiers, updates 3 existing story descriptions, and appends 5 rows to the Open Issues Index; all changes are internally consistent with no code impact.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    T1["Tier 1 — Foundation (parallelizable)\n#310 Story A · #311 Story B · #312 Story C\n#323 Story N · #324 Story O\n#333 Story R: Validation tooling (new)"]
    T2["Tier 2 — Framework Docs (depends on A)\n#313 Story D\n#331 Story P: Ancillary doc updates (new)"]
    T3["Tier 3 — Skills (depends on A + D; parallelizable)\n#314 Story E · #317 Story H · #318 Story I · #319 Story J\n#315 Story F · #316 Story G\n#332 Story Q: Go installer rewrite (new)"]
    T4["Tier 4 — CLI & Tests (depends on all above)\n#320 Story K · #321 Story L\n#334 Story S: Pre-cutover detection (new)"]
    T5["Tier 5 — Post-Cutover\n#322 Story M\n#335 Story T: Release & version boundary (new)"]

    T1 --> T2
    T2 --> T3
    T3 --> T4
    T4 --> T5

Loading

Prompt To Fix All With AI

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

Comment:
**Story R tier placement may warrant a sequencing note**

Story R's scope (scope validator, PROJECT-DEFINITION validator, folder/status consistency, epic-story links) is functionally defined by Story A's output — the validation schemas and folder conventions can't be fully spec'd until Story A lands. Placing R in the same parallelizable Tier 1 is workable but may lead to iterative rework if A's model evolves mid-implementation. Consider either noting an implicit "design-after-A" sequencing expectation in the story description, or bumping R to Tier 2 where Story D already sits for model-dependent work.

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: 42

Comment:
**Story Q placed in same tier as the skills it enumerates**

Story Q lists `allSkillNames` as a deliverable, but the canonical names for the `deft-directive-*` skills are being finalized in the same Tier 3 (Stories E, F, G, H, I, J). Since all Tier 3 items are marked "parallelizable via swarm," Story Q could lock in skill names before any of the rename/rewrite stories converge. Worth adding a note on Story Q (or this entry) that the `allSkillNames` list should be treated as draft until all sibling Tier 3 stories confirm their final identifiers.

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

_{Reviews (1): Last reviewed commit: "docs(roadmap): add Phase 2 gap analysis ..." | Re-trigger Greptile}