Between 2026-04-13 and 2026-04-14, James enriched quorum-pipeline-walkthrough.md substantially, establishing it as the source of truth for pipeline experience design (complementing the PRD's quorumPipeline YAML which owns structural definition). The walkthrough now materially diverges from the PRD, UX spec, and epics across nearly every pipeline step. Without this alignment pass, downstream artifacts (stories, design specs, implementation) will be built against stale definitions.
Trigger: Walkthrough enrichment (Round 1). Scope classification: Moderate — backlog reorganization needed (new Epic 9 for Step 13, several story AC expansions, new FRs). No rollback required; no MVP reduction. Path forward: Direct adjustment — modify/add stories and sections within existing plan.
Epic Impact: - Epic 3 (Vision capture) — Story 3.1, 3.3, 3.4, 3.7 expanded - Epic 4 (Three-pillar filter) — Story 4.1 expanded; new Story 4.6 added - Epic 5 (Planning artifacts) — Story 5.4, 5.5, 5.7 expanded - New Epic 9 — Portfolio Document output (Step 13)
Artifact Conflicts:
- prd.md — pipeline YAML and FRs both lag walkthrough
- epics.md — missing Step 13 coverage; several story ACs underspecified
- ux-design-specification.md — rail labels and journey steps reference Figma-Make-specific language; missing Step 13
Technical Impact: None at code level (no build work started). Downstream story generation will pick up the updated specs.
Direct Adjustment — 52 edits distributed as: - PRD: 20 edits (pipeline YAML, FRs, revisedPipeline string, keyArtifacts) - UX Spec: 8 edits (rail labels, component list, journey steps, canonical table) - Epics/Stories: 13 edits (story AC expansions, new Story 4.6, new Epic 9, FR Coverage Map) - New artifacts: 4 edits (personal portfolio doc, MEMORY.md reference, update cadence, export script deferral note)
Effort: ~1 session (this session). Risk: Low. All changes are additive or clarifying; no breaking changes to existing architecture decisions or MVP scope. Timeline impact: None — still pre-build.
See companion sections below (Step 1 → Step 13) and per-artifact diffs recorded in commit messages.
| Step | New in Walkthrough | Edits |
|---|---|---|
| 1 | Full team, 8-category Kitchen Sink Framework, 4 structured outputs | E-01..E-06 |
| 2a | Tool-agnostic, Doc/HTML/PDF download | E-07..E-11 |
| 2b | All screens (not just landing) | E-12..E-14 |
| 2c | Full sitemap output | E-15..E-19 |
| 3 | Collaborate/AI-handled modes, release allocation output | E-20..E-27 |
| 4 | — | — |
| 5 | — | — |
| 5.25 | Journey + screen refresh, fix-up design prompt, Doc/HTML exports | E-28..E-31 |
| 5.5 | Text + HTML export formats | E-32..E-34 |
| 6, 7 | — | — |
| 8 | Refinement loop + PDF/DOC/HTML exports | E-35..E-38 |
| 9 | — | — |
| 10a–12 | — | — |
| 13 (NEW) | Portfolio Document feature | E-39..E-45 |
| Meta | Figma-Make genericization + Step 13 cross-wiring | E-46..E-48 |
| Personal portfolio | Living meta-doc for James's BMad build process | E-49..E-52 |
Scope: Moderate — handled by Scrum Master (this workflow).
Deliverables:
- Sprint Change Proposal (this document)
- Updated PRD, epics, UX spec
- New james-quorum-build-portfolio.md living doc
- Updated MEMORY.md with portfolio reference
Success criteria: - Implementation-readiness re-check passes post-edits - Sprint planning (next workflow) can proceed against updated epics - Walkthrough and PRD no longer diverge