skills.rest
amirbiron
amirbironCOMMUNITY
Explore all skills by this author →
GitHub

stakeholder-summary

Generates plain-language stakeholder summaries from feature specifications for non-technical audiences.

Updated Sep 1, 2026
Search Tags:#product management#executive summary#feature specification#mermaid diagrams#prd#plain language#stakeholder summary
One-click install
npx skills add https://github.com/amirbiron/Han --skill stakeholder-summary-amirbiron
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: stakeholder-summary
Source: https://github.com/amirbiron/Han/tree/main/han-reporting/skills/stakeholder-summary
Command: npx skills add https://github.com/amirbiron/Han --skill stakeholder-summary-amirbiron

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Feature specifications and PRDs are written for engineers, leaving product managers without a shareable document for non-technical stakeholders who need to review scope and trade-offs before implementation begins. ## Core Features & Use Cases - Plain-Language Translation: Converts technical spec content (APIs, schemas, system names) into customer-facing vocabulary with no engineering artifacts. - Structured Summary Document: Produces a stakeholder-summary.md with problem framing, capabilities, outcomes, Mermaid UX and data-flow diagrams, out-of-scope items, and open questions. - Multi-Pass Quality Review: Runs contradiction, readability, and reading-order self-checks against the source spec before presenting the result. - Use Case: After finalizing a feature-specification.md for a new customer-claim flow, generate a summary to send to leadership and support leads for sign-off before kickoff. ## Quick Start Ask the assistant to create a stakeholder summary from your feature specification file, optionally noting the audience or emphasis.

Frequently Asked Questions about stakeholder-summary

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

FAQPage Schema
How do I create a stakeholder summary from a feature specification?▼

Provide the path to your feature-specification.md (or PRD) and the skill writes a stakeholder-summary.md in the same directory. It translates technical details into plain language and includes diagrams, exclusions, and open questions.

What is the difference between a stakeholder summary and a feature spec?▼

A feature spec is written for engineers with implementation detail; a stakeholder summary removes file paths, APIs, and schemas, framing the problem, capabilities, and trade-offs in customer language for non-technical review before kickoff.

Does the stakeholder summary include diagrams?▼

Yes. It generates Mermaid flowcharts for the user experience and for today-vs-after data flows, with one diagram per meaningfully distinct path in the spec. Diagram counts follow the spec, not a fixed template.

Can it write the feature specification itself?▼

No. It only summarizes an existing spec, PRD, or design doc. Writing the spec belongs to a separate planning skill, as does phased build sequencing or implementation planning.

What happens if stakeholder-summary.md already exists?▼

The skill asks whether to overwrite, append a timestamp suffix, or stop. It never silently overwrites an existing summary file.

Related Skills

Explore More Product & Management Skills→
GeneralJerelGeneralJerel
6

create-prd

Draft structured PRDs from problem statements for product teams.

Community
Advanced
docs-plusdocs-plus
88

grill-me

Question project plan decision branches and provide recommended answers.

Official
Intermediate
elasticelastic
71

docs-flag-jargon-skill

Flag internal jargon and abbreviations in documentation files with plain-language replacements.

Official
Intermediate
ihmorolihmorol
1

explain

Explain code, architecture, and technical concepts with analogies and Mermaid diagrams.

Community
Intermediate