@thierrynakoa/fire-flow 10.0.0 → 12.2.0

package/commands/fire-1a-new.md

@@ -0,0 +1,216 @@
+---
+description: Initialize a new project with Dominion Flow (Dominion Flow)
+---
+
+# /fire-1a-new
+
+> Initialize a new project — scaffold directory, gather requirements, create .planning/ structure
+
+---
+
+## Purpose
+
+Create the project foundation: directory, requirements gathering, and the complete `.planning/` file structure. This is Step 1 of 3 in project initialization.
+
+**Flow:** `/fire-1a-new` → `/fire-1b-research` → `/fire-1c-setup`
+
+---
+
+## Arguments
+
+```yaml
+arguments: none
+optional_flags:
+  --name: "Project name (will prompt if not provided)"
+  --path: "Project path (defaults to current directory)"
+  --minimal: "Skip adaptive questioning, use defaults"
+```
+
+---
+
+## EXECUTION ORDER
+
+```
+STEP 1: Environment Validation  → create NEW project directory
+STEP 2: Gather Requirements     → MODE GATE question, backward interview if needed
+STEP 3: Create .planning/       → mkdir + touch ALL files (EXACT names, no renaming)
+FINAL:  Chain to next command    → tell user to run /fire-1b-research
+```
+
+**Complete each step before starting the next. No skipping.**
+
+---
+
+## Step 1: Environment Validation
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+                         DOMINION FLOW > PROJECT INITIALIZATION
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+```
+
+1. **Create a NEW project directory** — Do NOT initialize inside an existing project. If the current directory has source code, `package.json`, or `.planning/`, create a new directory:
+   ```bash
+   mkdir -p {project-path}/{project-name}
+   cd {project-path}/{project-name}
+   git init
+   ```
+   Use `--path` flag if provided, otherwise ask the user or derive from project name.
+2. Check if `.planning/` already exists (warn if so — means project was already initialized)
+3. Verify write permissions
+4. Create git repo if not present
+
+---
+
+## Step 2: Gather Requirements
+
+**Core Questions:**
+1. What is this project? (one sentence)
+2. Who is the primary user?
+3. What is the core value it provides?
+4. What are the non-negotiable features (must-haves)?
+
+**The MODE GATE Question:**
+
+> **"Have you already started building this, or are we starting from scratch?"**
+
+This reveals technical level without asking them to self-assess:
+
+| Answer | Mode |
+|--------|------|
+| "I already have a React app with Express backend" | **Forward** — validate their stack |
+| "I started something but I'm stuck" | **Forward** — audit what exists |
+| "Starting from scratch, but I want Python" | **Forward** — build around preference |
+| "Starting from scratch" | **Backward** — derive stack from vision |
+| "I have an idea but don't know where to start" | **Backward** — full interview |
+| "I have a WordPress site and want to add features" | **Forward** — WordPress-aware stack |
+
+**If Forward Mode** (user has code or stated tech preferences):
+1. Existing codebases to integrate with?
+2. Known technical constraints?
+3. *(Anti-Frankenstein gate validates choices later in /fire-1b-research)*
+
+**If Backward Mode** (user described product, not tech):
+Use the interview protocol from `@skills-library/_general/methodology/BACKWARD_PLANNING_INTERVIEW.md`:
+
+0. **Visual Input (ALWAYS ask first)** — "Do you have anything visual — screenshot, wireframe, sketch? Drop it here."
+   - If provided: Extract requirements, save to `.planning/research/VISUAL-ANALYSIS.md`, skip questions already answered
+   - If not: Proceed to question 1
+1. **The Walkthrough** — "Walk me through a user's first 60 seconds"
+2. **The Money Screen** — "What's the ONE screen where your app delivers the most value?"
+3. **The Similar App** — "Name 1-2 apps that feel closest to yours"
+4. **The Deal-Breakers** — Yes/no: login, payments, uploads, emails, mobile, real-time
+5. **The MVP Gate** — "If you could only ship THREE features, which three?"
+
+**Timeline Questions:**
+1. Target completion date?
+2. Critical milestones?
+
+**Save outputs:**
+- `.planning/PROJECT.md` — requirements summary
+- `.planning/REQUIREMENTS.md` — REQ-IDs for traceability
+
+---
+
+## Step 3: Create .planning/ Structure
+
+**Create directories:**
+
+```bash
+mkdir -p .planning/breadcrumbs .planning/research .planning/phases
+```
+
+**Breadcrumbs are ON-DEMAND — do NOT create empty files.** Agents create breadcrumb files when they have something worth recording. The directory exists; the files don't — until earned.
+
+When agents write breadcrumbs, they use these EXACT names:
+- `breadcrumbs/LESSONS.md` — Solutions that worked
+- `breadcrumbs/FAILURES.md` — Approaches that failed
+- `breadcrumbs/PATTERNS.md` — Project conventions
+- `breadcrumbs/DEPENDENCIES.md` — Library gotchas
+
+> See `@skills-library/_general/methodology/LIVE_BREADCRUMB_PROTOCOL.md` for the full protocol.
+
+**Create CONSCIENCE.md** using template from `@templates/state.md`:
+- Project name and core value
+- Current phase: 1 of N (placeholder until ROADMAP.md exists)
+- Status: Ready to research
+- WARRIOR Integration section
+- Session Continuity section
+
+**After Step 3, these files MUST exist:**
+
+```
+.planning/
+├── PROJECT.md              # Step 2
+├── REQUIREMENTS.md         # Step 2
+├── CONSCIENCE.md           # Step 3
+├── breadcrumbs/            # Step 3 (empty dir — files created on-demand by agents)
+├── research/               # empty, ready for /fire-1b-research
+└── phases/                 # empty, ready for /fire-2-plan
+```
+
+**Verify before proceeding:**
+```bash
+test -f .planning/PROJECT.md && test -f .planning/REQUIREMENTS.md && test -f .planning/CONSCIENCE.md && test -d .planning/breadcrumbs && echo "ALL FILES PRESENT" || echo "MISSING FILES — go back"
+```
+
+---
+
+## Completion
+
+```
++==============================================================================+
+| SCAFFOLD COMPLETE                                                            |
+|==============================================================================|
+|                                                                              |
+|  Project: {project_name}                                                     |
+|  Mode:    {forward/backward}                                                 |
+|  Status:  Ready to research                                                  |
+|                                                                              |
+|  Created:                                                                    |
+|    [x] .planning/PROJECT.md              <- requirements                     |
+|    [x] .planning/REQUIREMENTS.md         <- REQ-IDs                          |
+|    [x] .planning/CONSCIENCE.md           <- project state                    |
+|    [x] .planning/breadcrumbs/            <- on-demand memory (empty until    |
+|                                             agents record learnings)         |
+|                                                                              |
+|  Pending (created by next commands):                                         |
+|    [ ] research/SYNTHESIS.md             <- /fire-1b-research                 |
+|    [ ] VISION.md                         <- /fire-1b-research                 |
+|    [ ] ROADMAP.md                        <- /fire-1b-research                 |
+|    [ ] TOOLING-LOG.md                    <- /fire-1c-setup                    |
+|    [ ] WARRIOR handoff                   <- /fire-1c-setup                    |
+|                                                                              |
+|==============================================================================|
+| NEXT UP                                                                      |
+|------------------------------------------------------------------------------|
+|                                                                              |
+|  -> Run /fire-1b-research to spawn researchers and select architecture        |
+|                                                                              |
++==============================================================================+
+```
+
+---
+
+## Error Handling
+
+### .planning/ Already Exists
+
+```
+╔══════════════════════════════════════════════════════════════════════════════╗
+║ ⚠ WARNING: Existing Project Detected                                         ║
+╠══════════════════════════════════════════════════════════════════════════════╣
+║  Options:                                                                    ║
+║    A) Use `/fire-6-resume` to continue existing project                     ║
+║    B) Delete .planning/ and run `/fire-1a-new` again                         ║
+║    C) Use `--path [new-directory]` to initialize elsewhere                   ║
+╚══════════════════════════════════════════════════════════════════════════════╝
+```
+
+---
+
+## References
+
+- **Template:** `@templates/state.md` - CONSCIENCE.md template
+- **Skill:** `@skills-library/_general/methodology/BACKWARD_PLANNING_INTERVIEW.md`
+- **Brand:** `@references/ui-brand.md` - Visual output standards

package/commands/fire-1b-research.md

@@ -0,0 +1,210 @@
+---
+description: Research, vision selection, and roadmap generation for a new project (Dominion Flow)
+---
+
+# /fire-1b-research
+
+> Spawn researchers, select architecture vision, generate roadmap
+
+---
+
+## Purpose
+
+Research the technology landscape, select a coherent architecture, and generate the project roadmap. This is Step 2 of 3 in project initialization.
+
+**Flow:** `/fire-1a-new` → **`/fire-1b-research`** → `/fire-1c-setup`
+
+**Prerequisite:** `.planning/PROJECT.md` and `.planning/REQUIREMENTS.md` must exist (created by `/fire-1a-new`).
+
+---
+
+## EXECUTION ORDER
+
+```
+STEP 1: Validate prerequisites     → PROJECT.md + REQUIREMENTS.md exist
+STEP 2: Research Synthesis          → spawn researchers, search GitHub, write SYNTHESIS.md
+STEP 3: Vision Branch Selection     → spawn fire-vision-architect, user picks branch, LOCK VISION.md
+STEP 4: Roadmap Generation          → spawn fire-roadmapper, write ROADMAP.md
+FINAL:  Chain to next command       → tell user to run /fire-1c-setup
+```
+
+**Complete each step before starting the next. Each step produces a file — verify it exists before proceeding.**
+
+---
+
+## Step 1: Validate Prerequisites
+
+```bash
+test -f .planning/PROJECT.md && test -f .planning/REQUIREMENTS.md && echo "READY" || echo "MISSING — run /fire-1a-new first"
+```
+
+If files are missing, stop and tell the user to run `/fire-1a-new` first.
+
+Read `.planning/PROJECT.md` to determine mode (forward/backward) for Step 3.
+
+---
+
+## Step 2: Research Synthesis (MANDATORY)
+
+**Spawn 4 parallel researchers** (or sequential if resources are limited):
+
+| Researcher | Focus | Output |
+|-----------|-------|--------|
+| STACK | Technology ecosystem, versions, compatibility | `research/STACK.md` |
+| FEATURES | Feature implementation patterns, complexity | `research/FEATURES.md` |
+| ARCHITECTURE | Folder structure, data flow, API design | `research/ARCHITECTURE.md` |
+| PITFALLS | Common mistakes, known issues, anti-patterns | `research/PITFALLS.md` |
+
+**Every researcher MUST search GitHub for open source reference projects:**
+
+Search for 2-3 real open source projects similar to what the user is building:
+- Repo name, stars, last updated
+- Tech stack used
+- Folder structure patterns
+- Key patterns worth adopting
+- Mistakes visible in their issues/PRs
+
+**Search strategy:**
+```
+gh search repos "{project type}" --sort stars --limit 5
+gh search repos "{project type} {framework}" --sort updated --limit 5
+```
+
+**Then synthesize:** Merge 4 files → `.planning/research/SYNTHESIS.md`
+
+Include a "Reference Projects" section listing the best repos found, what to steal, and what to avoid.
+
+> The 4-tier cascade: Skills Library → GitHub/Open Source → Context7 → Web search.
+
+**If token-constrained:** Run a single researcher covering all 4 areas into one SYNTHESIS.md.
+
+**Gate:** SYNTHESIS.md MUST exist before Step 3.
+
+```bash
+test -f .planning/research/SYNTHESIS.md && echo "SYNTHESIS READY" || echo "MISSING — complete research first"
+```
+
+---
+
+## Step 3: Vision Branch Selection
+
+**Spawn `fire-vision-architect`** with:
+- `.planning/research/SYNTHESIS.md`
+- `.planning/PROJECT.md`
+- Any visual input from Step 2 of `/fire-1a-new`
+
+**Two modes (auto-detected):**
+
+**Forward Mode** — User stated a tech stack → Anti-Frankenstein gate checks compatibility → generate branches.
+
+**Backward Planning Mode** — User described the PRODUCT, not tech:
+```
+Visual input → capability extraction
+  + What does the finished product do?
+    → What capabilities does that require?
+      → What proven stacks deliver those? → branches
+```
+
+**Process:**
+
+1. Mode detection from PROJECT.md
+2. Anti-Frankenstein Gate (forward) or Capability Extraction (backward)
+3. Generate 2-3 vision branches (often 2 in backward mode)
+4. Display via `AskUserQuestion` — one marked "(Recommended)"
+5. User picks one
+6. **Lock selected branch as `.planning/VISION.md`**
+7. **Save rejected branches to `.planning/research/ALTERNATIVES.md`**
+
+**Gate:** VISION.md MUST exist and be LOCKED before Step 4.
+
+```bash
+test -f .planning/VISION.md && test -f .planning/research/ALTERNATIVES.md && echo "VISION LOCKED" || echo "MISSING — complete vision selection"
+```
+
+---
+
+## Step 4: Roadmap Generation (MANDATORY)
+
+**Spawn `fire-roadmapper`** with locked VISION.md:
+
+1. Reads LOCKED `VISION.md` (does NOT make stack decisions)
+2. Reads `REQUIREMENTS.md` for feature list
+3. Groups requirements into phases by dependency order
+4. Derives success criteria goal-backward from each phase objective
+5. Validates 100% requirement coverage (every REQ-ID in a phase)
+6. Writes `.planning/ROADMAP.md`
+
+**Gate:** ROADMAP.md MUST exist before completion.
+
+```bash
+test -f .planning/ROADMAP.md && echo "ROADMAP READY" || echo "MISSING — complete roadmap generation"
+```
+
+> ROADMAP.md is what `/fire-2-plan` reads. Without it, `/fire-2-plan 1` has no Phase 1 definition.
+
+---
+
+## Agent Spawning Summary
+
+| Agent | Input | Output | Step |
+|-------|-------|--------|------|
+| `fire-project-researcher` (x4) | PROJECT.md, REQUIREMENTS.md | research/*.md → SYNTHESIS.md | 2 |
+| `fire-vision-architect` | SYNTHESIS.md, PROJECT.md, visual input | VISION.md, ALTERNATIVES.md | 3 |
+| `fire-roadmapper` | VISION.md (locked), REQUIREMENTS.md | ROADMAP.md | 4 |
+
+---
+
+## Completion
+
+```
++==============================================================================+
+| RESEARCH & VISION COMPLETE                                                   |
+|==============================================================================|
+|                                                                              |
+|  Project: {project_name}                                                     |
+|  Stack:   {locked stack from VISION.md}                                      |
+|  Phases:  {N} defined in ROADMAP.md                                          |
+|                                                                              |
+|  Created:                                                                    |
+|    [x] .planning/research/SYNTHESIS.md   <- merged research + GitHub refs    |
+|    [x] .planning/VISION.md               <- LOCKED architecture              |
+|    [x] .planning/research/ALTERNATIVES.md <- rejected branches               |
+|    [x] .planning/ROADMAP.md              <- phase breakdown                  |
+|                                                                              |
+|  Gates Triggered:                                                            |
+|    [?] Mode Gate        -> {forward/backward}                                |
+|    [?] Anti-Frankenstein -> {conflicts found / clean}                        |
+|    [?] Vision Architect -> {N} branches, Branch {X} selected                 |
+|    [?] Vision Lock      -> VISION.md marked LOCKED                           |
+|                                                                              |
+|==============================================================================|
+| NEXT UP                                                                      |
+|------------------------------------------------------------------------------|
+|                                                                              |
+|  -> Run /fire-1c-setup to install tooling and finalize initialization         |
+|                                                                              |
++==============================================================================+
+```
+
+---
+
+## Error Handling
+
+### Missing Prerequisites
+```
+╔══════════════════════════════════════════════════════════════════════════════╗
+║ ✗ ERROR: Run /fire-1a-new first                                               ║
+╠══════════════════════════════════════════════════════════════════════════════╣
+║  Missing: .planning/PROJECT.md or .planning/REQUIREMENTS.md                  ║
+║  These are created by /fire-1a-new. Run that command first.                   ║
+╚══════════════════════════════════════════════════════════════════════════════╝
+```
+
+---
+
+## References
+
+- **Agent:** `@agents/fire-project-researcher.md`
+- **Agent:** `@agents/fire-vision-architect.md`
+- **Agent:** `@agents/fire-roadmapper.md`
+- **Skill:** `@skills-library/_general/methodology/STACK_COMPATIBILITY_MATRIX.md`

package/commands/fire-1c-setup.md

@@ -0,0 +1,254 @@
+---
+description: Install tooling, create handoff, and finalize project initialization (Dominion Flow)
+---
+
+# /fire-1c-setup
+
+> Install CLI tools, create WARRIOR handoff, verify all files, show completion
+
+---
+
+## Purpose
+
+Finalize project initialization: install all CLI tools the locked stack requires, create the WARRIOR handoff, and verify every file exists. This is Step 3 of 3 in project initialization.
+
+**Flow:** `/fire-1a-new` → `/fire-1b-research` → **`/fire-1c-setup`**
+
+**Prerequisite:** `.planning/VISION.md` (locked) and `.planning/ROADMAP.md` must exist (created by `/fire-1b-research`).
+
+---
+
+## EXECUTION ORDER
+
+```
+STEP 1: Validate prerequisites     → VISION.md + ROADMAP.md exist
+STEP 2: WARRIOR Handoff Init       → create handoff file
+STEP 3: Zero-Friction Tooling      → install CLIs from VISION.md, write TOOLING-LOG.md
+STEP 4: SKILLS-INDEX.md            → create empty tracking file
+STEP 5: Update CONSCIENCE.md       → set status to "Ready to plan"
+STEP 6: MANDATORY FILE GATE        → verify ALL 16 files exist
+FINAL:  Completion Display          → show full project summary
+```
+
+**Complete each step before starting the next.**
+
+---
+
+## Step 1: Validate Prerequisites
+
+```bash
+test -f .planning/VISION.md && test -f .planning/ROADMAP.md && echo "READY" || echo "MISSING — run /fire-1b-research first"
+```
+
+If files are missing, stop and tell the user to run `/fire-1b-research` first.
+
+---
+
+## Step 2: WARRIOR Handoff Init
+
+**Create handoff directory if not exists:**
+```bash
+mkdir -p ~/.claude/warrior-handoffs/
+```
+
+**Create initial handoff file:**
+```
+~/.claude/warrior-handoffs/{PROJECT_NAME}_YYYY-MM-DD_init.md
+```
+
+Include: project name, core value, locked stack, phase count, current status, key decisions made, next steps.
+
+---
+
+## Step 3: Zero-Friction Tooling (MANDATORY)
+
+**Claude auto-installs ALL CLI tools the locked VISION.md stack requires.** The user should never manually install anything.
+
+**Read VISION.md and install everything the stack needs.**
+
+Reference: `@skills-library/_general/methodology/ZERO_FRICTION_CLI_SETUP.md`
+
+**Always install (every web project):**
+```bash
+npm install -D @playwright/test
+npx playwright install chromium firefox
+```
+
+> Playwright MCP is the primary visual testing tool for verification.
+
+**Install based on VISION.md stack:**
+
+| Stack Requirement | CLI Command |
+|------------------|-------------|
+| Supabase | `npx supabase init` then `npx supabase start` |
+| Stripe payments | `npm install stripe @stripe/stripe-js` |
+| Next.js | `npx create-next-app@latest` |
+| Prisma ORM | `npx prisma init` then `npx prisma generate` |
+| Drizzle ORM | `npm install drizzle-orm` + `npm install -D drizzle-kit` |
+| Tailwind CSS | `npm install -D tailwindcss @tailwindcss/vite` |
+| shadcn/ui | `npx shadcn@latest init` |
+| better-auth | `npx @better-auth/cli generate` |
+| Firebase | `npx firebase-tools init` |
+| Docker | `docker compose up -d` (if compose.yml exists) |
+| ESLint + Prettier | `npm install -D eslint prettier eslint-config-prettier` |
+| Husky (git hooks) | `npx husky init` |
+
+**Process:**
+1. Read locked VISION.md Technology Stack table
+2. Match each technology to its CLI setup command
+3. Run all installations sequentially (dependencies first)
+4. Verify each tool installed correctly (version check)
+5. Log installed tools to `.planning/TOOLING-LOG.md`
+
+**Skip conditions:**
+- Backend-only projects skip Playwright and frontend tools
+- User explicitly opts out of a specific tool
+- Tool already installed (check `package.json` or version command)
+
+---
+
+## Step 4: SKILLS-INDEX.md
+
+```markdown
+# Skills Applied to This Project
+
+## Summary
+- Total skills applied: 0
+- Categories used: 0
+- Last skill applied: N/A
+
+## By Phase
+*No phases executed yet*
+
+## By Category
+*Skills will be tracked here as they're applied during execution*
+
+## Quick Reference
+Run `/fire-search [query]` to find relevant skills.
+```
+
+---
+
+## Step 5: Update CONSCIENCE.md
+
+Update `.planning/CONSCIENCE.md`:
+- Status: `Ready to plan`
+- Phase count: from ROADMAP.md
+- Last Action: `Project initialized via /fire-1a-new → /fire-1b-research → /fire-1c-setup`
+
+---
+
+## Step 6: MANDATORY FILE GATE
+
+**Before showing completion, verify EVERY file exists. If ANY is missing, go back and create it.**
+
+```bash
+echo "=== FILE GATE CHECK ==="
+test -f .planning/PROJECT.md            || echo "MISSING: PROJECT.md"
+test -f .planning/REQUIREMENTS.md       || echo "MISSING: REQUIREMENTS.md"
+test -f .planning/CONSCIENCE.md         || echo "MISSING: CONSCIENCE.md"
+test -f .planning/SKILLS-INDEX.md       || echo "MISSING: SKILLS-INDEX.md"
+test -f .planning/research/SYNTHESIS.md || echo "MISSING: SYNTHESIS.md"
+test -f .planning/VISION.md             || echo "MISSING: VISION.md"
+test -f .planning/ROADMAP.md            || echo "MISSING: ROADMAP.md"
+test -f .planning/research/ALTERNATIVES.md || echo "MISSING: ALTERNATIVES.md"
+test -f .planning/TOOLING-LOG.md        || echo "MISSING: TOOLING-LOG.md"
+test -d .planning/breadcrumbs           || echo "MISSING: breadcrumbs/"
+test -d .planning/phases                || echo "MISSING: phases/"
+echo "=== GATE COMPLETE ==="
+```
+
+**If ANY file is missing, DO NOT show completion. Go back to the step that creates it — or tell the user which prior command to re-run.**
+
+---
+
+## DevTools Guide (Backward Mode Only)
+
+For users who were in backward mode (beginners), save a brief DevTools orientation to `.planning/DEVTOOLS-GUIDE.md`:
+
+```markdown
+## Quick DevTools Guide
+
+**Open DevTools:** F12 or Ctrl+Shift+I (Windows) / Cmd+Option+I (Mac)
+
+**3 tabs you'll use:**
+1. **Console** — errors show here (red = error, yellow = warning)
+2. **Network** — API calls (filter by Fetch/XHR)
+3. **Elements** — HTML/CSS inspector (click magnifier icon → click element)
+
+**Pro tip:** When something breaks, open Console, reproduce the error, screenshot the red text, share with Claude.
+```
+
+---
+
+## Completion Display
+
+**Show ONLY after file gate passes with zero missing files:**
+
+```
++==============================================================================+
+| PROJECT INITIALIZED                                                          |
+|==============================================================================|
+|                                                                              |
+|  Project: {project_name}                                                     |
+|  Stack:   {locked stack from VISION.md}                                      |
+|  Phases:  {phase_count} defined in ROADMAP.md                                |
+|  Status:  Ready to plan                                                      |
+|                                                                              |
+|  Core Files:                                                                 |
+|    [x] .planning/PROJECT.md              <- requirements                     |
+|    [x] .planning/REQUIREMENTS.md         <- REQ-IDs                          |
+|    [x] .planning/VISION.md               <- LOCKED                           |
+|    [x] .planning/ROADMAP.md              <- phase breakdown                  |
+|    [x] .planning/CONSCIENCE.md           <- project state                    |
+|                                                                              |
+|  Research:                                                                   |
+|    [x] .planning/research/SYNTHESIS.md   <- merged research + GitHub refs    |
+|    [x] .planning/research/ALTERNATIVES.md <- rejected branches               |
+|                                                                              |
+|  Memory:                                                                     |
+|    [x] .planning/breadcrumbs/            <- on-demand (agents create files   |
+|                                             when they record learnings)      |
+|                                                                              |
+|  Tooling:                                                                    |
+|    [x] .planning/TOOLING-LOG.md          <- installed CLIs                   |
+|    [x] WARRIOR handoff                   <- session continuity               |
+|                                                                              |
+|  Gates Triggered:                                                            |
+|    [?] Mode Gate        -> {forward/backward}                                |
+|    [?] Anti-Frankenstein -> {conflicts found / clean}                        |
+|    [?] Vision Architect -> {N} branches, Branch {X} selected                 |
+|    [?] Vision Lock      -> VISION.md marked LOCKED                           |
+|                                                                              |
+|==============================================================================|
+| NEXT UP                                                                      |
+|------------------------------------------------------------------------------|
+|                                                                              |
+|  -> Run /fire-2-plan 1 to create plans for Phase 1                           |
+|  -> Or run /fire-dashboard to view project status                            |
+|                                                                              |
++==============================================================================+
+```
+
+---
+
+## Error Handling
+
+### Missing Prerequisites
+```
+╔══════════════════════════════════════════════════════════════════════════════╗
+║ ✗ ERROR: Run /fire-1b-research first                                          ║
+╠══════════════════════════════════════════════════════════════════════════════╣
+║  Missing: .planning/VISION.md or .planning/ROADMAP.md                        ║
+║  These are created by /fire-1b-research. Run that command first.              ║
+╚══════════════════════════════════════════════════════════════════════════════╝
+```
+
+---
+
+## References
+
+- **Skill:** `@skills-library/_general/methodology/ZERO_FRICTION_CLI_SETUP.md`
+- **Protocol:** `@references/honesty-protocols.md` - WARRIOR honesty foundation
+- **Template:** `@templates/state.md` - CONSCIENCE.md template
+- **Template:** `@templates/skills-index.md` - Skills tracking template