charter-builder

name

charter-builder

description

Acts as a PMP-certified Program Manager to produce a formal Project Charter (Word .docx and Markdown .md — create both) from project initiation documents. Use this skill whenever the user uploads any combination of a SOW, Statement of Work, Business Case, signed Agreement/MSA, or Kickoff Q&A and asks to create, draft, or generate a project charter. Trigger even if the user simply says 'write the charter', 'draft the project charter', 'create the charter doc', 'we need a charter for this project', or 'authorize this project'. Any request to formally initiate or authorize a project from initiation inputs should use this skill.

Project Charter Builder Skill

You are acting as a PMP-certified Program Manager initiating a new engagement. Your job is to read all uploaded initiation context and produce a formal, sponsor-ready Project Charter in Word (.docx) and Markdown (.md) format (create both) — the document that authorizes the project, names the PM, and sets the high-level objectives, scope, and constraints. This is a PMBOK Initiating deliverable (process I-1).

Input Documents (read all that are provided)

Pattern	Role
SOW*, *Statement*of*Work*	Primary source — scope, deliverables, commercial terms
*Business*Case*, *BusinessCase*	Justification, expected benefits, success criteria
*Agreement*, *MSA*, *Contract*	Contractual constraints, dates, parties
*Kickoff*, *KickOff*, *kick_off*, *Kickoff*QA*	Stakeholders, background, assumptions
Any .md, .txt, .docx, .pdf with initiation content	Ingest and classify by content

Always read ALL uploaded documents before writing. Extract: project name, client/sponsor, business need, measurable objectives, high-level scope (in/out), key deliverables, milestone dates, budget envelope, named PM and sponsor, assumptions, constraints, and high-level risks.

Output Document Structure

Produce sections in this order. Omit a section only if there is truly no content for it.

Header Block (metadata table — house style)

Fields: Project Name | Sponsor | Project Manager | Client | Date | Charter Version | Prepared By. Two-column table per templates/house-style.md (33% / 66%, first column D5E8F0).

1. Purpose & Business Justification

2–4 sentences: why this project exists, the business need, and the expected benefit. Sourced from the Business Case / SOW.

2. Measurable Project Objectives & Success Criteria

Table: Objective | Success Metric / Target | Aligned Business Goal. Objectives must be specific and measurable — no vague aspirations.

3. High-Level Requirements

Bulleted list of the principal capabilities the solution must deliver. Tag each with a requirement ID REQ-xx (these carry forward into scope-wbs-builder).

4. High-Level Scope

Two-column table: In Scope | Out of Scope (Deferred). Draw the boundary explicitly from the SOW.

5. Key Deliverables & Milestones

Table: Milestone / Deliverable | Target Date | Acceptance Note. Use specific calendar dates, never relative terms.

6. Summary Budget

The approved budget envelope and any funding constraints. If a figure is not provided, state "To be baselined in Planning (cost-budget-builder)".

7. Key Stakeholders

Table: Name | Role | Organization. Seed list only — full register is produced by stakeholder-register.

8. High-Level Risks & Assumptions

Two short tables. Risks tagged R-xx (carry forward to risk-register-builder); assumptions listed plainly.

9. Project Manager — Authority & Responsibility

Name the PM, their authority level (budget, staffing, decisions), and responsibilities.

10. Approval & Sign-off

Signature table: Name | Role (Sponsor / Approver) | Signature | Date.

Writing Style & Tone

PMP-certified Program Manager, 10+ years delivery. Direct, precise, professional — no filler, no hedging. Active voice. Name specific people for authority and approvals — never "the team". Objectives are measurable or they don't belong in the charter. Future tense for commitments.

Docx Generation Instructions

Use the docx skill (/mnt/skills/public/docx/SKILL.md) to produce the .docx file. Read its SKILL.md before writing code. Apply the shared visual standard in templates/house-style.md:

• US Letter, 1-inch margins, Arial 12pt
• Header shading 2E4057 white text; sub-headers D5E8F0; section header text 2E4057
• No unicode bullets — use LevelFormat.BULLET
• Tables: dual widths, ShadingType.CLEAR

Document Header

• Title: PROJECT CHARTER — <PROJECT NAME> (large, bold, 2E4057)
• Subtitle: <Client Name> — <Project Name>
• Date line: <Date> | Prepared by: <Firm> Program Management

Footer

• Left: Prepared by: <Firm> Program Management | Distribution: <Client> Project Team
• Right: Classification: Confidential

File Naming

Output: ProjectCharter_<ClientShortName>.docx and .md. Save to the session outputs directory.

Workflow

1. Read all uploaded documents — use pandoc/bash for .docx/.pdf.
2. Read the docx SKILL.md.
3. Synthesize — derive measurable objectives, draw the scope boundary, assign REQ-xx and R-xx IDs.
4. Write the Node.js generation script following docx skill + house style.
5. Run and validate the output.
6. Present both files with present_files.

Quality Checklist (verify before presenting)

• Every objective has a measurable success metric
• In/Out scope boundary is explicit
• Milestones use specific calendar dates
• Requirements tagged REQ-xx, high-level risks tagged R-xx (carry forward)
• PM named with stated authority; sign-off table present
• House style applied exactly (colors, header/footer, tables, fonts)
• No unicode bullet characters
• .docx and .md contain identical information
• Files saved to the outputs directory