---
name: quarterly-enablement-planner
description: Build a quarterly enablement roadmap and execution calendar across launches, onboarding, coaching, and field support. Use when the user asks to plan next quarter, sequence enablement work, set a priority stack, or align initiatives to business priorities and real capacity. Route full initiative chartering to enablement-program-design and launch-specific readiness buildouts to product-launch-enablement.
---

# Quarterly Enablement Planner

Turn quarterly priorities into a realistic enablement plan with owners, milestones, and review points.

## Confirm Inputs First

Confirm:

- Quarter and planning horizon
- Business priorities and major initiatives
- Teams and roles covered
- Known launch dates and immovable events
- Capacity constraints
- Whether a current context artifact from `revenue-enablement-context` exists

If inputs are partial, ask for missing blockers or proceed with assumptions labeled by confidence.

## Read The Right Reference

Read [references/quarterly-plan-template.md](references/quarterly-plan-template.md) before building the plan.

## Default Workflow

1. Reuse current `revenue-enablement-context` if available; otherwise label context assumptions.
2. Translate business priorities into enablement outcomes and target behaviors.
3. List candidate initiatives and score them by impact, effort, and urgency.
4. Build an explicit `must do`, `should do`, and `defer` stack.
5. Sequence work around launches, peak selling periods, and manager bandwidth.
6. Assign owners, milestones, dependencies, and due dates.
7. Add reinforcement checkpoints, manager cadence, and field adoption checks.
8. Define monthly review points and re-plan triggers.
9. Produce a quarter roadmap plus a short execution brief.

## What To Avoid

- Quarter plans that exceed real capacity.
- Prioritizing visible activity over high-impact work.
- Omitting explicit defer calls, which creates hidden scope creep.
- Failing to define re-plan triggers when launches or priorities shift.

## Tool Notes

- Keep planning format tool-agnostic.
- If requested, map deliverables into the user's existing calendar, project tracker, or wiki.

## Output Contract

Default output includes:

- Quarterly enablement roadmap or calendar
- Initiative priority stack with rationale
- Defer list with rationale and re-entry conditions
- Owner and milestone matrix
- Monthly review cadence
- Risk and dependency notes

## Quality Bar

- Calendar is achievable with available capacity.
- High-impact work is prioritized ahead of low-value activity.
- Reinforcement and inspection are built into the quarter.
- Defer decisions are explicit enough to prevent hidden overcommitment.
- Plan is clear enough for cross-functional alignment.