/nw-stakeholder-engagement
Demonstration preparation, audience-tailored presentations, feedback collection, and business outcome measurement. Load when preparing demos or measuring business value delivery.
Claude Code
$ npx -y skills add nWave-ai/nWave --skill nw-stakeholder-engagement --agent claude-code
Codex
$ npx skills add nWave-ai/nWave --skill nw-stakeholder-engagement -a codex -y
Cursor
$ npx skills add nWave-ai/nWave --skill nw-stakeholder-engagement -a cursor -y
Gemini CLI
$ npx skills add nWave-ai/nWave --skill nw-stakeholder-engagement -a gemini-cli -y
GitHub Copilot
$ npx skills add nWave-ai/nWave --skill nw-stakeholder-engagement -a github-copilot -y
OpenCode
$ npx skills add nWave-ai/nWave --skill nw-stakeholder-engagement -a opencode -y
Windsurf
$ npx skills add nWave-ai/nWave --skill nw-stakeholder-engagement -a windsurf -y
SKILL.md
nw-stakeholder-engagement.SKILL.mdname: nw-stakeholder-engagement
description: Demonstration preparation, audience-tailored presentations, feedback collection, and business outcome measurement. Load when preparing demos or measuring business value delivery.
user-invocable: false
disable-model-invocation: true
Stakeholder Engagement
Demonstration Preparation
Audience Analysis
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 |
Demonstration Script Development
Structure as problem-solution narratives: 1. **Before state**: current pain point with quantitative evidence 2. **Feature walkthrough**: end-to-end workflow with realistic data 3. **After state**: measurable improvement with before/after comparison 4. **Business impact**: translate technical metrics to business outcomes
Preparation Checklist
- [ ] Demo environment set up with realistic data
- [ ] Backup plan for demo failures (screenshots, recorded fallback)
- [ ] Stakeholder briefing sent with agenda and expectations
- [ ] Interactive participation points identified
- [ ] Time budget allocated per section
Feedback Collection
Structured Feedback Process
1. Real-time feedback during demonstration (capture questions and concerns) 2. Post-demonstration survey with structured questions 3. Follow-up interviews for deeper insights (optional, for major features)
Feedback Categories
- **Functional**: does the feature meet requirements?
- **Usability**: is the user experience intuitive?
- **Performance**: does speed/responsiveness meet expectations?
- **Priority**: what enhancements should come next?
Feedback Action Workflow
1. Categorize feedback items 2. Prioritize by business impact 3. Assign ownership for each action item 4. Communicate response plan with timelines 5. Track resolution to completion
Business Outcome Measurement
Quantitative Metrics
| 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 |
Qualitative Assessments
User satisfaction surveys (NPS, CSAT) | Usability testing results | Stakeholder satisfaction with delivery quality | Alignment with business objectives.
Success Validation Process
1. **Baseline**: collect pre-implementation measurements 2. **Monitor**: track metrics post-deployment (minimum 2 weeks) 3. **Validate**: compare against success thresholds with statistical rigor 4. **Report**: present results framed in business value terms 5. **Iterate**: identify continuous improvement opportunities
Retrospective and Lessons Learned
Delivery Effectiveness Assessment
Feature delivery timeline vs plan | Quality gate effectiveness (false positives/negatives) | Stakeholder satisfaction scores | Implementation quality metrics.
Knowledge Capture
Successful practices to replicate | Challenges encountered and resolution strategies | Process improvements identified | Tool/technology effectiveness observations.
Integration into Future Iterations
Update process templates and checklists | Share learnings across teams | Adjust estimation models based on actuals | Feed enhancement requests into backlog.
Read more
name: nw-stakeholder-engagement description: Demonstration preparation, audience-tailored presentations, feedback collection, and business outcome measurement. Load when preparing demos or measuring business value delivery. user-invocable: false disable-model-invocation: true
Stakeholder Engagement
Demonstration Preparation
Audience Analysis
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 |
Demonstration Script Development
Structure as problem-solution narratives: 1. **Before state**: current pain point with quantitative evidence 2. **Feature walkthrough**: end-to-end workflow with realistic data 3. **After state**: measurable improvement with before/after comparison 4. **Business impact**: translate technical metrics to business outcomes
Preparation Checklist
- [ ] Demo environment set up with realistic data
- [ ] Backup plan for demo failures (screenshots, recorded fallback)
- [ ] Stakeholder briefing sent with agenda and expectations
- [ ] Interactive participation points identified
- [ ] Time budget allocated per section
Feedback Collection
Structured Feedback Process
1. Real-time feedback during demonstration (capture questions and concerns) 2. Post-demonstration survey with structured questions 3. Follow-up interviews for deeper insights (optional, for major features)
Feedback Categories
- **Functional**: does the feature meet requirements?
- **Usability**: is the user experience intuitive?
- **Performance**: does speed/responsiveness meet expectations?
- **Priority**: what enhancements should come next?
Feedback Action Workflow
1. Categorize feedback items 2. Prioritize by business impact 3. Assign ownership for each action item 4. Communicate response plan with timelines 5. Track resolution to completion
Business Outcome Measurement
Quantitative Metrics
| 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 |
Qualitative Assessments
User satisfaction surveys (NPS, CSAT) | Usability testing results | Stakeholder satisfaction with delivery quality | Alignment with business objectives.
Success Validation Process
1. **Baseline**: collect pre-implementation measurements 2. **Monitor**: track metrics post-deployment (minimum 2 weeks) 3. **Validate**: compare against success thresholds with statistical rigor 4. **Report**: present results framed in business value terms 5. **Iterate**: identify continuous improvement opportunities
Retrospective and Lessons Learned
Delivery Effectiveness Assessment
Feature delivery timeline vs plan | Quality gate effectiveness (false positives/negatives) | Stakeholder satisfaction scores | Implementation quality metrics.
Knowledge Capture
Successful practices to replicate | Challenges encountered and resolution strategies | Process improvements identified | Tool/technology effectiveness observations.
Integration into Future Iterations
Update process templates and checklists | Share learnings across teams | Adjust estimation models based on actuals | Feed enhancement requests into backlog.
AI agents that guide you from idea to working code, with human judgment at every gate. nWave runs inside Claude Code. It breaks feature delivery into seven waves (discover, diverge, discuss, design, devops, distill, deliver).
Other skills on nwave.
More skills from other plugins.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
ask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
Questions about nw-stakeholder-engagement.
- Which coding agents can use nw-stakeholder-engagement?
- nw-stakeholder-engagement installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.

