fire-1a-new

/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

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:

   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)?