nwave-ai/nw-stakeholder-engagement
Demonstration preparation, audience-tailored presentations, feedback collection, and business outcome measurement. Load when preparing demos or measuring business value delivery.
npx skills add https://github.com/nWave-ai/nWave --skill nw-stakeholder-engagement
Tailor presentation content and depth to audience type:
| Audience | Focus | Style | Success Criteria |
|----------|-------|-------|-----------------|
| Executive | Business value, ROI, strategic alignment | High-level outcomes, success metrics, roadmap | Business objective achievement, ROI demonstration |
| Business | Functional capability, process improvement, UX | Feature walkthrough, workflow demo, benefit realization | Requirement satisfaction, process efficiency |
| Technical | Implementation quality, architecture, ops readiness | Technical deep-dive, architecture review, operational metrics | Technical excellence, operational readiness |
Structure as problem-solution narratives:
| Category | Metrics |
|----------|---------|
| Performance | Response time improvement | throughput gains | error rate reduction |
| Business | Revenue impact | cost reduction | user adoption rate | conversion changes |
| Operational | Deployment frequency | MTTR | support ticket reduction | availability |
User satisfaction surveys (NPS, CSAT) | Usability testing results | Stakeholder satisfaction with delivery quality | Alignment with business objectives.
Feature delivery timeline vs plan | Quality gate effectiveness (false positives/negatives) | Stakeholder satisfaction scores | Implementation quality metrics.
Successful practices to replicate | Challenges encountered and resolution strategies | Process improvements identified | Tool/technology effectiveness observations.
Update process templates and checklists | Share learnings across teams | Adjust estimation models based on actuals | Feed enhancement requests into backlog.
Take nwave-ai/nw-stakeholder-engagement from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.