pm-initiating

Generates PMBOK Project Charters and Stakeholder Registers for project initiation.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/jcg-admin/IACT-ui --skill pm-initiating-jcg-admin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pm-initiating
Source: https://github.com/jcg-admin/IACT-ui/tree/main/.claude/skills/pm-initiating
Command: npx skills add https://github.com/jcg-admin/IACT-ui --skill pm-initiating-jcg-admin

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Starting a project without formal authorization leads to unclear scope, unidentified stakeholders, and no accountability. This Skill guides the PMBOK Initiating process group to produce a signed Project Charter and a complete Stakeholder Register before any planning begins. ## Core Features & Use Cases - Project Charter Development: Builds all Charter sections including business need, SMART objectives, high-level scope, risks, milestones, budget, and sponsor authorization. - Stakeholder Identification & Analysis: Creates a Stakeholder Register with Power/Interest Grid classification and engagement-level strategies. - High-Level Risk Log: Captures preliminary risks with probability, impact, and response strategies. - Use Case: A sponsor approves a new call center analytics platform. Use this Skill to draft the Charter, map stakeholders across IT and operations, and decide whether the project is ready to advance to Planning. ## Quick Start Ask the assistant to run the pm-initiating step to develop a Project Charter and Stakeholder Register for your new project.

Frequently Asked Questions about pm-initiating

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

FAQPage Schema
How do I create a Project Charter for a PMBOK project?▼

A Project Charter includes the business need, measurable SMART objectives, high-level requirements and scope, top risks, summary milestones and budget, and sponsor authorization. This Skill walks through each section and produces a complete Charter document from a template.

How do I identify and classify project stakeholders?▼

Stakeholders are identified through sponsor interviews, org chart analysis, and brainstorming, then classified on a Power/Interest Grid into four quadrants: Manage Closely, Keep Satisfied, Keep Informed, and Monitor. Each quadrant has a defined engagement strategy.

When should a project move from Initiating to Planning?▼

Advance to Planning only when the Charter is signed by the sponsor, high-power stakeholders are identified, the PM is assigned with documented authority, and top risks are logged. If the business need is unclear or the sponsor has not signed, remain in Initiating.

What are common mistakes when writing a Project Charter?▼

Common red flags include a Charter without sponsor signature, objectives without verifiable success metrics, specifying technical solutions instead of business needs, an empty risk log, and assigning the PM after Planning has started.

How accurate are budget estimates in the Project Charter?▼

Charter estimates are rough order of magnitude (ROM) with ±50% accuracy, typically using analogous or expert judgment techniques. High-precision estimates (±10%) are only possible after detailed Planning, so fixed commitments should not be made at this stage.