Individual skill
strategy-builder
Draft STRATEGY.md from a goal - read the operator's brief (goal, repo, links) plus the repo README and memory, then write a tight north-star/priorities/audience/constraints strategy.
skills/strategy-builder/SKILL.md
Source commit 25575a6be3bfab41925964de55654056a2fe0c39
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 789
- Repository last updated
- Nov 7, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agents Repository topic
- claude-code Repository topic
- agent-framework Repository topic
- agents Repository topic
- ai Repository topic
- anthropic Repository topic
- claude Repository topic
- harness Repository topic
- llm Repository topic
- automation Repository topic
- meta Declared skill tag
- productivity Declared skill tag
- productivity Derived category
- docs Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
> **${var}** — a brief. Two accepted shapes:
> - **Structured (from the dashboard):** ` | `-separated tokens — any of `repo=<owner/repo>`, `links=<url1,url2>`, `goal=<free text>`. `goal` is the **last** token; everything after `goal=` is the goal text. Example: `repo=acme/widgets | links=https://acme.com | goal=grow paying teams, win on reliability`.
> - **Bare text:** just the goal, e.g. `growing my open-source agent framework — active contributors, not stars`.
>
> If `${var}` is empty, fall back to the repo README + `memory/MEMORY.md` to infer direction. If even that yields nothing usable, log `STRATEGY_BUILDER_SKIP: no brief — set var or add a goal` and stop with no notification.
Today is ${today}. This skill writes **`STRATEGY.md`** — the operator's north-star. It's imported into `CLAUDE.md`, so it rides along in the context of **every** skill run. That sets the bar: it must be **tight** (it costs tokens every run) and **specific** (a vague strategy can't break a tie when a skill has to choose what to work on).
This is the agent behind the dashboard's **Strategy → Build my strategy** button.
## Why this skill exists
Most forks never tailor `STRATEGY.md` — it sits on the unconfigured defaults, so skills operate with no specific bias. But the operator's direction is usually knowable from a sentence of intent plus what's already in the repo (README, what's being shipped, MEMORY.md). This skill turns that into a strategy skills can actually act on: one outcome to optimize, a few ordered priorities, the audience, and the hard lines.
