stakeholder-summary
From the author
Produces a plain-language stakeholder summary from an existing feature specification, for sharing with non-technical stakeholders before implementation kicks off. Use when the user wants to draft a stakeholder summary, executive summary, or business summary of a feature spec or PRD. Does not write the spec itself — use plan-a-feature. Does not sequence the build into phases — use plan-a-phased-build. Does not produce an implementation plan — use plan-implementation.
Install
npx skills add testdouble/han --skill stakeholder-summary -a claude-code
Installs to .claude/skills/stakeholder-summary/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 85
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- discover-stakeholder-summaryproduct-on-purpose/pm-skillsMaps the people and groups with a stake in a project, documenting their needs, concerns, influence, and engagement approach. Use at project kickoff, when taking over from another PM, or when resistance signals misalignment. For the update you send to those stakeholders, use foundation-stakeholder-update instead; this skill maps them, that one talks to them.Productivity★ 770
- stakeholder-updateanthropics/knowledge-work-pluginsGenerate a stakeholder update tailored to audience and cadence. Use when writing a weekly or monthly status for leadership, announcing a launch, escalating a risk or blocker, or translating the same progress into exec-brief, engineering-detail, or customer-facing versions.OfficialWriting★ 33.8K
- stakeholder-briefleeandev/stop-slop-koUse when turning dev/project material (design doc, analysis, plan, status, root-cause report, tool/skill docs) into a document for a specific audience such as executives, customer PMs, internal staff or other teams, or customer engineers. Leads document requests that name an audience, and stop-slop-ko runs last as the tone pass. Triggers include /stakeholder-brief, "고객PM/경영진용으로 정리해줘", "직원 공유용 md 만들어줘", "이해관계자 공유용 문서/브리프/소개 자료 만들어줘". Outputs HTML, DOCX, or MD.Documents★ 73
- plan-implementationtestdouble/hanBuilds a feature implementation plan from an existing feature specification (or equivalent context) through a facilitated team conversation. Use when the user wants to plan how to implement, build, deliver, or ship a feature that has already been specified. Does not specify what the feature should do — use plan-a-feature first. Does not design the contract for an interface — use design-an-api. Does not refine or stress-test an already-written plan — use iterative-plan-review. Runs its resolution rounds to completion and holds its questions until after they finish; to review each round as it lands, use pairing.Planning★ 327
- html-summarytestdouble/hanConvert a stakeholder summary markdown file into a single self-contained HTML executive report — bottom line and decision asks up front, supporting detail later — styled with a Test Double-derived palette and self-contained mermaid diagrams. Use when the user wants to turn a stakeholder summary, executive summary, or business summary into an HTML report, generate an HTML version of a summary doc, or produce a shareable HTML file from a summary markdown. Produces an HTML sibling file only; does not publish anything.Productivity★ 327
- requirement-summaryArabelaTso/Skills-4-SEGenerate concise, structured summaries of requirements for quick team understanding. Use when analyzing requirements from text documents (MD, TXT, DOCX) or technical specifications to create bullet-point summaries that highlight core functionality and dependencies/constraints. Ideal for sprint planning, stakeholder updates, team onboarding, or any situation requiring rapid comprehension of requirement documents.Planning★ 260
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in