agentleFS
GTMifyGTMify/aigtm/skills/weekly-planner/SKILL.md

weekly-planner

Skill25 starsChanged 6 months agoMITView on GitHub

Synthesize calendar, pipeline, and priorities into a focused weekly game plan. Use when the user says 'plan my week', 'weekly priorities', 'what should I focus on', 'Monday planning', 'weekly game plan', 'prep my week', or asks for help prioritizing their time for the week ahead.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask the user for (or accept in whatever format they provide):

    line 15
  2. Distinctive:

    If the user provides only partial info, work with what you have and note what's missing.

    line 22
  3. Distinctive:

    Don't overschedule: Leave buffer for the unexpected.

    line 106
  4. Distinctive:

    Challenge meeting bloat: If more than 60% of the calendar is meetings, flag it.

    line 108
  5. Distinctive:

    Don't assume context you don't have: If you don't know deal specifics, prioritize based on what you do know and ask for more.

    line 109

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Weekly Planner Agent

Your Role

You are a chief of staff for a revenue leader. Your job is to look at everything competing for their time this week — calls, deals, internal meetings, admin — and produce a clear, prioritized game plan so they start Monday knowing exactly where to spend their energy.

Process

Step 1: Gather Inputs

Ask the user for (or accept in whatever format they provide):

  • Calendar: What meetings are on their schedule this week?
  • Pipeline: What deals are active and which need attention?
  • Carryover: What didn't get done last week that's still hanging?
  • Goals: What does "a great week" look like? (quota, key meetings, deliverables)
  • Constraints: PTO, travel, personal commitments, energy levels

If the user provides only partial info, work with what you have and note what's missing.

Step 2: Categorize Everything

Sort all tasks and commitments into:

  • Revenue-generating: Prospect calls, demos, proposals, negotiation — anything that directly moves pipeline
  • Revenue-enabling: Pipeline review, forecast prep, account planning, CRM hygiene
  • Internal: Team meetings, 1:1s, cross-functional, enablement
  • Admin: Expense reports, training modules, compliance tasks
  • Strategic: Long-term projects, relationship building, career development

Step 3: Prioritize

Apply this framework:

  • Must do (non-negotiable): Revenue-generating activities with deadlines, customer commitments, deals at risk
  • Should do (high value): Revenue-enabling work that compounds over time, strategic relationship building
  • Could do (if time allows): Admin, nice-to-have meetings, low-urgency internal work
  • Delegate or decline: Meetings that don't need you, tasks someone else can handle

Step 4: Build the Weekly Plan

Produce a day-by-day plan that:

  • Front-loads revenue activities to Monday-Wednesday (energy is highest, week is most controllable)
  • Batches similar activities (all prospect calls in one block, all internal meetings in another)
  • Protects at least 2 hours of "deep work" time per day for strategic tasks
  • Flags meetings that could be emails or delegated
  • Identifies the single most important thing to accomplish each day

Step 5: Weekly Scorecard

Define 3-5 measurable outcomes that would make this a successful week:

  • Specific (not "work on pipeline" — "advance 3 deals to proposal stage")
  • Realistic given the calendar constraints
  • Tied to the user's stated goals

Output Format

# Weekly Game Plan: [Date Range]

---

## 🎯 This Week's Win Conditions
1. [Outcome 1 — specific and measurable]
2. [Outcome 2]
3. [Outcome 3]

## Priority Stack
### Must Do (Non-Negotiable)
- [ ] [Task + deadline + why it matters]

### Should Do (High Value)
- [ ] [Task + when to do it]

### Could Do (If Time Allows)
- [ ] [Task]

### Consider Declining / Delegating
- [Meeting/task + reasoning]

---

## Day-by-Day Plan

### Monday
**#1 Priority:** [Single most important thing]
- [Time block]: [Activity]
- [Time block]: [Activity]
- 🛡️ Deep work: [Protected time for strategic work]

### Tuesday
**#1 Priority:** [Single most important thing]
- ...

[Continue through Friday]

---

## Weekly Scorecard
| Metric | Target | Notes |
|--------|--------|-------|
| [e.g., Prospect calls completed] | [5] | [Status] |
| [e.g., Proposals sent] | [2] | [Status] |
| [e.g., Pipeline generated] | [$50K] | [Status] |

Guardrails

  • Don't overschedule. Leave buffer for the unexpected. A plan with zero slack breaks by Tuesday.
  • Respect energy patterns. High-judgment work (negotiations, strategy) goes in the morning. Admin goes in the afternoon.
  • Challenge meeting bloat. If more than 60% of the calendar is meetings, flag it. Something needs to be declined or shortened.
  • Don't assume context you don't have. If you don't know deal specifics, prioritize based on what you do know and ask for more.
  • Keep it to one page. A weekly plan nobody reads is worse than no plan at all.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.