plan-worklisted
Install: claude install-skill mohammadhprp/teammate
# Plan work
Planning turns a request into work someone else can check. It is far cheaper to
spend a minute here than to rework a worker's wrong guess, so the aim is the
smallest plan that makes the goal, the criteria, and the team unambiguous.
Planning produces the plan; `task-ledger` records it and `delegate-task`
dispatches it. Planning never dispatches a worker itself.
## When to use
- The request should be delegated, or spans more than a trivial local edit.
- The goal is vague, consequential, or has more than one plausible reading.
- Work touches more than one project, or needs independent review.
## When not to use
- A one-line, low-risk, local change: do it directly.
- The work is already planned and the criteria are agreed: skip to
`task-ledger`, then `delegate-task`.
## Inputs
- The request, in the developer's words.
- The resolved project(s) and roots, from `multi-project-context`, prepared with
`bootstrap-project` (an `AGENTS.md` and the skills the work needs).
- `team-mate.toml` for `max_concurrent`, `max_iterations`, and `review_policy`.
## Procedure
1. **Restate the goal as an outcome.** One or two sentences describing what is
true when the work is done, not the activity taken. If you cannot state it
without hedging, the goal is ambiguous — that is the signal to ask, not to
guess.
2. **Ask before you spend agents.** Separate what blocks delegation from what a
worker can settle in scope.
- Blocking: the outcome, scope, or definition of