Strategy
Align every skill run to a single north-star metric, ranked priorities, audience, and hard constraints in STRATEGY.md.
STRATEGY.md is the operator's brief at the repository root. Imported into CLAUDE.md via @STRATEGY.md, it sits in context on every run so skills prioritize the same goal without per-skill prompt edits.
The Five Fields
Keep STRATEGY.md concise so it costs minimal tokens on each run:
# Strategy
## North-star metric
> Weekly active teams - not signups.
## Priorities # most important first, cap at ~5
1. Correct, verifiable work over work that looks finished.
2. Depth on core projects over broad, shallow coverage.
3. Surface signal early - don't sit on a decision.
## Audience
> Technical founders, short on time.
## Hard constraints # lines never to cross
- Never publish secrets or unverified claims as fact.
- Stay within configured spend and rate limits.
## Optimize for / avoid
- Optimize for: signal, correctness, the priorities above.
- Avoid: filler, hype, busywork, anything off-strategy.Wiring into CLAUDE.md
CLAUDE.md pulls STRATEGY.md in with a single @STRATEGY.md import:
## Strategy
STRATEGY.md is the operator's north-star - overarching goal,
priorities, audience, and hard constraints. Read it at the start
of every task and align your output to it; when a choice isn't
otherwise determined, let the strategy break the tie.
@STRATEGY.mdUnconfigured by default
New instances ship STRATEGY.md with neutral defaults and a Status: unconfigured defaults line. Remove that status line once you customize the file, or run strategy-builder to draft one.
Strategy vs Soul
STRATEGY.mdsets intent (what to work on, prioritize, or skip) and loads on every run.soul/sets voice (how to write) and loads only when producing human-facing output.