# Phase 1: Iterative Specification Gathering
**Role:** Senior Product Architect (Reasoning Mode: ON)
**Gemini CLI Context:**
- This phase is an interactive dialogue between the User and Gemini CLI.
- Gemini CLI captures the final output into `spec.md`.

**Instruction:** Ask me one question at a time to develop a thorough, step-by-step technical specification for my idea. 
Each question must build on previous answers.  Do not stop until we have covered:
1. Core Value Prop
2. User Flow
3. Data Architecture
4. Boundary Conditions
5. Security & Auth
6. Deployment Target
**Constraint:** ONLY ONE QUESTION AT A TIME.
**The Idea:** [INSERT YOUR IDEA HERE]

# Phase 2: Implementation Blueprinting
**Context:** [PASTE FINALIZED SPEC HERE]
**Instruction:** Draft a detailed, step-by-step blueprint. Break the build into small, iterative chunks.
**Gemini CLI Automation:**
- Gemini CLI will execute these chunks directly.
- Cross-reference with `manifest.md` to ensure no redundant modules are created.

**For each chunk, you must provide:**
1. Goal & TDD Criteria
2. A specific coding prompt wrapped in ```text``` tags (or direct execution plan for Gemini CLI).
**Requirements:** Incremental progress, zero mocks, observability (logging), and no orphaned code.

# Phase 3: The Production Todo List
**Instruction:** Generate a `todo.md` checklist based on the blueprint.
**Gemini CLI Automation:**
- Gemini CLI will automatically maintain this file.
- When a task is completed and verified (tests pass), Gemini CLI must check the box `[x]`.
- Gemini CLI must cross-reference this list with `manifest.md` to ensure the "Active Modules" list is up to date.

**Format:**
- [ ] **Task:** [Feature Name]
    - **Verify:** Manual test steps.
    - **Automated:** Test file location.
    - **Vibe Check:** Edge case handling.

# Phase 4: The Architect's Audit
**Context:** [PASTE SPEC AND BLUEPRINT]
**Gemini CLI Automation:**
- Gemini CLI runs this audit automatically after the blueprint is drafted (Phase 2) and before execution starts.
- Issues found here must be resolved in `blueprint.md` before writing code.

**Instruction:** Act as a Red Team Architect. Identify:
1. Complexity Leaps
2. Silent Failures
3. Architectural Debt
4. Security Holes
**Output:** Provide "Vibe Corrections" for each.

# 📂 Project Manifest
**Gemini CLI Automation:**
- Gemini CLI acts as the custodian of this manifest.
- **State Registry:** Must be updated automatically after every successful feature implementation.
- **Model Log:** Log significant architectural decisions or pivots here.

## 🏗️ Metadata
- Status: [Current Status]
- Current Prompt: [X/Y]
- Tech Stack: [List]
## 🤖 Model Log
- [Phase]: [Model Name] -> [Notes]
## 🗺️ State Registry
- Entry Point: `main.py`
- Active Modules: [List]
- Debt: [List]

# 🌊 Vibecoding Production Workflow (SOP) with Gemini CLI

**Role:** Gemini CLI acts as the Lead Engineer and Project Manager.

1. **Initialization:**
   - Gemini CLI assesses the current directory.
   - If starting fresh, Gemini CLI sets up the environment structure automatically (replacing the old Phase 0).
   - Reads `manifest.md` to establish context.

2. **Extraction (Phase 1):**
   - Gemini CLI engages the user in an iterative interview using `01_spec_generator.md` to build `spec.md`.

3. **Architecting (Phase 2 & 4):**
   - Gemini CLI drafts `blueprint.md` based on `02_blueprint_builder.md`.
   - Gemini CLI self-audits the blueprint using `04_vibe_audit.md` before execution.

4. **Execution:**
   - Gemini CLI implements features step-by-step.
   - **Critical:** Gemini CLI creates/updates `todo.md` (`03_todo_checklist.md`) and actively checks off items `[x]` as they pass verification.

5. **Verification & Documentation:**
   - Run tests.
   - Update `manifest.md` with new modules and debt.
   - Await next user instruction.