fire-2-plan

/fire-2-plan

Plan phase N with skills library integration and WARRIOR validation

---

Purpose

Create detailed execution plans for a specified phase by combining Dominion Flow's structured planning with skills library access, honesty protocols, and validation requirements. Plans are reviewed by a plan-checker before approval.

---

Arguments

arguments:
  phase_number:
    required: true
    type: integer
    description: "Phase number to plan (e.g., 1, 2, 3)"
    example: "/fire-2-plan 3"

optional_flags:
  --gaps: "Plan only for gaps identified in verification"
  --research-first: "Force research phase before planning"
  --skip-checker: "Skip plan-checker validation (not recommended)"

---

Process

Step 0.5: Prompt Enhancer — Codebase Convention Scan (v11.0)

conventions BEFORE planning enriches the planner's context with actual patterns, reducing hallucinated approaches and increasing plan accuracy.

Before any validation or planning, scan the project for conventions that should inform the planner:

SCAN (quick — max 60 seconds):

1. Package manager: check for bun.lockb / pnpm-lock.yaml / yarn.lock / package-lock.json
2. Test framework: grep for jest.config / vitest.config / playwright.config / .mocharc
3. Naming patterns: sample 3 source files — camelCase vs snake_case, barrel exports
4. Error handling: grep for common error patterns (try/catch, .catch, Result types)
5. API style: check for REST routes / GraphQL schema / tRPC routers
6. State management: grep for zustand / redux / context / signals

OUTPUT — codebase_conventions block injected into planner context:

<codebase_conventions>
  package_manager: {bun | pnpm | yarn | npm}
  test_framework: {jest | vitest | playwright | none detected}
  naming: {camelCase | snake_case | mixed}
  error_pattern: {try-catch | Result type | .catch chains}
  api_style: {REST | GraphQL | tRPC | mixed}
  state: {zustand | redux | context | none detected}
  notes: [any other conventions discovered]
</codebase_conventions>