Planning
Skill ulises-jeremias/agent-toolkit/skills/delivery/planning
WHAT - Planning, estimation, task breakdown, and iteration capacity fallback based on Best Practices. Use before finalizing backlog scope, story/task estimates, or iteration commitments.From its SKILL.md
npx -y skills add ulises-jeremias/agent-toolkit --skill planningAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 19 stars19 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.5 KB, as published. Nobody here has run it
Planning and Estimation (WHAT)
Use this skill when work needs planning, breakdown, estimation, or capacity validation before it becomes final backlog content.
Default guardrails
- Apply
output-handshakebefore producing any final planning artifact: ask where it should live and confirm human review. - Prefer project-specific planning rules if the repo, ticket system, or engagement pack defines them. Otherwise use this default.
- If a work item is being created or refined, pair this with
work-itemand the relevant atomic skill.
What to check
- Scope and goal are clear.
- Work is broken down into manageable items; anything estimated at 5+ points should be considered for splitting.
- Acceptance criteria and dependencies are known enough for estimation.
- Estimation technique is explicit: planning poker, T-shirt sizing, Fibonacci, or the team override.
- Capacity considers availability, holidays, meetings, focus factor, dependencies, and historical velocity.
References
references/default-template.md- default planning and capacity templatereferences/example-sprint-planning.md— example sprint planning with work item breakdown, capacity, and risk assessmentwork-item- work item hierarchy and creationclickup-cli- task updates after user approval