Initial commit
This commit is contained in:
31
skills/insight-synthesis/SKILL.md
Normal file
31
skills/insight-synthesis/SKILL.md
Normal file
@@ -0,0 +1,31 @@
|
||||
---
|
||||
name: insight-synthesis
|
||||
description: Use to convert raw customer feedback into compelling narratives, themes,
|
||||
and recommendations.
|
||||
---
|
||||
|
||||
# Insight Synthesis Framework Skill
|
||||
|
||||
## When to Use
|
||||
- Wrapping up research studies, surveys, or ongoing feedback programs.
|
||||
- Preparing executive readouts or roadmap recommendation docs.
|
||||
- Aligning cross-functional stakeholders on prioritized issues/opportunities.
|
||||
|
||||
## Framework
|
||||
1. **Signal Stacking** – layer qualitative quotes, quantitative metrics, and behavioral data for each insight.
|
||||
2. **Theme Laddering** – cluster related findings into parent themes, mapping to personas and journeys.
|
||||
3. **Impact Assessment** – estimate business impact (ARR, adoption, satisfaction, efficiency) and confidence level.
|
||||
4. **Recommendation Crafting** – outline proposed actions, owners, and success metrics.
|
||||
5. **Storytelling** – build narrative arcs with hooks, evidence, and clear calls to action.
|
||||
|
||||
## Templates
|
||||
- Insight card (context, signal evidence, impact, recommendation).
|
||||
- Executive summary outline with top themes and action table.
|
||||
- Appendix structure for quotes, charts, and methodology notes.
|
||||
|
||||
## Tips
|
||||
- Keep verbatim quotes close to stats to reinforce credibility.
|
||||
- Use visual cues (heatmaps, journey overlays) to help audiences grasp patterns quickly.
|
||||
- Pair with `stakeholder-ops` to ensure follow-up actions are logged and tracked.
|
||||
|
||||
---
|
||||
31
skills/stakeholder-ops/SKILL.md
Normal file
31
skills/stakeholder-ops/SKILL.md
Normal file
@@ -0,0 +1,31 @@
|
||||
---
|
||||
name: stakeholder-ops
|
||||
description: Use to coordinate approvals, communications, and accountability across
|
||||
teams for feedback programs.
|
||||
---
|
||||
|
||||
# Stakeholder Operations Guide Skill
|
||||
|
||||
## When to Use
|
||||
- Launching surveys, betas, or listening tours that require multi-team approvals.
|
||||
- Routing insights to product, CS, marketing, and exec stakeholders with clear accountability.
|
||||
- Ensuring follow-up communications and governance rituals stay on track.
|
||||
|
||||
## Framework
|
||||
1. **Stakeholder Map** – list involved teams, decision rights, and expectations per stage.
|
||||
2. **Approval Workflow** – define checkpoints (brief sign-off, launch approval, readout review) with timelines.
|
||||
3. **Communication Plan** – specify audiences, channels, frequency, and owners for updates.
|
||||
4. **Action Tracking** – set up shared trackers with status, blockers, and success metrics.
|
||||
5. **Governance Rituals** – outline cadences (weekly syncs, monthly reviews) plus escalation paths.
|
||||
|
||||
## Templates
|
||||
- RACI chart for research + activation workflows.
|
||||
- Approval checklist with required artifacts (brief, QA results, comms plan).
|
||||
- Meeting agenda + notes template to keep stakeholders aligned.
|
||||
|
||||
## Tips
|
||||
- Keep stakeholder rosters fresh; note backups for vacations or org changes.
|
||||
- Automate reminders linked to due dates via project/workflow tools.
|
||||
- Pair with `insight-synthesis` outputs to ensure narrative consistency.
|
||||
|
||||
---
|
||||
31
skills/survey-design/SKILL.md
Normal file
31
skills/survey-design/SKILL.md
Normal file
@@ -0,0 +1,31 @@
|
||||
---
|
||||
name: survey-design
|
||||
description: Use to craft rigorous survey instruments with sampling, question logic,
|
||||
and QA standards.
|
||||
---
|
||||
|
||||
# Customer Survey Design Kit Skill
|
||||
|
||||
## When to Use
|
||||
- Launching new surveys or refreshing existing templates.
|
||||
- Diagnosing low response quality or bias in ongoing programs.
|
||||
- Training GTM teams on survey best practices.
|
||||
|
||||
## Framework
|
||||
1. **Objective Clarity** – define single-topic goals, hypotheses, and decision criteria.
|
||||
2. **Audience & Sampling** – specify personas, quotas, suppression rules, and incentive plan.
|
||||
3. **Question Architecture** – balance quant vs qual questions, avoid double-barreled prompts, include screener + validation items.
|
||||
4. **Logic & Branching** – outline conditional flows, progress indicators, and completion time targets.
|
||||
5. **QA Checklist** – test across devices, languages, anonymity rules, and data export formats.
|
||||
|
||||
## Templates
|
||||
- Survey brief (goal, audience, sample, success metrics).
|
||||
- Question bank categorized by objective (adoption, satisfaction, pricing, roadmap).
|
||||
- QA script for reviewers to confirm copy, logic, and translations.
|
||||
|
||||
## Tips
|
||||
- Cap surveys at <10 minutes unless offering significant incentives.
|
||||
- Randomize answer choices when appropriate to reduce bias.
|
||||
- Pair with `stakeholder-ops` to align approvals and launch windows.
|
||||
|
||||
---
|
||||
Reference in New Issue
Block a user