fire-resurrect

/fire-resurrect

Burn the Frankenstein. Rise production-ready. Reverse-engineer INTENT from messy code, ask clarifying questions, then rebuild clean in a new folder.

---

Purpose

Take a messy "vibe coded" project and autonomously rebuild it into a clean, production-quality application. The source folder is never modified — the rebuild happens in a new target folder using the full Dominion Flow pipeline.

What makes this different from refactoring: Refactoring improves code incrementally. Resurrection Mode burns the old code entirely and rebuilds from extracted INTENT. The result carries the knowledge but none of the accidental complexity.

Reference: @skills-library/_general/methodology/PHOENIX_REBUILD_METHODOLOGY.md

Core pipeline:

AUTOPSY → DATABASE → INTENT → CLARIFY → VISION → REBUILD → COMPARISON

---

Arguments

arguments:
  --source:
    type: path
    required: true
    description: "Path to the messy source project"
    example: "/fire-resurrect --source C:/Projects/my-app"

  --target:
    type: path
    required: false
    default: "{source}-phoenix"
    description: "Path for the clean rebuild output"
    example: "/fire-resurrect --source ./app --target ./app-v2"

  --migrate:
    type: boolean
    default: false
    description: "Enable stack migration mode (propose alternative tech stacks)"

  --dry-run:
    type: boolean
    default: false
    description: "Run Phases 1-4 only (autopsy + database + intent + clarify). No rebuild."

  --focus:
    type: string
    required: false
    description: "Limit analysis to a specific subsystem"
    example: "/fire-resurrect --source ./app --focus auth"

  --db-strategy:
    type: string
    required: false
    default: "auto"
    description: "Database continuity strategy: 'auto' (detect best), 'reuse' (point to existing), 'clone' (dump+restore), 'fresh' (new empty DB with migrations only), 'skip' (no database)"
    example: "/fire-resurrect --source ./app --db-strategy clone"