Strategy → Plan Flow (v1.6.1)

v1.6.1 adds a 3-tier planning model to 4 workflows (/docs, /plan, /open, /end). In v1.6.3, this model is managed by the Central Gate architecture, where all tiers are strictly enabled via fields in project.md rather than filesystem probing.

The 3-Tier Model

┌─────────────────────────────────────────────────────────────┐
│ Tier 1: docs/strategy/          WHY + WHAT  (opt-in)       │
│         ├── strategy.md          Overall strategy           │
│         └── strategy-*.md        Branch-specific strategy   │
├─────────────────────────────────────────────────────────────┤
│ Tier 2: plans/*-roadmap.md      HOW (overview)  (opt-in)   │
│         Living index — phases → links to detail plans       │
│         Never archived, never set as active_plan            │
├─────────────────────────────────────────────────────────────┤
│ Tier 3: plans/*.md              HOW (detail)   (always)    │
│         Task-level phases — IS active_plan                  │
│         Archived to plans/done/ when complete               │
└─────────────────────────────────────────────────────────────┘

Use as many tiers as your project needs:

Project Size	Tier 1 (Strategy)	Tier 2 (Roadmap)	Tier 3 (Detail)
Small (1-2 features)	—	—	1 plan
Medium (CLI, app)	optional	✅	multiple plans
Ecosystem (meta)	✅	✅	per satellite

End-to-End Flow

/brainstorm  ──▶  /docs new     ──▶  /plan create  ──▶  /open & /end
(ideation)        (strategy/)         (roadmap/plan)     (context + sync)

Step-by-Step

Brainstorm (/brainstorm) — Option D smart-routes to /docs for strategy creation.
Create Strategy (/docs new) — Step 3.5 detects docs/strategy/ or suggests creation.
Create Roadmap (/plan create) — Step 2.8 asks: Roadmap or Detail Plan? Choose 🗺️ Roadmap.
Create Detail Plan (/plan create) — Step 2.8 detects existing roadmap → suggests next phase. Step 2.9 loads strategy + roadmap context.
Daily Dev (/open) — Loads strategy summary (~30 tokens), roadmap overview (~40 tokens), pending brainstorms (~20 tokens). Cascade warning (D10) if strategy is newer than roadmap.
End Session (/end) — Step 3.2 detects strategy/roadmap changes → SYNC entries. Step 3.3 suggests next steps for new brainstorms. Step 4.5 auto-updates roadmap phase status.
Plan Complete (/plan review) — Archives detail plan, updates roadmap phase → ✅ Done, suggests creating next phase’s detail plan.

Key Decisions

#	Decision	Resolution
D7	Brainstorm vs Strategy priority	Strategy wins — skip older brainstorm
D10	Strategy change cascade	Date compare → warn if roadmap stale
D4	`active_plan` scope	Detail plans only, never roadmap
D6	`/brainstorm` Option F “Strategy”?	No — smart routing via Option D

Filesystem Detection

As of v1.6.3, the system uses field-gated detection via the Central Gate:

Tier	`project.md` Field	Used By
Strategy	`strategy: "docs/strategy/..."`	`/docs`, `/plan`, `/open`, `/end`
Roadmap	`roadmap: "plans/*-roadmap.md"`	`/plan`, `/open`, `/end`
Detail	`active_plan: "plans/*.md"`	All workflows

Roadmap Rules

Naming: [scope]-roadmap.md (e.g., ecosystem-roadmap.md)
Never set as active_plan
Never archived to done/
Auto-updated when a detail plan is activated or completed

Added in v1.6.1. See also: Meta-Project Guide · Ecosystem Architecture · Planning & Backlog

→ Learn: Meta-Project Guide → Learn: Ecosystem Architecture → Learn: Planning & Backlog Guide