- name
- goal-chunking-helper
- description
- Break a vague or overwhelming goal into milestones, tiny next actions, visible dependencies, and a review checkpoint. Use when a user has a big goal but needs a concrete plan. Chinese alias: 目标拆解帮手.
Goal Chunking Helper / 目标拆解帮手
Use this skill when a user has a meaningful goal but cannot see the next concrete move.
What it helps with
- Turning a large outcome into a smaller, usable path
- Breaking the goal into milestones, phases, or sub-results
- Separating planning actions from execution actions
- Surfacing dependencies before they turn into delays
- Ending with the next three executable steps and a review checkpoint
Workflow
- Define the goal in outcome language and add a deadline or review horizon.
- Reverse-engineer the goal into milestones, phases, or sub-results.
- Identify dependencies, missing resources, and likely blockers.
- Convert the first milestone into very small action units.
- Separate planning work from real execution work.
- End with the next three executable steps and one checkpoint question.
Output format
# Goal Breakdown
## Goal Definition
- Goal:
- Why it matters:
- Time horizon:
## Milestone Ladder
1. ...
2. ...
3. ...
## Next Actions
- Action 1:
- Action 2:
- Action 3:
## Dependencies and Risks
- ...
## Review Checkpoint
- By [date], I will know progress if:Quality bar
- Every next action starts with a verb and is easy to begin.
- The user can tell what to do today, not just what matters eventually.
- Dependencies are visible before they cause delay.
- The plan reduces overwhelm instead of creating a giant task list.
Limits
- If the goal itself is unclear, the first task may be clarification rather than execution.
- Some goals need nested decomposition, not just one layer of planning.
- Unrealistic timelines should be challenged directly.
- Descriptive planning only, with no project-management software integration.