agentleFS
derekrossderekross/derek-claude-skills/strategic-planning/SKILL.md

strategic-planning

Skill1 starsChanged 10 months agoMITView on GitHub

Create strategic plans and execute them systematically. Use for conference planning, product launches, campaign strategies, and project management.

6 other projects use 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. 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 5

    Distinctive

    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:

    Create comprehensive strategic plans and break them into actionable steps with clear milestones and tracking.

    line 8
  2. Distinctive:

    Use this skill when you need to:

    line 12
  3. Distinctive:

    Create quarterly/annual goals

    line 18
  4. Distinctive:

    Use the Eisenhower Matrix:

    line 132
  5. Distinctive:

    Urgent + Important: Do now

    line 133

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “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

Strategic Planning

Create comprehensive strategic plans and break them into actionable steps with clear milestones and tracking.

When to Use This Skill

Use this skill when you need to:

  • Plan a conference or event
  • Prepare a product launch strategy
  • Organize a marketing campaign
  • Manage complex multi-week projects
  • Coordinate multiple stakeholders
  • Create quarterly/annual goals
  • Plan content or community initiatives

Planning Framework

1. Define the Vision

  • What does success look like? (specific, measurable)
  • Why does this matter? (motivation/purpose)
  • When does it need to happen? (deadline)
  • Who is involved? (stakeholders, team)

2. Assess Current State

  • Resources available (time, money, people)
  • Constraints and limitations
  • Dependencies on others
  • Risks and unknowns

3. Strategic Pillars

Break the goal into 3-5 major workstreams:

  • Each pillar is a major area of focus
  • Pillars should be relatively independent
  • Each has its own owner/lead

4. Tactical Breakdown

For each pillar:

  • Key milestones with dates
  • Specific tasks
  • Dependencies between tasks
  • Success criteria

5. Timeline & Rhythm

  • Work backwards from deadline
  • Build in buffer time (20% minimum)
  • Set regular check-in cadence
  • Define decision points

Plan Templates

Conference/Event Plan

Vision Statement: [Event Name] on [Date] will [outcome] for [audience].

Pillars:

  1. Venue & Logistics
    • Location secured by [date]
    • A/V requirements by [date]
    • Catering finalized by [date]
  2. Content & Speakers
    • CFP opens [date], closes [date]
    • Speakers confirmed by [date]
    • Schedule published by [date]
  3. Marketing & Promotion
    • Announce date by [date]
    • Early bird tickets by [date]
    • Speaker announcements [cadence]
  4. Sponsorship
    • Prospectus ready by [date]
    • Outreach begins [date]
    • Commitments secured by [date]
  5. Operations
    • Volunteer recruitment by [date]
    • Day-of schedule by [date]
    • Contingency plans by [date]

Product Launch Plan

Vision Statement: Launch [Product] by [Date] reaching [metric] with [outcome].

Pillars:

  1. Product Readiness
    • Feature complete by [date]
    • Beta testing [date range]
    • Bug fixes complete by [date]
  2. Documentation
    • Getting started guide by [date]
    • API docs by [date]
    • Tutorial content by [date]
  3. Marketing & Comms
    • Messaging finalized by [date]
    • Assets created by [date]
    • Launch posts scheduled by [date]
  4. Community Preparation
    • Beta testers recruited by [date]
    • Support channels ready by [date]
    • FAQ prepared by [date]

Campaign Strategy

Vision Statement: [Campaign] will [action] resulting in [metric] by [date].

Pillars:

  1. Content Creation
  2. Distribution Channels
  3. Community Engagement
  4. Measurement & Iteration

Execution Framework

Weekly Rhythm

  • Monday: Review week's priorities, blockers
  • Mid-week: Progress check, adjust if needed
  • Friday: Week recap, next week prep

Task Prioritization

Use the Eisenhower Matrix:

  • Urgent + Important: Do now
  • Important + Not Urgent: Schedule
  • Urgent + Not Important: Delegate
  • Neither: Eliminate

Progress Tracking

For each task track:

  • Status: Not Started / In Progress / Blocked / Complete
  • Owner
  • Due date
  • Actual completion date
  • Notes/blockers

Risk Management

Maintain a risk register:

  • Risk description
  • Likelihood (H/M/L)
  • Impact (H/M/L)
  • Mitigation strategy
  • Owner

Decision Framework

When facing decisions:

  1. What are we deciding?
  2. What are the options?
  3. What are the criteria?
  4. Who needs to be involved?
  5. What's the deadline for deciding?
  6. How will we communicate the decision?

Plan Review

After Action Review

Post-event/project:

  1. What did we set out to do?
  2. What actually happened?
  3. Why did it happen that way?
  4. What will we do differently next time?

Metrics to Track

  • Timeline adherence
  • Budget adherence
  • Quality metrics
  • Stakeholder satisfaction
  • Key outcomes achieved

Example Prompts This Skill Handles

  • "Create a plan for Bitcoin Conference Week 2026"
  • "Help me strategize the diVine launch"
  • "Build a 90-day marketing plan for Shakespeare"
  • "Plan the NosVegas side event"
  • "Create a quarterly roadmap for community building"

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.