Agent skill
closed-loop-playbook
Governance system for routing VoC insights to owners and tracking follow-through.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/development/closed-loop-playbook-gtmagents-gtm-agents
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
- Intake – capture insight ID, driver, severity, customer(s), and evidence link.
- Routing – assign accountable owner, supporting squad, and due date.
- Action Plan – define mitigation plan, success criteria, and measurement method.
- Communication – schedule updates to customers, exec sponsors, and internal stakeholders.
- 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.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?