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:

• references/intake-packets-and-route-outs.md
• references/packet-shapes.md
• references/readiness-checklist.md
• references/planning-patterns.md

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?"