project-charter
Skill1 starsChanged 5 months agoMITView on GitHub
Draft a project or program charter for a kickoff — problem statement, goals, scope (in/out), success metrics, stakeholders, milestones, and risks. Use when the user says "write a charter", "kick off a project", "create a project brief", "we're starting a new initiative", or needs a one-page alignment doc before work begins.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- kenmulford/PMSkillstheir own version, first seen Apr 19, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- kenmulford/PMSkills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository18 other files it gives its agents.
- capacity-planningSkill
- decision-logSkill
- dependency-mappingSkill
- escalationSkill
- estimation-sizingSkill
- exec-summarySkill
- launch-readinessSkill
- okr-trackingSkill
- postmortemSkill
- prd-reviewSkill
- program-health-dashboardSkill
- raid-logSkill
- release-notesSkill
- retrospectiveSkill
- roadmap-planningSkill
- sprint-planningSkill
- stakeholder-comms-planSkill
- status-reportSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Not for: detailed requirements (use prd-review/PRD), or ongoing status (use status-report).
- Distinctive: line 18
Ask only for what's missing.
- Distinctive: line 33
Use the structure in templates/charter-template.md.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Project Charter
Produce a clear, one-page charter that gets a team and its stakeholders aligned before work starts.
When to use
- A new project, program, or workstream is starting and needs scope + alignment.
- A stalled effort needs to be (re)framed and re-aligned.
Not for: detailed requirements (use prd-review/PRD), or ongoing status (use status-report).
Inputs to gather
Ask only for what's missing; infer the rest from context and state your assumptions:
- The problem and who has it; why now.
- Desired outcome and how success will be measured.
- Known scope, constraints, deadline, and budget/headcount.
- Sponsor, lead, and key contributors.
Process
- Sharpen the problem statement to one or two sentences — the pain, not the solution.
- State 2–4 goals as outcomes, and 2–4 success metrics that are measurable (baseline → target).
- Define scope explicitly: what's in, and — just as important — what's out.
- List stakeholders with roles (sponsor, lead, contributors, informed). Use RACI if helpful.
- Lay out milestones with target dates and a clear definition of done for the project.
- Capture top risks/assumptions and any dependencies.
Output format
Use the structure in templates/charter-template.md. Keep it to one page. Mark every assumption explicitly and flag the 2–3 open questions that most need answers to proceed.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.