skills/week-planner/SKILL.md
Structures the CSM's week based on their portfolio status, upcoming events, overdue items, and strategic priorities. Produces a time-blocked plan that balances reactive demands with proactive account management. Use when asked to plan a week, structure daily priorities, build a weekly schedule, allocate time across accounts, manage a busy week, or when a CSM feels overwhelmed and needs to determine where to focus. Also triggers for questions about time management, weekly planning, account prioritisation for the week, daily priority setting, or how to balance competing demands across a portfolio.
npx skillsauth add stephenrogan/csm-skills week-plannerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Structures your week by pulling together everything that needs your attention -- meetings, overdue items, risk accounts, proactive outreach, and administrative tasks -- and allocating time based on impact, not urgency.
The fundamental problem this skill solves: urgent things are visible. Important things are not. Without a plan, every week is consumed by what is loudest, not what matters most. The week planner makes the important things visible.
Provide:
Sort all items into four buckets:
| Bucket | Definition | Time Allocation | Examples | |--------|-----------|----------------|---------| | Protect | Activities that prevent revenue loss or relationship damage | 40% of available time | At-risk accounts, escalations, renewal prep, overdue commitments | | Grow | Activities that create new value or revenue | 25% of available time | Expansion conversations, adoption planning, QBR prep, success plan reviews | | Maintain | Activities that sustain healthy relationships | 20% of available time | Scheduled check-ins, routine touchpoints, CRM updates | | Build | Activities that invest in your long-term effectiveness | 15% of available time | Account strategy, multi-threading, internal development, process improvement |
The 40/25/20/15 split is a guideline, not a rule. A week with 3 at-risk accounts and an active escalation shifts to 60% Protect. A week with no fires shifts to 30% Protect and more Grow and Build. Adjust based on reality -- but if Protect is consistently >50%, your portfolio has a structural problem, not a time management problem.
These happen regardless of what else is on the list:
List them, estimate time, and subtract from your available hours. What remains is your discretionary time.
For everything that is not a non-negotiable, rank by impact:
Impact scoring (quick assessment):
Assign items to specific days and time blocks:
| Day | Focus | Why This Day | |-----|-------|-------------| | Monday | Protect + Plan | Start the week by addressing the most urgent items and reviewing the plan | | Tuesday-Wednesday | Grow + Maintain | Mid-week has the most energy and the fewest interruptions. Use it for high-value work | | Thursday | Maintain + Build | Customer check-ins, relationship maintenance, and investment in your own development | | Friday | Build + Admin | Process improvement, CRM cleanup, next-week planning, reflection |
Time-blocking rules:
At the end of each day, take 5 minutes:
## Weekly Plan: [CSM Name]
**Week of:** [Date]
**Available hours:** [X] (after scheduled meetings)
### Non-Negotiables This Week
| Item | Day | Time | Bucket |
|------|-----|------|--------|
| Acme Corp renewal call | Tue | 1hr | Protect |
| Beta Inc escalation follow-up | Mon | 30min | Protect |
| Commitment: send API docs to Gamma Corp | Mon | 30min | Protect |
| QBR prep for Delta Corp (QBR Thursday) | Tue-Wed | 2hr | Grow |
| Manager 1:1 | Wed | 30min | Internal |
### Discretionary Priority List
| Priority | Item | Bucket | Est. Time | Scheduled |
|----------|------|--------|----------|-----------|
| 1 | Competitive response plan for Acme Corp | Protect | 1hr | Mon PM |
| 2 | Expansion proposal draft for Echo Corp | Grow | 1.5hr | Tue PM |
| 3 | Check-in calls: 4 mid-market accounts | Maintain | 2hr | Thu AM |
| 4 | Account strategy draft for top 3 accounts | Build | 2hr | Fri AM |
| 5 | Multi-threading outreach for Beta Inc | Build | 30min | Fri PM |
### Daily Breakdown
**Monday:** [Scheduled items + priority discretionary items]
**Tuesday:** [...]
**Wednesday:** [...]
**Thursday:** [...]
**Friday:** [...]
### Parked for Next Week
[Items that did not make the cut, with a note on why and when to revisit]
development
Constructs a compelling value narrative for a customer account by connecting product usage to business outcomes in the customer's language. Produces different versions for different audiences -- the champion, the CFO, the board. Use when asked to build a value story, articulate ROI, create a business case for the customer, prepare value evidence for a renewal or QBR, or when a CSM needs to translate usage metrics into business impact the customer will recognise. Also triggers for questions about value articulation, ROI storytelling, customer business case, value evidence, or how to prove the product is worth the investment.
data-ai
Takes raw usage data -- even a spreadsheet export or pasted metrics -- and identifies patterns, risks, and opportunities. Translates product analytics into account intelligence a CSM can act on. Use when asked to interpret usage data, analyse product metrics, make sense of a usage report, identify trends in customer behaviour, flag usage-based risks, or when a CSM has data but does not know what it means for the account. Also triggers for questions about usage analysis, product analytics interpretation, behavioural pattern detection, usage-based risk identification, or turning raw metrics into actionable insight.
development
Builds a structured 30-60-90 day plan for a CSM taking over a new book of accounts or joining a new team. Prioritises accounts by risk and value, identifies immediate relationship actions, and structures the ramp to full productivity. Use when asked to plan a book transition, create a new CSM onboarding plan, structure a territory takeover, build a 30-60-90 plan for a new role, or when a CSM is inheriting accounts and needs a systematic approach to getting up to speed. Also triggers for questions about account transitions, new book ramp-up, CSM onboarding to a portfolio, territory planning, or how to take over accounts from another CSM.
development
Builds a mutual success plan with the customer that defines what success looks like, how it will be measured, who is responsible, and what the timeline is. Produces a shared document that both sides reference throughout the engagement. Use when asked to create a success plan, build a customer outcome framework, define success criteria with a customer, structure mutual goals, or when a CSM needs to align with a customer on what they are trying to achieve together. Also triggers for questions about success planning, outcome definition, customer goal alignment, mutual accountability frameworks, or how to ensure both sides know what success looks like.