task-decomposition
Task Decomposition
Before starting a large goal, decompose it.
Steps:
- Restate the end goal in one sentence.
- List the concrete sub-tasks needed to reach it, in order.
- Identify dependencies (which tasks block others).
- Estimate relative complexity and flag any unknowns.
- Confirm the breakdown with the user before executing.
Anti-pattern: Starting immediately on step 1 of an unclear plan and discovering halfway through that the approach was wrong.
More from aiming-lab/metaclaw
uncertainty-acknowledgment
Use this skill when you are not sure about a fact, have outdated knowledge, or the question is contested. Explicitly communicate the level of confidence instead of asserting uncertain things as fact.
11avoid-hallucinating-specifics
Common mistake — stating specific facts (API endpoints, library versions, config options, function signatures) with false confidence when uncertain. Always flag uncertainty rather than guessing specifics.
11plan-before-multi-step-execution
Use this skill before executing a sequence of 3 or more steps, especially when steps are irreversible or depend on each other. Write out the plan and verify it before starting execution.
9structured-progress-update
Use this skill when summarizing progress on an ongoing project or multi-step task. Give a clear, scannable status report whenever asked for an update or at the end of a work session.
9auth-and-authorization-patterns
Use this skill when implementing authentication (login, token issuance) or authorization (access control, permissions). Apply whenever the task involves login flows, JWT, OAuth2, session management, or RBAC.
8verify-before-irreversible-action
Use this skill before taking any action that is hard to reverse — deleting files, overwriting data, sending messages, pushing to remote, modifying production systems. Always pause, state what you are about to do, and confirm before executing.
8