strategylisted
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