docs(epics): refresh roadmap with pilot v1 / MENA-10 / launch phases#3
Open
abdout wants to merge 2 commits into
Open
docs(epics): refresh roadmap with pilot v1 / MENA-10 / launch phases#3abdout wants to merge 2 commits into
abdout wants to merge 2 commits into
Conversation
Reframes the existing 28-epic production roadmap (`epic-prod-01..28`)
around three release phases tied to the live King Fahad Schools pilot:
- Phase 1 Pilot v1 (3 sprints, ~7 weeks, ~296 pts, target 2026-07-12)
- Phase 2 MENA-10 (5 sprints, ~10 weeks, ~411 pts, target 2026-09-15)
- Phase 3 Public Launch (8 sprints, ~16 weeks, ~408 pts, target 2026-12-20)
Epic IDs and story IDs are preserved. Build phases (A Foundation → F
Production) describe dependency order; release phases (1/2/3) describe
ship order. The two axes are orthogonal — see .bmad/epics/README.md.
Changes
- Add .bmad/epics/{README,phase-1-pilot-v1,phase-2-mena10,phase-3-launch}.md
- Update .bmad/epics/epic-prod-overview.md with Release Phases section
and reference King Fahad pilot in the why-a-new-roadmap motivation
- Update .bmad/bmm-workflow-status.yaml with release_phases block,
per-epic phase_1_story_ids enumeration, and release_phase_concentration
- Rewrite docs/prd.md Milestones around Pilot/MENA-10/Launch phases;
update related-documents pointers to the new manifests
- Archive legacy V1 epics (epic-01..17) and V2 backend draft to
.bmad/epics/archive/; archive stale docs/epics/* subset alongside
Phase 1 deliberately ships read-only views + admission + signed APK on
Play Internal — explicit deferrals to Phase 2/3 are listed per-epic in
phase-1-pilot-v1.md so the deferrals don't drift into invisibility.
Source plan: ~/.claude/plans/take-web-app-as-precious-turtle.md
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Adds inline `**Phase: Pilot v1**` markers to every story selected for Phase 1 in `phase-1-pilot-v1.md`. Phase 2 and Phase 3 markers intentionally deferred — manifest + `phase_1_story_ids` in the YAML remain the authoritative cross-phase index. Heading-style epics (E01-E11): marker appended after the points bracket. Table-style epics (E19, E25, E26, E27): marker appended to the title cell. Verification: `grep -rE 'Phase: Pilot v1' .bmad/epics/epic-prod-*.md | wc -l` returns 71 (matches the manifest count). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
phase-1-pilot-v1.md(71 stories, 3 sprints, ~296 pts, King Fahad target 2026-07-12),phase-2-mena10.md,phase-3-launch.md, plus README indexepic-01..17) + V2 (epic-v2-01) +docs/epics/*to.bmad/epics/archive/docs/prd.mdMilestones around the three phases; updatesbmm-workflow-status.yamlwithrelease_phases,phase_1_story_ids, andrelease_phase_concentrationblocksWhy now
King Fahad Schools (Pilot Seat 1) conversion conversation is in Jun 2026. The original 32-week plan treats every feature equally and obscures what must ship for the conversion. The release-phase overlay makes "what ships next" obvious without re-deriving priorities from 28 epic files.
Test plan
python -c "import yaml; yaml.safe_load(open('.bmad/bmm-workflow-status.yaml'))"— passesls .bmad/epics/{README,phase-1-pilot-v1,phase-2-mena10,phase-3-launch}.md— all presentls .bmad/epics/archive/— 17 V1 files + V2 file +docs-epics/subdir presentdocs/epics/is empty (legacy moved)epic-prod-overview.md— Release Phases section appears between "28 Epics in 6 Phases" and "Architecture Decisions"phase-1-pilot-v1.md— 71 stories enumerated; dependencies in the sanity check don't cycleOut of scope (deliberately)
**Phase: …**markers inside the 28 individual epic-prod-NN files — the phase manifests + YAMLphase_1_story_idscarry this for now; a follow-up sweep can add inline markers if discoverability needs it/featureis the smoke test of the workflowCloses #2
Source plan:
~/.claude/plans/take-web-app-as-precious-turtle.mdGenerated with Claude Code