project-charterlisted
Install: claude install-skill teodstr/workbench
# Project charter
Most projects go wrong at the start, when nobody wrote down what "done" means. This skill turns a vague intention into a one-page charter that the people involved can agree on, then plans the first steps.
## When to use
- At the start of any project, at home or at work, or when a project restarts after a pause.
- When people disagree on what the project includes.
- Not for a single task that takes less than a day: just do it.
## Inputs
1. The project in a few sentences, and why it matters now.
2. Deadline, budget envelope, and the people involved.
3. Constraints: rules, contracts, dependencies, things that must not change.
## Method
1. **Write the why** in two sentences: the problem or the opportunity, and what happens if nothing is done.
2. **Turn it into a goal you can check**: specific, measurable, with a date (Doran's SMART criteria). "Move into the new flat before September 1 with the children enrolled at school", not "move soon".
3. **Draw the boundaries**: what is in scope, what is explicitly out of scope, and the deliverables.
4. **Name the decision owner**: the one person who decides when there is a disagreement, plus who must be consulted (`stakeholder-map`).
5. **Set the envelope**: deadline, budget with a contingency reserve (`project-budget`), the time each person can give.
6. **List the top three risks and the open questions** (`risk-register` goes deeper).
7. **Plan the next two weeks**: the first actions with an owner and a date, and t