Repository navigation
Add program planning with initiatives, epics, milestones, and metadata design #1652
Description
Parent epic: #1648
Outcome
Add /squad plan program to convert accepted triage into an outcome-oriented delivery structure before PR-sized work is designed.
Requirements
- Propose one initiative rooted in original intent.
- Group work into coherent epics and user-observable features/stories.
- Propose outcome-based GitHub milestones with demonstrations and exit criteria.
- Prefer native issue types and Project fields; propose minimal labels only as fallbacks.
- Label proposals include exact names, descriptions, and intentional color families.
- Preserve existing repository taxonomy unless changes are approved.
Acceptance criteria
- Output distinguishes initiatives, epics, stories/features, and tasks.
- Milestones are demonstrable outcomes, not prose-only phases.
- Every triage item maps to hierarchy or explicit exclusion/deferment.
- This phase creates no implementation issues.
- Repositories without Projects/custom issue types remain supported.
Size: L
Activity
feat(gh-aw): add program planning with initiatives/epics/milestones (#…
bradygaster commentedon Aug 8, 2026
E2E evidence: activation flattens the program plan and omits milestones/metadata design
Tested SHA:
47e04dc73663cba40b47f00dd8e2ac42c37f6419Consumer: https://github.com/bradygaster/squad-planning-e2e
Lifecycle root: https://github.com/bradygaster/squad-planning-e2e/issues/2
Program run: https://github.com/bradygaster/squad-planning-e2e/actions/runs/31241161935
Activation run/artifacts: https://github.com/bradygaster/squad-planning-e2e/actions/runs/31242960785
Prerequisites
The consumer had no Project V2, no custom issue types, no milestones, and only GitHub default labels. Native sub-issues are available and were successfully used.
Reproduction
Run program plan → implementation plan → validate → accept scope → accept implementation → activate on the root intent.
Expected
The program plan's 4 initiatives, 9 epics, 20 stories, and 4 outcome milestones are represented through the supported GitHub-native/fallback hierarchy, with intentional metadata.
Actual
squad,squad:*,size:*) have empty descriptions and defaultedededcolors.Graph: https://github.com/bradygaster/squad-planning-e2e/issues?q=parent-issue%3A2
Activation record: https://github.com/bradygaster/squad-planning-e2e/issues/2#issuecomment-5224864184
Impact
The accepted strategic structure disappears at activation, outcome tracking is lost, and the resulting backlog is a flat task list rather than the approved program hierarchy. Metadata is not intentional or self-describing.
fix(gh-aw): activation creates full hierarchy with milestones (#1652)
feat(gh-aw): add program planning with initiatives/epics/milestones (#…
fix(gh-aw): activation creates full hierarchy with milestones (#1652)
feat: Evolve Squad planning into executable SDLC lifecycle (github#1648…