Triggers on "project charter", "project initiation", "acta de constitucion", "kickoff document". Generates formal project initiation documents with business case, scope, stakeholders, milestones, budget, risks, and success criteria. Output: branded HTML charter or markdown. [EXPLICIT]
From jm-adknpx claudepluginhub javimontano/jm-adk-alfaThis skill is limited to using the following tools:
TL;DR — Produces a complete, stakeholder-ready project charter that formalizes scope, authority, budget, and success criteria into a single source of truth for project initiation.
Invoke this skill when any of these conditions are met:
| Signal | Examples |
|---|---|
| Explicit request | "Create a project charter for X", "Draft an acta de constitucion" |
| Kickoff preparation | "We need a kickoff document before the steering committee meets" |
| Scope formalization | "Let's document what's in and out of scope for this initiative" |
| Governance need | "The PMO requires a formal initiation artifact before we allocate budget" |
Do not activate for lightweight task tracking, sprint planning, or informal project briefs that lack budget and governance dimensions.
Before drafting, extract or request the following baseline information:
If the user provides fewer than three of these dimensions, enter clarification mode and ask targeted questions before proceeding.
The generated charter follows this canonical structure:
[OPEN].Generated by project-charter skill | {date} | v1.0.After the first draft:
[OPEN] or [INFERRED] and prompt the user for confirmation../output/project-charter-{slug}-{date}.md.| Dimension | Priority | Rationale |
|---|---|---|
| Completeness | HIGH | A charter with missing sections loses governance credibility |
| Brevity | MEDIUM | Executives skim; keep each section concise but sufficient |
| Visual polish | MEDIUM | HTML mode elevates perceived quality for steering committees |
| Speed | LOW | Thoroughness matters more than turnaround for initiation docs |
risk-assessment skill. [EXPLICIT]Good output (excerpt):
### 3. Objectives
1. Reduce customer onboarding time from 14 days to 5 days by Q3 2026. [EXPLICIT]
2. Achieve 90% self-service completion rate for Tier-1 accounts. [EXPLICIT]
3. Integrate with Salesforce CRM by milestone M3. [EXPLICIT]
### 4. Scope
**In scope:**
1. Redesign of onboarding wizard (web + mobile)
2. API integration with Salesforce and HubSpot
3. Automated welcome-email sequence
**Out of scope:**
1. Legacy system decommissioning (Phase 2)
2. Billing module changes
Bad output (excerpt):
### Objectives
- Make onboarding better
- CRM stuff
- Emails
### Scope
We will do the onboarding project and related things.
The good example uses SMART objectives, evidence tags, and explicit in/out scope. The bad example is vague, unmeasurable, and lacks boundary definition.
Before delivering the charter, confirm every item:
name, description, model, context, allowed-tools with no angle brackets[OPEN] tag[INFERRED] or [OPEN]| File | Purpose |
|---|---|
references/charter-template.md | Canonical charter markdown template |
references/body-of-knowledge.md | PMI/PRINCE2 charter standards and best practices |
references/html-template.html | Branded HTML output template with JM Labs design tokens |
evals/evals.json | Evaluation scenarios for charter completeness and quality |
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.