Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Program Charter

ASecurity

Turn a fuzzy cross-team mandate into a chartered program — a measurable outcome, a named sponsor, explicit in/out-of-scope boundaries, the teams on the hook, and the starting RAID. Use at the very start, before any planning, whenever a multi-team effort lacks a clear outcome or owner.

7 stars
0 votes
0 copies
1 views
Added 9/23/2026
ai-agentsgo

Security Analysis

A100/100

Scanned 9/23/2026

$npx -y skills add mcorbett51090/RavenClaude --skill program-charter --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Program Charter?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Program Charter
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mcorbett51090-program-charter/badge)](https://www.skillsdirectory.com/skills/mcorbett51090-program-charter)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: program-charter
description: "Turn a fuzzy cross-team mandate into a chartered program — a measurable outcome, a named sponsor, explicit in/out-of-scope boundaries, the teams on the hook, and the starting RAID. Use at the very start, before any planning, whenever a multi-team effort lacks a clear outcome or owner."
---

# Skill: Program charter

Charter a program before planning it. A program without a measurable outcome and a
named sponsor is a request, not a program — and it cannot be declared done.

## When to use

- A multi-team effort has been handed down but the outcome is fuzzy.
- Several teams share a deadline but no one owns the joint result.
- A program is in flight but nobody can state, in one sentence, what "done" means.

First confirm this is actually a program (tree 1 in
[`../../knowledge/tpm-engagement-decision-trees.md`](../../knowledge/tpm-engagement-decision-trees.md)).
If the hard part isn't cross-team seams, route to `project-management`.

## Procedure

1. **Write the outcome as one measurable sentence.** Metric + target + date. If you
   can't measure it, you can't close it. Push back on "improve X" until it's
   "move metric M from A to B by date D."
2. **Name the single sponsor.** One accountable executive who funds tradeoffs and
   breaks ties. Two sponsors is zero sponsors.
3. **Draw the scope boundary — out-of-scope first.** The out list is what protects
   the date; make it explicit and get the sponsor to agree it.
4. **List the teams and each team's one deliverable** into the program.
5. **Seed the RAID** with the known risks, assumptions, issues, and the obvious
   cross-team dependencies.
6. **Fill the [`program-charter`](../../templates/program-charter.md) template** and
   get the sponsor's explicit sign-off before any planning starts.

## Output

A completed charter. The outcome sentence is the contract; everything downstream
(plan, RAID, status, go/no-go) is judged against it.

## Anti-patterns (the hook flags these in artifacts)

- A charter with no measurable outcome ("improve billing").
- A charter with no named sponsor, or two co-sponsors.
- A scope section with an in-list but no out-list.

Attribution

mcorbett51090mcorbett51090
View sourceSee grades on GitHubMore from mcorbett51090 →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →