← ClaudeAtlas

strategylisted

Work out what you are betting on over the next few quarters and what would prove it wrong: the angle, the pieces that have to land for it to hold, who else has to move, and the signal that would say it was the wrong call. Use it when the direction matters more than the feature list — "what's our angle here?", "what are we actually betting on?", "what has to be true for this to work?", "how would we know if this was the wrong call?", "how do we avoid getting commoditized?", "why would this still matter in a year?" — and also when you are holding a settled feature spec and the real question is the bet behind it. Left unwritten, the bet lives in one person's head and nothing can falsify it. Do NOT use it to argue why the project should exist at all (`/vision`), to order the features that carry the bet (`/roadmap`), or to pick between options already named (`/decision`). When more than one of those is open at once, `/charter` runs them together.
tsukumogami/shirabe · ★ 0 · AI & Automation · score 67
Install: claude install-skill tsukumogami/shirabe
!`bash ${CLAUDE_PLUGIN_ROOT}/scripts/skill-preflight.sh strategy 2>&1 || true` @.claude/shirabe-extensions/strategy.md @.claude/shirabe-extensions/strategy.local.md # Strategy Documents STRATEGY documents capture the medium-term bet a project commits to when operationalizing a piece of an upstream VISION. They sit between VISION (long-term aspiration, years) and ROADMAP (sequenced features) at medium-term defensibility altitude. Each STRATEGY names a falsifiable hypothesis, decomposes it into coherent building blocks, maps coordination dependencies, and lists per-direction invalidation conditions so the team can recognize when the bet has been wrong. A STRATEGY links one level in each direction: its upstream is a VISION, and its Downstream Artifacts are ROADMAPs. Keeping the links strict is what makes the chain walkable -- a reader moving VISION -> STRATEGY -> ROADMAP hits every altitude in order rather than landing two levels down with the reasoning in between skipped. The ROADMAP is the boundary between the strategic chain and the tactical one, and `/brief` is what crosses it, so a STRATEGY never links a PRD, DESIGN, or PLAN directly. A PRD can still ground the conversation — `/strategy docs/prds/PRD-<name>.md` reads one to derive the bet, and an author holding a feature PRD who wants the medium-term bet behind it has a real strategy to write. But reading a document and recording it as the strategy's parent are different acts. `upstream:` takes a VISION or nothing; a s