agentleFS
Sign inStart free
pi247pi247/classic-PM-skills/skills/documents/draft-project-charter/SKILL.md

draft-project-charter

Skill1 starsChanged 3 months agoMITView on GitHub

Draft or revise a project charter (authorization, objectives, high-level scope, success criteria). Use when starting a project, authorizing work, or the user asks for a charter.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read PROJECT_CONTEXT.md (and ORG_CONTEXT.md if present).

    line 21
  2. Very specific:

    If open assumptions block authorization, stop and run /stress-test first.

    line 22
  3. Distinctive:

    Prefer facts from context over invention.

    line 23
  4. Very specific:

    After material charter changes, offer to sync PROJECT_CONTEXT.md identity/success sections.

    line 59

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Draft project charter

Produce or revise a project charter as a portable markdown document.

Before drafting

  1. Read PROJECT_CONTEXT.md (and ORG_CONTEXT.md if present).
  2. If open assumptions block authorization, stop and run /stress-test first.
  3. Prefer facts from context over invention; mark gaps explicitly.

Template

Use assets/charter.md. Skeleton:

Charter skeleton

# Project charter - <name>

## Authorization
- Sponsor:
- Project manager authority:

## Purpose and objectives

## High-level scope
### In scope
### Out of scope

## Success criteria

## Key stakeholders (summary)

## High-level risks and constraints

## Approval
- Authorized by:
- Date:

Rules

  • Stay PM-native. Do not invent developer-pack framing.
  • Align wording with org/project shared vocabulary.
  • After material charter changes, offer to sync PROJECT_CONTEXT.md identity/success sections.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free