kwp-product-management-stakeholder-update

Generate audience-specific stakeholder status updates from project progress and meeting notes.

7|5|Updated May 7, 2026
One-click install
npx skills add https://github.com/14790897/MiQi --skill kwp-product-management-stakeholder-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kwp-product-management-stakeholder-update
Source: https://github.com/14790897/MiQi/tree/main/miqi/skills/kwp/product-management/stakeholder-update
Command: npx skills add https://github.com/14790897/MiQi --skill kwp-product-management-stakeholder-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the challenge of drafting consistent, high-impact status updates for diverse audiences, preventing communication gaps and ensuring strategic alignment across teams.

Core Features & Use Cases

  • Audience-Specific Templates: Automatically formats content for executives, engineering teams, cross-functional partners, or customers.
  • Status Frameworks: Integrates standard reporting frameworks like ROAM for risk management and ADRs for decision documentation.
  • Use Case: Quickly generate a concise executive summary that highlights key progress, flags a yellow-status risk with a mitigation plan, and requests a specific decision by a deadline.

Quick Start

Use the kwp-product-management-stakeholder-update skill to draft a weekly status update for the executive leadership team based on the current project progress.

Frequently Asked Questions about kwp-product-management-stakeholder-update

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

FAQPage Schema
How do I generate professional stakeholder status updates for different audiences?

To generate professional stakeholder status updates, provide project context, meeting notes, or manual input to synthesize progress, risk assessments, and decision logs into audience-specific templates for leadership, engineering, or external partners.

What is the best way to format a weekly executive summary that includes risk management and decision logs?

The best way to format a weekly executive summary is by integrating standard reporting frameworks like ROAM for risk management and ADRs for decision documentation, highlighting key progress, flagging risks, and requesting specific decisions by deadlines.

Can I use project meeting notes to automatically create audience-specific status reports?

Yes, you can use project meeting notes to create audience-specific status reports by feeding the notes as project context into the skill, which then synthesizes the information into professional reports tailored for executives, cross-functional partners, or engineering teams.

Does this stakeholder reporting tool support standard frameworks like ROAM and ADRs?

Yes, this stakeholder reporting tool supports standard frameworks by integrating ROAM for structured risk management and ADRs for decision documentation, ensuring strategic alignment and high-impact communication across diverse organizational roles.

What input is required to draft consistent cross-functional partner updates?

Drafting consistent cross-functional partner updates requires access to project context, meeting notes, or manual input to effectively populate audience-specific templates with synthesized project progress, risk assessments, and decision logs.

When do I need to use structured reporting frameworks for stakeholder communication?

You need to use structured reporting frameworks for stakeholder communication when drafting consistent, high-impact status updates for diverse audiences to prevent communication gaps and ensure strategic alignment across teams.