Generate Comprehensive Project Charters

This skill is expert in project management and business analysis, specializing in comprehensive project charters that serve as authoritative reference documents for project initiation and stakeholder alignment. Every charter it produces covers eight essential elements: project purpose and justification with a quantifiable business case, explicit in-scope/out-of-scope boundaries, measurable success criteria, a stakeholder matrix with authority levels, a high-level timeline with milestones, resource requirements, initial risk assessment, and a governance structure with decision-making and escalation paths. It structures the charter document itself - executive summary, project justification (business problem, proposed solution, financial/operational/strategic benefits), a scope statement, a success criteria table, and a stakeholder matrix - and applies the MoSCoW method (Must/Should/Could/Won't Have) for requirement prioritization to keep scope boundaries explicit.

Use this skill when initiating a project that needs real governance and authority structures, not just a scope document. It builds a RACI matrix (Responsible, Accountable, Consulted, Informed) mapping decisions like budget approval, technical design, user acceptance, and go-live to specific roles, plus explicit decision-making protocols (consensus required for major scope changes or budget increases over 10%, sponsor authority for resource allocation, PM authority for day-to-day decisions, and escalation triggers at 1+ week timeline delays or 5%+ budget variance). Its stakeholder engagement strategy insists on actual end-users (not just their managers) and validated decision-making authority, not just titles. It is not meant to be signed once and shelved - the skill treats the charter as a living document requiring formal sign-off, wide distribution, regular review, and use as an onboarding tool for new team members.

| Decision/Activity | Sponsor | PM | Tech Lead | Users | Legal |
|-------------------|---------|----|-----------|---------|
| Budget approval | A | R | C | I | I |
| Technical design | C | A | R | C | I |
| User acceptance | I | A | C | R | I |
| Go-live decision | A | R | C | C | C |

Given a project's business case, the skill produces a full charter document with the RACI governance matrix shown above, a MoSCoW-prioritized requirements list, an initial risk assessment table scoring probability times impact with mitigation strategies across technical/resource/organizational/external categories, a budget breakdown (personnel typically 80%, technology/infrastructure 15%, other expenses including 10-15% contingency at 5%), and a balanced-scorecard success framework spanning financial, customer, internal process, and learning-and-growth perspectives.

Project managers and business analysts standing up a new project that needs real authority and governance structures defined up front, not just a scope document. It suits organizations that want scope-creep prevention built in via formal change control and impact assessment, realistic commitments grounded in historical project data and explicit contingency buffers, and a charter that survives as a living reference and onboarding tool rather than a one-time sign-off artifact.