Nw stakeholder engagement
Skill nWave-ai/nWave/plugins/nw/skills/nw-stakeholder-engagement
Demonstration preparation, audience-tailored presentations, feedback collection, and business outcome measurement. Load when preparing demos or measuring business value delivery.From its SKILL.md
npx -y skills add nWave-ai/nWave --skill nw-stakeholder-engagementAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
3.8 KB, 661 tokens by cl100k_base, as published. Nobody here has run it
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:
- Before state: current pain point with quantitative evidence
- Feature walkthrough: end-to-end workflow with realistic data
- After state: measurable improvement with before/after comparison
- 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
- Real-time feedback during demonstration (capture questions and concerns)
- Post-demonstration survey with structured questions
- 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
- Categorize feedback items
- Prioritize by business impact
- Assign ownership for each action item
- Communicate response plan with timelines
- Track resolution to completion
Business Outcome Measurement
Quantitative Metrics
| Category | Metrics |
|---|---|
| Performance | Response time improvement |
| Business | Revenue impact |
| Operational | Deployment frequency |
Qualitative Assessments
User satisfaction surveys (NPS, CSAT) | Usability testing results | Stakeholder satisfaction with delivery quality | Alignment with business objectives.
Success Validation Process
- Baseline: collect pre-implementation measurements
- Monitor: track metrics post-deployment (minimum 2 weeks)
- Validate: compare against success thresholds with statistical rigor
- Report: present results framed in business value terms
- 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.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most operations skills give in 661 tokens
Counted across 483 of the 484 authors here whose files we hold, read 2026-08-07
- Collect monitoring data throughout the simulationin 14 of 483, across 6 files
- Set the random seed for reproducibilityin 14 of 483, across 6 files
- Validate simulations against analytical solutionsin 12 of 483, across 4 files
- Clarify goals, constraints, and inputsin 11 of 483, across 2 files
- Implement contract tests for integration pointsin 11 of 483, across 2 files
- Implement strangler fig infrastructure with API gatewayin 11 of 483, across 2 files
- Audit modernized components for security vulnerabilitiesin 11 of 483, across 2 files
- Avoid Python blocking calls in processesin 10 of 483, across 3 files
- Use resource context managers for automatic cleanupin 9 of 483, across 2 files
- Maintain consistent time unitsin 9 of 483, across 2 files
- Validate outcomes against success criteriain 8 of 483, across 1 file
- Analyze the legacy codebase for technical debtin 8 of 483, across 1 file
Said here and by no other author read
- Tailor presentation content to audience type
- Structure demonstrations as problem-solution narratives
- Set up demo environments with realistic data
- Prepare backup plans for demo failures
- Collect real-time feedback during demonstrations
- Categorize feedback items
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.