delegation-brieflisted
Install: claude install-skill teodstr/workbench
# Delegation brief
Most delegation fails at the brief: the person knows what to do but not why, so they cannot adapt when reality differs from the plan. This skill writes the intent first, a lesson the Heath brothers draw from the military "commander's intent".
## When to use
- Before handing a task to someone else, inside or outside the project team.
- When a task keeps coming back unfinished or wrong.
- Not to split a whole project: use `responsibility-matrix`.
## Inputs
1. The task, and why it matters for the project.
2. The person: their experience with this kind of task and their availability.
3. Constraints: budget, deadline, rules, things that must not change.
## Method
1. **Write the intent** in one or two sentences: the purpose of the task and what success means for the project. If the plan breaks, the person follows the intent.
2. **Describe the result**, not the steps: what "done" looks like, with an example or a model when possible, and how it will be checked.
3. **State the constraints and resources**: deadline, budget, tools, access, people to ask, and what must not happen.
4. **Set the decision rights**: what the person decides alone, what they must ask about first, and the spending limit.
5. **Adapt the level of detail** to experience: more steps and earlier check-ins for a first time, more freedom for an expert.
6. **Plan the check-ins**: the first one early (to catch misunderstandings), then at milestones, and the format of the report.
7. **Ask the pe