# Library Context

### Job this is for

Audit, refresh, review, reinforce, and measure one sales playbook or enablement workflow with clear owners, source-backed claims, manager coaching, role-play practice, and adoption feedback.

### When to use it

- a sales playbook is stale or ownerless
- enablement content has unsupported claims
- sellers need role-play scenarios from approved guidance
- managers need coaching reinforcement materials
- enablement needs adoption feedback without overstating revenue impact

### Inputs needed

- current playbook or section with private details removed
- target audience and sales motion
- last refresh date and owner
- approved product, methodology, and competitive sources
- known objections or scenarios with customer details removed
- adoption signals and manager feedback at aggregate level

### Expected output

- playbook inventory and freshness audit
- claim and source map
- role-play scenario set
- manager coaching reinforcement plan
- adoption feedback loop
- enablement-platform-safe summary

### What good looks like

- stale and unsupported claims are visible
- every field-ready claim maps to an approved source or review owner
- role-play uses synthetic or sanitized scenarios
- manager coaching material is reviewable and not rep-specific by default
- adoption metrics are separated from revenue impact claims

### Operating steps

1. Collect only the minimum inputs needed for the playbook refresh.
2. Remove customer, prospect, rep, deal, pricing, and partner identifiers before using AI.
3. Run the relevant skill from the skill library.
4. Review the output against the manager QA checklist.
5. Route flagged items to enablement, sales leadership, product marketing, product, legal, or frontline managers before field use.
6. Save only approved final assets and a safe system-of-record summary.

### Operator run sheet

| Step | Owner                                         | Action                                               | Required input              | Data class | Approved tool path   | Approval gate             | System of record           | Done when                                         |
| ---- | --------------------------------------------- | ---------------------------------------------------- | --------------------------- | ---------- | -------------------- | ------------------------- | -------------------------- | ------------------------------------------------- |
| 1    | Enablement                                    | Audit playbook freshness and source support          | redacted playbook           | internal   | approved GTM AI tool | self-check                | enablement workspace       | stale sections and unsupported claims are visible |
| 2    | Enablement Manager or Sales Leader            | Review refreshed guidance and coaching reinforcement | draft assets and source map | internal   | document review only | required before field use | LMS or enablement platform | field-ready guidance is approved by owner         |
| 3    | Product Marketing, Product, Legal, or Manager | Review triggered claims or rep-specific coaching     | flagged items only          | restricted | review channel       | required when triggered   | approval record            | approval or blocked reason is recorded            |

This run sheet is the part a manager can operationalize. If a team cannot identify the owner, data class, approval gate, and system of record for a run, the workflow is not ready for field use.