| name | task-planning |
| description | Turn vague features, bug clusters, roadmap items, launch work, or playtest findings into one execution-ready planning packet by choosing the right packet type, separating discovery from delivery, and making blockers, dependencies, and the next move explicit. Use when the user needs backlog cleanup, feature slicing, sprint or milestone prep, release planning, or roadmap-to-delivery translation across developer workflow, web/fullstack, product/ops, marketing/GTM, or game work. Route sizing to `task-estimation`, issue-state governance to `triage`, plan review to `plannotator`, daily syncs to `standup-meeting`, retros to `sprint-retrospective`, and pre-planning concept framing to `bmad`, `bmad-idea`, or `bmad-gds`.
|
| allowed-tools | Bash Read Write Edit Glob Grep |
| compatibility | Best for repositories, issue lists, specs, PRDs, GDDs, launch notes, playtest feedback, or chat context that must become a compact execution packet. This is a planning and decomposition workflow, not the long-term system of record.
|
| license | MIT |
| metadata | {"tags":"task-planning, backlog-grooming, sprint-planning, milestone-planning, roadmap-slicing, feature-breakdown, launch-planning, game-development","platforms":"Claude, ChatGPT, Gemini, Codex","version":"2.1.0","source":"akillness/jeo-skills","modernization":"2026-04-12T00:00:00.000Z","hardening":"2026-04-18T00:00:00.000Z","ratchet":"2026-04-20T00:00:00.000Z"} |
Task Planning
Use this skill when the job is turning messy context into one small planning packet that a team can actually act on.
task-planning is the PM front door for backlog cleanup, feature decomposition, sprint-candidate prep, release slicing, milestone packets, and roadmap-to-delivery translation before estimation, boards, review, or execution.
Core references:
When to use this skill
- The request is too vague, too large, or too mixed to hand straight to implementation.
- A backlog needs to be cleaned into ready vs not-ready work.
- A roadmap item, feature, bug cluster, launch beat, or playtest finding needs execution slices.
- A team needs one compact packet that names dependencies, blockers, and acceptance criteria.
- The packet spans multiple disciplines: frontend/backend, PM/ops, GTM/content, or code/content/build/playtest work.
- The key question is "what should we actually do next?" rather than "how big is it?" or "what board should we use?"
When not to use this skill
- The main job is sizing, forecasting, or story-point language →
task-estimation.
- The work already exists and the real job is issue state transitions →
triage.
- The plan already exists and the real job is review/approval or diff markup →
plannotator.
- The main job is daily status coordination →
standup-meeting.
- The main job is reflection on completed work →
sprint-retrospective.
- The work is still concept framing, scope shaping, or game-production orchestration before decomposition →
bmad, bmad-idea, or bmad-gds first.
Instructions
Step 1: Choose one intake packet
Use references/intake-packets-and-route-outs.md and pick exactly one primary packet:
task_planning_packet:
