closed-loop-playbook

v2026.09.25

Governance system for routing VoC insights to owners and tracking follow-through.

GitHub
Install command
npx skhub add gtmagents/closed-loop-playbook
Markdown
SKILL.md

Closed-Loop Playbook Skill

When to Use

  • After synthesizing VoC insights that require cross-functional action.
  • During QBRs or ELT reviews to show status of customer commitments.
  • Whenever audit trails are required for compliance or customer councils.

Framework

  1. Intake – capture insight ID, driver, severity, customer(s), and evidence link.
  2. Routing – assign accountable owner, supporting squad, and due date.
  3. Action Plan – define mitigation plan, success criteria, and measurement method.
  4. Communication – schedule updates to customers, exec sponsors, and internal stakeholders.
  5. Retrospective – log outcomes, lessons, and whether additional listening is needed.

Templates

  • Action register (spreadsheet/Notion/Jira) with status automation.
  • Customer commitment digest template for AM/CS teams.
  • SLA matrix by issue severity and customer tier.

Tips

  • Integrate with ticketing/project systems to avoid duplicate tracking.
  • Highlight blockers early; exec sponsors can unblock resources fast.
  • Close the loop with customers even when timelines slip—transparency builds trust.

Discovery
Tags

No tags published for this skill.

Version
Latest version metadata

Version

v2026.09.25

Published

Sep 25, 2026

Category

Uncategorized

License

Apache-2.0

Source path

plugins/voice-of-customer/skills/closed-loop-playbook

Default branch

main

Latest commit

78e0419

Tree SHA

9016d99