[strategist] Milestones never created — MILESTONES.md plan still unexecuted
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
## Strategic Finding
**Type**: roadmap-gap / execution-blocker
**Horizon**: near-term
MILESTONES.md (merged via #53) defines four GitHub milestones matching the ROADMAP phases and explicitly says automation could not create them — a maintainer must. As of 2026-08-08 (sweep 6) the repo still has **zero milestones**. Consequence chain: ROADMAP checkboxes can't be tied to milestones, Phase 1 issues (#74–#77, #79, #80) can't be tagged, the KubeCon launch milestone proposed in #104 can't exist, and MILESTONES.md instructs that it "can be deleted once milestones exist" — it is currently a permanent TODO file.
**Automation blocker — now with a queued fix**: the hive GitHub App cannot create milestones (no GraphQL `createMilestone` mutation; REST writes are secondary-rate-limited). PR #130 (MERGEABLE) adds a maintainer-triggered `workflow_dispatch` workflow that creates the four milestones from MILESTONES.md — merging it converts this from a manual chore into a one-click action.
## Rationale
The planning infrastructure the project landed this week (ROADMAP, MILESTONES, GOVERNANCE, ADR-0001) only becomes operational when milestones exist — until then the roadmap is documentation, not a tracking system. With the KubeCon NA 2026 launch window opening today (#104), milestone tagging is now on the launch critical path.
## Proposed Next Step
1. Merge PR #130, then run the workflow once (Actions tab) to create the four milestones.
2. Tag the issues listed in MILESTONES.md plus #74–#77/#79/#80 to Phase 1, and add the "KubeCon NA 2026 launch" milestone from #104.
3. Trim MILESTONES.md to a pointer. Acceptance: `/milestones` shows the four phases.
---
*Filed by strategist agent (ACMM L6 — full mode); updated in place 2026-08-08 sweep 6*
Contributor guide
Research direction
Read MILESTONES.md and review PR #130, then inspect the workflow's manual dispatch entry point in the Actions tab. Confirm the workflow creates the four phase milestones, tag the listed issues and launch milestone, and leave MILESTONES.md as a pointer; done is verified when /milestones shows the four phases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, github-actions, markdown
- Domain
- devops, documentation, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 25/100