Plan milestone: $ARGUMENTS
SkillDev toolsPlan or replan an OpenRisk milestone — select ready issues, assess the load against the date, name what gets cut, and sequence the work. Use at the start of a milestone or when one starts slipping.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Plan milestone: $ARGUMENTS skill
What this skill tells your AI
The instructions your AI receives, as published by opendefender/openrisk in .claude/skills/plan-milestone/SKILL.md and read by ahel’s review.
Delegate to po-openrisk, with tech-lead consulted on sequencing and
dependencies.
Produce
- Candidate table — issue · title · estimate · dependencies · risk.
- Load versus date — total S/M/L against the due date, honestly. If it does not fit, say so in the first sentence, not the last.
- The cut — which issues leave the milestone and why. Scope is cut by removing issues, never by lowering the Definition of Done.
- Sequence — the dependency-ordered list, marking which pairs can run in
parallel under
/sprint. - The one risk most likely to blow this milestone, and the mitigation.
- Apply it —
gh issue edit <n> --milestone "$ARGUMENTS"for the keepers,--remove-milestonefor the cuts.
End with any item that needs my decision, appended to docs/DECISIONS.md.
Signals
- GitHub stars
- 33
- Forks
- 3
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
plan-milestone-opendefender- Source
- github.com/opendefender/openrisk