strategylisted

Structured workflow for creating STRATEGY documents — medium-term defensibility bets that operationalize a piece of an upstream VISION without re-justifying the long-term thesis. Use when the work in front of the team needs a falsifiable bet, building-block decomposition, coordination dependencies, and per-direction invalidation conditions — but doesn't pivot the upstream VISION and isn't ready to commit to a ROADMAP's sequenced feature list. Triggers on "draft a strategy for X", "what's our bet on Y", "operationalize the VISION", "we need a strategic doc between vision and roadmap", or "STRATEGY-<name>". Do NOT use for long-term thesis articulation (/vision), feature sequencing (/roadmap), feature requirements (/prd), or open-ended exploration (/explore). Drives a six-phase workflow: conversational scoping, structured drafting, Building Blocks decomposition, three-reviewer jury, finalization.
tsukumogami/shirabe · ★ 0 · AI & Automation · score 67

Install: claude install-skill tsukumogami/shirabe

@.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. **Writing style:** Read `skills/writing-style/SKILL.md` for guidance. ## Artifact Lifecycle **Lifecycle:** Durable. Stays in `docs/strategies/` after completion. STRATEGY is durable because the medium-term bet — the falsifiable claim a project pursues — stays in the audit trail. Future readers reviewing which strategic direction was taken need the STRATEGY to remain in place. ## Strategy Format See `references/strategy-format.md` for the full format specification: frontmatter schema, required and optional sections, visibility-gated sections, section matrix, content boundaries, lifecycle states, validation rules, and quality guidance. Load it during Phases 2, 3, and 4. ## File Location STRATEGY documents live at `docs/strategies/STRATEGY-<topic>.md` (kebab-case). No directory movement until Sunset, which moves files to `docs/strategies/sunset/`. Stable paths keep cross-references durable and git bl