review-team-charter

Review Team Charter

Audits a team charter and reports findings across eight categories: purpose and vision, stakeholders, responsibilities and boundaries, roles, operating norms, decision-making, success metrics, and ratifiability.

A charter fails in two ways: it is too vague to guide decisions, or it contradicts a neighboring charter and reopens a boundary dispute. This review checks both.

Prerequisites

• A charter file, default teams/<team-slug>/charter.md, or a charter provided in context or as a file path
• The parent organization's mission and values, when available (for alignment checks)
• Adjacent team charters, when available (for boundary-overlap checks)

Steps

1. Read the charter from teams/<team-slug>/charter.md if present, otherwise from context or as a file path.
2. Read adjacent charters and the org mission when available.
3. Identify issues in each category below.
4. Report findings using the output format. Omit any category with no findings.
5. Write the findings to teams/<team-slug>/review-charter.md with frontmatter artifact: team-charter, verdict (approved if there are no blocking findings, changes-requested if the author must address findings, rejected for a fundamental flaw), and reviewed_at: <ISO date>, and the findings as the body. Record any unresolved open questions in the findings body.
6. On approved, also update the charter's frontmatter: set status: approved and last_reviewed: <ISO date>.

Review Checklist

Purpose and Vision

• Does the Purpose name an outcome the team owns, rather than a list of activities?
• Is the Purpose one or two sentences, or does it grow too long?
• Is the Vision a specific future state for the current horizon, not a generic aspiration?

Stakeholders

• Are customers and stakeholders named concretely, not as "the company" or "internal stakeholders"?
• Does each named group have what it needs from the team stated?
• Is any obvious consumer of the team's output missing?