plan-milestone

Plan dependency-ordered project milestones from issue tracker and repository context.

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/akoita/agent-toolkit --skill plan-milestone-akoita
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-milestone
Source: https://github.com/akoita/agent-toolkit/tree/main/plugins/claude/utilities/skills/plan-milestone
Command: npx skills add https://github.com/akoita/agent-toolkit --skill plan-milestone-akoita

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Planning a milestone across many open issues is error-prone: hidden dependencies, unverified prerequisites, and unbalanced scope lead to milestones that cannot actually be delivered. This Skill discovers repository guidance, roadmap context, milestone history, and issue relationships, then produces a goal-shaped, dependency-ordered milestone proposal. ## Core Features & Use Cases - Dependency graph construction: Collects declared Dependencies, Blocked by, and tracker-native relationships, resolves transitive prerequisites, detects cycles, and classifies each prerequisite into states like closed/satisfied, closed/unverified, or open-outside. - Balanced work selection: Classifies candidates across four axes — business value, usability, known issues, and new needs — and checks capacity against evidence rather than invented estimates. - Approval-gated tracker writes: Planning is read-only by default; creating milestones, assigning issues, or changing relationships requires explicit user approval, with a state refresh before any write. - Use Case: Ask the agent to plan the next sprint for a repository; it inspects open issues and their dependency links, defers blocked work, and returns a milestone proposal with execution order, exit criteria, and explicit exclusions. ## Quick Start Use the plan-milestone skill to analyze the open issues in this repository and propose the next executable milestone in dependency order.

Frequently Asked Questions about plan-milestone

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan a milestone across multiple GitHub issues?▼

Milestone planning starts by reading open issues, labels, estimates, and declared dependency links from the tracker, then building a dependency graph. Candidates are balanced across business value, usability, known issues, and new needs before proposing a dependency-ordered milestone for approval.

How are issue dependencies handled when planning a sprint?▼

Declared Dependencies, Blocked by, and Depends on links are collected from issue bodies and tracker-native relationships, then resolved transitively. An issue with an open prerequisite is admitted only if every prerequisite is also admitted earlier in the same milestone; otherwise it is deferred.

Can this skill create milestones or assign issues automatically?▼

No. Planning is read-only by default, and creating a milestone, assigning issues, or changing relationships requires explicit approval of the full proposal. After approval, the tracker state is refreshed and re-verified before any write occurs.

What happens when a closed prerequisite was only partially delivered?▼

A closed prerequisite whose closing change is described as a first slice, scaffold, or partial delivery is marked closed/unverified and treated as blocking. Full acceptance evidence, such as linked pull requests meeting the acceptance criteria, is required to count it as satisfied.

When should I not use milestone planning?▼

Do not use it for starting or finishing a single issue; it is designed for planning a milestone or sprint across multiple issues. It also defers work when dependencies are cyclic, inaccessible, or exceed the evidence-supported capacity.