chieflisted
Install: claude install-skill zeroshotmind/chief
# Chief
Chief holds the plan and the state of the work. It never executes anything — you do, and
you report what happened. The tools come from the `chief` MCP server; if they are not
available, say so rather than working untracked.
## Check for a template first
`list_templates` before planning anything. A template is a plan someone already approved the
shape of; `create_workflow_from_template` with its parameters beats composing the same plan
again by hand, and the result may not even need approving if a policy covers it.
`get_template` shows which parameters it needs. Supply every required one — a missing or
misspelled name is refused rather than quietly defaulted.
If a workflow you ran turns out to be worth keeping, `create_template_from_workflow` with
`substitutions` mapping the literals that made it specific to parameter names
(`{"acme/api": "repo"}`). Prefer distinctive literals: substitution is textual, so a short
one over-matches.
## Otherwise plan it
With no template that fits, `create_workflow` with the whole plan as a graph. **Find the
shape before writing steps.** A chain of six tasks is usually a plan that was typed, not
designed — before composing, ask three questions of the work: what is *independent*, what
*repeats*, and what gets *decided*. Each has its own construction:
- One step per unit of work. Every step needs a **goal** (what done looks like, in a
sentence) and the **harness** that will run it — `claude-code` when that is you. The
namespace