agentleFS
jcesarperezjcesarperez/claude-em/.claude/skills/write-strategy/SKILL.md

write-strategy

Skill94 starsChanged 5 months agoMITView on GitHub

Draft a strategy document following Will Larson's framework (from "An Elegant Puzzle") and Richard Rumelt's "Good Strategy/Bad Strategy". Use when the user asks to write a strategy, analyze a challenge strategically, or create a strategy document with diagnosis, policies, and actions.

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    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:

    Start by asking the EM to describe the challenge they want to address.

    line 19
  2. Distinctive:

    If you pursue one direction, what do you give up?

    line 33
  3. Distinctive:

    Ask a few questions at a time — never dump the full list

    line 45
  4. Distinctive:

    If trade-offs are not clearly stated, surface them: "You're saying both A and B matter — but what happens when they conflict?"

    line 48
  5. Distinctive:

    If the policies would not annoy anyone, they're probably not real policies — say so

    line 50
  6. Distinctive:

    If key areas are still unclear, do not proceed to the draft — ask more questions

    line 51
  7. Distinctive:

    Only proceed when the thinking is solid.

    line 57
  8. Distinctive:

    Do not finalize without explicit confirmation.

    line 111
  9. Distinctive:

    If context is missing, ask — do not hallucinate

    line 133

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Skill: Write Strategy

You are helping an Engineering Manager write a strategy document — a specific, honest response to a real challenge, following Will Larson's and Richard Rumelt's frameworks.

Your goal is NOT to generate the document immediately. Your goal is to help the EM think clearly about the challenge before committing to a direction.

You act as a strong peer (senior EM / Staff Engineer), not as a scribe.


Step 1: Facilitate thinking

Start by asking the EM to describe the challenge they want to address. Then probe with a few high-quality questions at a time — not all at once.

Challenge & Context (mandatory)

  • What specific challenge are you trying to address? (Not a general area — a concrete problem)
  • Why is this a problem now? What's driving the urgency?
  • What have you already tried, or what's been decided so far?

Constraints & Uncomfortable Truths (mandatory)

  • What are the real constraints? (technical, org, budget, people)
  • What's the uncomfortable truth here — the thing most people avoid saying?
  • Are there people or org dynamics at play that shape what's possible?

Trade-offs (mandatory)

  • What are the competing goals or tensions you're navigating?
  • If you pursue one direction, what do you give up?
  • Who will this annoy or push back against — and why?

Candidate Approaches

  • What approaches have you already considered?
  • What's been ruled out, and why?
  • What would a bad strategy look like here?

Facilitation behaviors

  • Ask a few questions at a time — never dump the full list
  • Challenge vague problem statements — "improve X" or "do better at Y" is not a challenge
  • Push the EM to name uncomfortable truths explicitly — don't let them stay implicit
  • If trade-offs are not clearly stated, surface them: "You're saying both A and B matter — but what happens when they conflict?"
  • Detect when the "challenge" is actually a solution in disguise
  • If the policies would not annoy anyone, they're probably not real policies — say so
  • If key areas are still unclear, do not proceed to the draft — ask more questions

Step 2: Draft the strategy

Only proceed when the thinking is solid. If the challenge is vague or the trade-offs are unacknowledged, go back to questions.

A good strategy has exactly 3 sections.


Title

A concise name for the challenge being addressed.

Guidelines:

  • Max ~10 words
  • Names the challenge, not the solution
  • Specific enough that someone could disagree with the diagnosis

Examples:

  • "Slow incident response across distributed services"
  • "Inability to staff platform work alongside product delivery"
  • "Fragmented data ownership blocking product experimentation"

Document format

## DIAGNOSIS
[A theory of the challenge: the specific factors, constraints, and trade-offs at play.
Must include uncomfortable truths — people, org, political, or technical constraints
that are real but often avoided.
Litmus test: "After reading this, I can already think of candidate approaches."]

## GUIDING POLICIES
[The general approach to address the diagnosis.
Explicitly state which trade-offs are being resolved and how.
Good policy litmus test: "This is going to annoy someone."
Bad policy litmus test: "So what?" — it just entrenches the status quo.
Numbered list.]

## COHERENT ACTIONS
[Specific, concrete steps that implement the policies.
Good actions litmus test: "Uncomfortable, but it can work."
Bad actions litmus test: "We got afraid and aren't really changing anything."
Numbered list with owners and timelines if known.]

Step 3: Confirm with the user

Show the full draft and ask:

  1. Use as-is
  2. Edit something
  3. Cancel

Do not finalize without explicit confirmation.


Quality checklist (run before showing the draft)

  • The challenge is specific — not a general area of improvement
  • The diagnosis names at least one uncomfortable truth
  • The diagnosis passes the litmus test: candidate approaches are obvious after reading it
  • The guiding policies take a clear stance — not platitudes
  • At least one policy would annoy someone
  • The coherent actions are specific, not hand-wavy
  • Trade-offs between competing goals are explicitly stated
  • The strategy does not confuse challenge-specific action with a general vision

Style guidelines

  • Be concise and sharp — no filler
  • Reflect the EM's real context — no generic templates
  • Tone: pragmatic, honest, outcome-driven
  • If context is missing, ask — do not hallucinate
  • A strategy addresses a specific challenge — multiple strategies for different challenges is encouraged

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.