npx claudepluginhub tractorjuice/ipad-kit --plugin ipad-kit<project ID or IPA name, e.g. '001'># IPAD Stakeholder Analysis
## User Input
## Prerequisites
> **Recommends**: An ASSESS artifact (`IPAD-{PID}-ASSESS-*.md`) in the target project. The stakeholder analysis is enriched by assessment context (understanding the IPA's maturity level helps calibrate stakeholder data needs and engagement expectations), but it is not strictly required.
## Instructions
> **Note**: The IPAD Kit Project Context hook has already detected all projects, artifacts, and external documents. Use that context below.
### Step 1: Identify Project
1. Parse `$ARGUMENTS` for a project ID (e.g., `001`) or .../stakeholdersAnalyzes stakeholder drivers, goals, and measurable outcomes for a specified project or group using templates, context, and external docs.
/stakeholdersIdentifies key stakeholders (approvers, consultants, FYI) for a change, project, or decision from a description, using searches and vetting for relevance.
/stakeholdersGenerate 01_Stakeholder_Map — influence matrix, RACI, communication plan, change readiness
$ARGUMENTS
Recommends: An ASSESS artifact (
IPAD-{PID}-ASSESS-*.md) in the target project. The stakeholder analysis is enriched by assessment context (understanding the IPA's maturity level helps calibrate stakeholder data needs and engagement expectations), but it is not strictly required.
Note: The IPAD Kit Project Context hook has already detected all projects, artifacts, and external documents. Use that context below.
$ARGUMENTS for a project ID (e.g., 001) or IPA name.IPAD-{PID}-STKE-*.md).projects/ using the next available project number.PROJECT_ID, PROJECT_NAME, and PROJECT_DIR..ipad/templates/stakeholders-template.md.${CLAUDE_PLUGIN_ROOT}/templates/stakeholders-template.md.Read the following reference data files to inform the stakeholder analysis with IPA domain knowledge:
${CLAUDE_PLUGIN_ROOT}/references/framework/investment-lifecycle/domains.md — the 5 IPAD business domains (Investment Climate, Investor Targeting, Investment Facilitation, Expansion & After-Care, Policy & Advocacy) and their associated entities. This helps map stakeholders to the data domains they interact with.${CLAUDE_PLUGIN_ROOT}/references/framework/investment-lifecycle/promotion-lifecycle.md — the end-to-end investment promotion lifecycle phases (Image Building, Investor Targeting, Investment Facilitation, Aftercare & Expansion, Policy Advocacy). This maps stakeholder engagement to lifecycle stages.${CLAUDE_PLUGIN_ROOT}/references/framework/investment-lifecycle/investment-growth-funnel.md — the funnel model (Outreach → Lead → Order → Delivery → Revenue → Loyalty) showing where stakeholders interact with the investment pipeline.${CLAUDE_PLUGIN_ROOT}/references/framework/governance/roles-and-responsibilities.md — data governance roles and responsibilities that map to stakeholder tiers.${CLAUDE_PLUGIN_ROOT}/references/framework/governance/cda-model.md — the Create-Distribute-Act governance model for data stewardship.projects/000-global/external/ and projects/{PROJECT_DIR}/external/ for reference documents.Conduct a structured stakeholder analysis across 5 tiers. For each tier, identify specific stakeholders and document their characteristics. Engage the user interactively to gather information about their specific stakeholder landscape.
Description: Senior decision-makers who set strategy, approve budgets, and are accountable for IPA performance.
Typical stakeholders:
For each stakeholder, document:
Description: External organisations that collaborate with the IPA on investment promotion, share data, or co-deliver services.
Typical stakeholders:
For each stakeholder, document: (same fields as Tier 1, plus)
Description: Special economic zones, free zones, industrial estates, and development authorities that operate within or alongside the IPA's jurisdiction.
Typical stakeholders:
For each stakeholder, document: (same fields as Tier 1, plus)
Description: Internal departments and teams within the IPA that produce, consume, and act on investment data.
Typical stakeholders:
For each stakeholder, document: (same fields as Tier 1, plus)
Description: External clients of the IPA — prospective investors, established investors, and intermediaries who interact with the IPA's services.
Typical stakeholders:
For each stakeholder, document: (same fields as Tier 1, plus)
Based on the stakeholder analysis, create a Power-Interest grid that maps all identified stakeholders:
HIGH INTEREST
│
┌───────────────────┼───────────────────┐
│ │ │
│ KEEP SATISFIED │ MANAGE CLOSELY │
│ │ │
HIGH │ • Board members │ • Minister │
POWER │ • Finance Min. │ • CEO/DG │
│ │ • Key partners │
├───────────────────┼───────────────────┤
│ │ │
│ MONITOR │ KEEP INFORMED │
│ │ │
LOW │ • Regulators │ • Internal teams │
POWER │ • Int'l orgs │ • Investors │
│ │ • Intermediaries │
└───────────────────┼───────────────────┘
│
LOW INTEREST
Populate the grid with the actual stakeholders identified in Steps 5.1-5.5.
For each quadrant of the Power-Interest grid, define the engagement strategy:
For each stakeholder, recommend a specific engagement cadence, channel, and key messages related to the IPAD framework.
Produce a RACI (Responsible, Accountable, Consulted, Informed) matrix for key IPAD framework activities:
| Activity | CEO/DG | CIO/CDO | Dept Heads | Data Owners | IT Team | Partners |
|----------|--------|---------|------------|-------------|---------|----------|
| Data Strategy | A | R | C | C | I | I |
| Data Quality | I | A | C | R | C | I |
| Analytics | I | A | R | C | R | I |
| Governance | A | R | C | R | C | I |
| Data Sharing | C | A | C | R | R | R |
| Training | I | A | R | C | C | I |
Map RACI assignments based on the stakeholders identified and the IPA's organisational structure. If an assessment exists, calibrate the RACI to the current and target maturity levels.
Create a summary table mapping each stakeholder tier to IPAD framework elements:
| Tier | Business Domains | Data Layers | Key Entities | Lifecycle Phases |
|------|-----------------|-------------|-------------|-----------------|
| T1: Leadership | D1-D5 (all) | L7-L8 | E-042, E-043 | All (strategic) |
| T2: Partners | D1, D4, D5 | L1-L2, L4 | E-001-E-009 | Phase 1, 4, 5 |
| T3: Entities | D3, D4 | L2, L4 | E-015, E-028-E-032 | Phase 3, 4 |
| T4: Teams | D1-D5 (varies) | L2-L6 | All (varies) | All (operational) |
| T5: Investors | D2, D3, D4 | L8 | E-021-E-035 | Phase 2, 3, 4 |
projects/{PROJECT_DIR}/IPAD-{PROJECT_ID}-STKE-v1.0.mdIMPORTANT — Auto-Populate Document Information Fields: When writing the output artifact, automatically populate these fields without asking the user:
IPAD-{PROJECT_ID}-STKE-v{VERSION} (e.g., IPAD-001-STKE-v1.0)1.0 for the initial stakeholder analysis, incremented for updatesDRAFTIPAD-001-ASSESS-v1.0)Generation Metadata Footer:
---
**Generated by**: IPAD Kit `/ipad-kit:stakeholders` command
**Generated on**: {DATE}
**IPAD Kit Version**: {IPAD_KIT_VERSION}
**Project**: {PROJECT_NAME} (Project {PROJECT_ID})
After writing the artifact, inform the user of recommended follow-on commands:
/ipad-kit:funnel {PROJECT_ID} — Map data requirements to the Investment Growth Funnel, informed by stakeholder needs at each tier./ipad-kit:roadmap {PROJECT_ID} — Generate an improvement roadmap that includes a stakeholder buy-in and change management strategy./ipad-kit:governance {PROJECT_ID} — Define the data governance framework with roles and responsibilities mapped to identified stakeholders./ipad-kit:assess {PROJECT_ID} — If not yet done, conduct a maturity assessment to calibrate stakeholder expectations to the IPA's current capability.