Strategy session skill. Interactive founder Q&A that produces an initiative document with project suggestions. Triggers: 'd-strategy', 'strategy session', 'new initiative', 'what should we build next'.
Interactive founder Q&A that produces a strategy initiative. Reads codebase state, past initiative learnings, and domain context to ask smart questions. Outputs an initiative folder with document.md, suggested project breakdown, and empty future-work.md.
d-strategy → gstack reviews (CEO/eng/design) → d-roadmap → /ship
Before asking questions, load this context silently:
Codebase state:
tokei --sort lines 2>/dev/null || echo "tokei not installed"
git log --oneline -20
All nested CLAUDE.md files (skim for what exists):
fd CLAUDE.md --type f
Maturity context (ALWAYS read these first):
decisions/maturity.md — principles, level definitions, categories, decision filterdecisions/health.md — current maturity scores per category, bottlenecksDomain context (based on which domain the user specifies):
decisions/product/context.mddecisions/growth/context.mddecisions/harness/context.mdPrevious initiative (if exists):
ls decisions/{domain}/document.md and future-work.md for continuityUniversal files relevant to the domain:
decisions/company.mddecisions/voice.md (for content positioning)decisions/voice.mddecisions/harness.md, decisions/code.mdPrevious initiative (if exists):
ls decisions/{domain}/document.md and future-work.md for continuityIf the user didn't specify a domain, ask:
Which domain is this initiative for?
A) Product — features, UX, pricing, user experience
B) Growth — content, distribution, conversion, expansion
C) Harness — AI methodology, skills, hooks, workflows
Wait for response. Use the selected domain for all subsequent steps.
Summarize in 3-5 bullets:
Each question must have 2-3 concrete options (not open-ended "describe your thinking").
Example question format:
Q1: What's the primary goal of this initiative?
A) Revenue — get paying customers faster (free funnel, checkout optimization, pricing experiments)
B) Retention — make existing users stick (decision graph, streaks, follow-ups)
C) Foundation — build infrastructure that multiple future features need (schema, API, auth)
Question topics to cover:
Wait for the user to answer ALL questions before proceeding.
Determine the next initiative number. Use Bash:
ls decisions/{domain}/ | sort -n | tail -1
If no numbered folders exist, start with 01. Otherwise increment the highest number.
Increment by 1. Create the folder.
# {Initiative Title}
> Domain: {product|growth|harness}
> Created: {YYYY-MM-DD}
> Status: draft
## Context
{2-3 paragraphs: what exists, what's missing, why now}
## Goal
{1 sentence: what success looks like}
## Constraint
{1 sentence: the tightest constraint}
## Projects (suggested breakdown)
### Project 1: {name}
- **Scope:** {1-2 sentences}
- **Deliverables:** {bullet list}
- **Acceptance criteria:** {bullet list}
- **Risk:** {1 sentence}
### Project 2: {name}
...
## Decision Log
| Decision | Choice | Why |
|----------|--------|-----|
| {first decision from Q&A} | {choice} | {reasoning} |
## Open Questions
- {anything unresolved from the Q&A}
# Future Work — {Initiative Title}
> Updated: {YYYY-MM-DD}
Items deferred from this initiative for future consideration.
(empty — populated by d-code as projects complete)
Initiative created: decisions/{domain}/NN-name/
Next steps:
1. Run gstack reviews to refine: /plan-ceo-review, /plan-eng-review, /plan-design-review
2. After reviews settle the project breakdown: /d-roadmap
3. Then execute per-project: d-code or d-content