project-charter

Create a PROJECT.md with problem, audience, metrics, milestones, and constraints.

1|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/AnjinMeili/Claude-ITIL-Planner --skill project-charter-anjinmeili
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-charter
Source: https://github.com/AnjinMeili/Claude-ITIL-Planner/tree/main/planitil/skills/project-charter
Command: npx skills add https://github.com/AnjinMeili/Claude-ITIL-Planner --skill project-charter-anjinmeili

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill creates a single PROJECT.md to anchor all downstream planning work, ensuring a consistent, auditable problem framing that guides scope, requirements, architecture, and release decisions.

Core Features & Use Cases

  • Produces PROJECT.md at the project root containing Problem Statement, Target Audience, Success Metrics, Timeline & Milestones, and Constraints.
  • Enforces a gate: downstream artifacts like SCOPE.md, SPEC.md, ARCH.md, and DEV-SPEC.md cannot proceed until the PROJECT.md is confirmed.
  • Provides a reusable template and workflow for initiating cross-functional projects across teams.

Quick Start

Run project-charter to create and confirm the PROJECT.md so all downstream artifacts reference a single, validated foundation.

Frequently Asked Questions about project-charter

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a project charter for a cross-functional software project?

To create a project charter, generate a PROJECT.md file capturing the problem statement, target audience, success metrics, timeline, and constraints to anchor downstream planning work.

What sections do I need in a project charter before starting scope or architecture work?

A project charter requires five sections: Problem Statement, Target Audience, Success Metrics, Timeline & Milestones, and Constraints. Downstream artifacts are gated until these are confirmed.

How do I enforce a project charter gate before writing specifications?

Enforce a project charter gate by requiring a confirmed PROJECT.md before initiating downstream artifacts like SCOPE.md, SPEC.md, ARCH.md, and DEV-SPEC.md to ensure a validated foundation.

Can I use a project charter template for initiating cross-functional IT projects?

Yes, the project charter provides a reusable template and workflow for initiating cross-functional IT projects, producing a consistent, auditable problem framing to guide release decisions.

What's the best way to anchor downstream project planning artifacts?

The best way to anchor downstream planning artifacts is producing a single PROJECT.md at the project root, ensuring scope, requirements, architecture, and release decisions reference a validated foundation.

When should I not use a project charter for software project initiation?

A project charter is not suited for projects outside the initiation stage or those lacking cross-functional complexity, as it specifically gates downstream artifacts for IT and software teams.