[VSM-02] Eliminate top bottleneck identified by Value Stream Mapping
Labels: process, devops, p1-critical, effort-medium
Assignee: 👤 Human (triage) + 🤖 Copilot (implementation)
Phase: Phase 1 — AI Foundation
DORA 2025 Source: VSM chapter; “AI increases throughput, also increases instability” finding
Effort: Medium (depends on bottleneck — typically 1–2 days)
Prerequisites: VSM-01
Why This Follows Immediately from VSM-01
The 2025 DORA report warns explicitly: AI increases throughput AND increases instability. The instability materialises at the bottleneck. If you don’t fix the bottleneck before increasing Copilot usage, faster code generation produces faster accumulation of unreviewed, undeployed, or unstable changes.
This issue is intentionally open-ended because VSM-01 determines what the bottleneck actually is. This issue is a placeholder that must be scoped after VSM-01 is complete.
Most Likely Bottleneck Candidates (based on codebase audit)
Based on the current Goald codebase and workflow, the most probable bottlenecks are:
Candidate A: Review Quality (most likely for a solo/small vibe-coding team)
Symptom: PRs sit in “In Review” for > 1 day OR are merged without meaningful review
Fix: GITOPS-04 checklist is too long / not actionable → shorten to 5 must-check items; add Copilot-generated PR summary to every PR body
Candidate B: CI Feedback Speed
Symptom: CI takes > 5 minutes, causing context-switch while waiting
Fix: Parallelise lint + typecheck + test jobs; cache node_modules in CI; only run full E2E suite on main branch, not on every PR
Candidate C: Deployment Friction (likely once EAS Build is configured)
Symptom: Changes merge to main but don’t reach users for days
Fix: Expo OTA updates should publish automatically on merge to main; DEVOPS-03 (EAS Build) should be elevated in priority
Candidate D: Issue Spec Quality
Symptom: Copilot frequently produces wrong output requiring rework
Fix: AIOPS-01 copilot-instructions.md needs enrichment; AIOPS-03 issue templates need to enforce richer context
Acceptance Criteria
These must be filled in after VSM-01 is complete. The issue owner updates this section before moving to “Ready”.
Files to Change (varies by bottleneck)
.github/workflows/ci-quality.yml — if CI speed.github/GITOPS-04-review-checklist.md — if review friction.github/PULL_REQUEST_TEMPLATE.md — add auto-summary sectiondocs/VALUE_STREAM_MAP.md — update with post-fix timings
[VSM-02] Eliminate top bottleneck identified by Value Stream Mapping
Labels:
process,devops,p1-critical,effort-mediumAssignee: 👤 Human (triage) + 🤖 Copilot (implementation)
Phase: Phase 1 — AI Foundation
DORA 2025 Source: VSM chapter; “AI increases throughput, also increases instability” finding
Effort: Medium (depends on bottleneck — typically 1–2 days)
Prerequisites: VSM-01
Why This Follows Immediately from VSM-01
The 2025 DORA report warns explicitly: AI increases throughput AND increases instability. The instability materialises at the bottleneck. If you don’t fix the bottleneck before increasing Copilot usage, faster code generation produces faster accumulation of unreviewed, undeployed, or unstable changes.
This issue is intentionally open-ended because VSM-01 determines what the bottleneck actually is. This issue is a placeholder that must be scoped after VSM-01 is complete.
Most Likely Bottleneck Candidates (based on codebase audit)
Based on the current Goald codebase and workflow, the most probable bottlenecks are:
Candidate A: Review Quality (most likely for a solo/small vibe-coding team)
Symptom: PRs sit in “In Review” for > 1 day OR are merged without meaningful review
Fix: GITOPS-04 checklist is too long / not actionable → shorten to 5 must-check items; add Copilot-generated PR summary to every PR body
Candidate B: CI Feedback Speed
Symptom: CI takes > 5 minutes, causing context-switch while waiting
Fix: Parallelise lint + typecheck + test jobs; cache node_modules in CI; only run full E2E suite on main branch, not on every PR
Candidate C: Deployment Friction (likely once EAS Build is configured)
Symptom: Changes merge to main but don’t reach users for days
Fix: Expo OTA updates should publish automatically on merge to main; DEVOPS-03 (EAS Build) should be elevated in priority
Candidate D: Issue Spec Quality
Symptom: Copilot frequently produces wrong output requiring rework
Fix: AIOPS-01 copilot-instructions.md needs enrichment; AIOPS-03 issue templates need to enforce richer context
Acceptance Criteria
These must be filled in after VSM-01 is complete. The issue owner updates this section before moving to “Ready”.
____________________________docs/VALUE_STREAM_MAP.mdupdated with new timing after fixFiles to Change (varies by bottleneck)
.github/workflows/ci-quality.yml— if CI speed.github/GITOPS-04-review-checklist.md— if review friction.github/PULL_REQUEST_TEMPLATE.md— add auto-summary sectiondocs/VALUE_STREAM_MAP.md— update with post-fix timings