Menu

Individual skill

team-charter

0upvotes

Creates a team charter covering mission, roles via RACI, decision rights, working norms, communication protocols, and a conflict protocol, built in a facilitated workshop and delivered as a fill-in template. Use when someone says "my new team needs a charter", "we keep stepping on each other's toes", "who decides what on this team", or "write our team's working agreement". Do NOT use for diagnosing dysfunction in an existing team - use team-health-check instead - or for setting the team's goals and key results - use okr-builder.

skills/team-charter/SKILL.md

Read pinned source

Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
24
Repository last updated
Oct 13, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Team Charter

A charter makes the implicit explicit. New and reorganized teams waste weeks on collisions a charter would have prevented - two people doing the same work, decisions stalling because nobody knows who owns them, norms enforced by whoever is most annoyed that day. The costly mistake this skill prevents is the manager-written charter: drafted alone, imposed top-down, ignored within a week. The document only binds people who built it.

## Inputs to collect

1. Team name, size, and whether it is new, reorganized, or existing-but-friction-y. For an existing team with unclear dysfunction, diagnose first with team-health-check - a charter papering over a trust problem fixes nothing.
2. The team's mandate as leadership states it, verbatim.
3. Known friction points: past collisions, stalled decisions, turf disputes. These become test cases for the draft.
4. Recurring decision types the team faces (prioritization, hiring, technical direction, spend).
5. Time zones and working-hours spread.

## Operating procedure