ai-flow-dev 1.4.0 → 2.0.1

package/prompts/backend/{flow-bootstrap-phase-9.md → flow-build-phase-9.md}

@@ -265,16 +265,16 @@ Story Points | Complexity | Typical Time | Examples
 
 **Use this table to add time estimates to each task:**
 
-| Story Points | Time Estimate (solo dev) | Time Range | Example Task                               |
-| ------------ | ------------------------ | ---------- | ------------------------------------------ |
-| **1 SP**     | 1-2 hours                | (~1-2h)    | Add enum value, simple config change       |
-| **2 SP**     | 3-4 hours                | (~3-4h)    | Write 5-8 unit tests, basic validation     |
-| **3 SP**     | 4-8 hours                | (~4-8h)    | Simple CRUD endpoint, basic entity         |
-| **5 SP**     | 1-2 days                 | (~1-2d)    | Complex endpoint with business logic       |
-| **8 SP**     | 2-3 days                 | (~2-3d)    | Auth flow, complex validation              |
-| **13 SP**    | 1 week                   | (~1w)      | Complete module with full test coverage    |
-| **21 SP**    | 2 weeks                  | (~2w)      | Major feature with integration             |
-| **34 SP**    | 3 weeks                  | (~3w)      | Multiple related features (Epic-level)     |
+| Story Points | Time Estimate (solo dev) | Time Range | Example Task                            |
+| ------------ | ------------------------ | ---------- | --------------------------------------- |
+| **1 SP**     | 1-2 hours                | (~1-2h)    | Add enum value, simple config change    |
+| **2 SP**     | 3-4 hours                | (~3-4h)    | Write 5-8 unit tests, basic validation  |
+| **3 SP**     | 4-8 hours                | (~4-8h)    | Simple CRUD endpoint, basic entity      |
+| **5 SP**     | 1-2 days                 | (~1-2d)    | Complex endpoint with business logic    |
+| **8 SP**     | 2-3 days                 | (~2-3d)    | Auth flow, complex validation           |
+| **13 SP**    | 1 week                   | (~1w)      | Complete module with full test coverage |
+| **21 SP**    | 2 weeks                  | (~2w)      | Major feature with integration          |
+| **34 SP**    | 3 weeks                  | (~3w)      | Multiple related features (Epic-level)  |
 
 > **Note:** Time assumes AI-assisted development (GitHub Copilot, Claude, etc.). Without AI assistance, multiply time estimates by 2-3x.
 >
@@ -320,11 +320,13 @@ Story Points | Complexity | Typical Time | Examples
 **Parallelization Rules ([P] marker):**
 
 ✅ **Use [P] when:**
+
 - Tasks target different files
 - No shared dependencies between tasks
 - Can run simultaneously (e.g., independent entities, different modules)
 
 ❌ **Don't use [P] when:**
+
 - Task depends on another incomplete task
 - Same file is modified by multiple tasks
 - Shared resource (DB migration, config file, shared service)
@@ -356,95 +358,89 @@ For each Epic:
 
 **Feature Template:**
 
+```markdown
+### Feature {{NUMBER}}: {{FEATURE_NAME}} • {{SP}} SP (~{{TIME}})
+
+**Scope:** {{ENTITY}} entity + {{ENDPOINT_COUNT}} endpoints + {{TEST_COUNT}} tests
+
+**Tasks:**
+
+- [ ] T0XX [P] Write {{ENTITY}} entity tests • 2 SP (~3-4h) → tests/unit/{{ENTITY}}.spec.ts
+- [ ] T0YY Create {{ENTITY}} entity • 2 SP (~3-4h) → src/entities/{{ENTITY}}.ts
+- [ ] T0ZZ Create I{{REPOSITORY}} interface • 1 SP (~1-2h) → src/repositories/I{{REPOSITORY}}.ts
+- [ ] T0AA Implement {{REPOSITORY}} • 2 SP (~3-4h) → src/repositories/{{REPOSITORY}}.ts (after T0YY, T0ZZ)
+- [ ] T0BB Implement {{SERVICE}} business logic • 3 SP (~4-8h) → src/services/{{SERVICE}}.ts (after T0AA)
+- [ ] T0CC Create {{CONTROLLER}} endpoints • 2 SP (~3-4h) → src/controllers/{{CONTROLLER}}.ts (after T0BB)
+- [ ] T0DD [P] Write integration tests • 2 SP (~3-4h) → tests/integration/{{CONTROLLER}}.spec.ts
+- [ ] T0EE [P] Update API docs • 1 SP (~1h) → docs/api.md
+
+**Parallel:** T0XX, T0DD, T0EE can run together
+
+**Done when:** All endpoints work + tests pass + coverage ≥ {{COVERAGE}}%
+
+**Start:** `/feature new "{{FEATURE_NAME}}"`
+```
+
+`````
+
+**Example (Real Project):**
+
 ````markdown
-### Feature {{NUMBER}}: {{FEATURE_NAME}} • {{SP}} SP
+### Feature 2.1: User Entity & Repository • 12 SP (~2-3d)
 
-⏱️ **Est. Time:** {{TIME_RANGE}}
-🎯 **Priority:** {{PRIORITY}}
-📋 **Dependencies:** {{DEPENDENCIES}}
+**Scope:** User entity + CRUD endpoints + 12 tests
 
-**Scope:**
+**Tasks:**
 
-- {{ENDPOINT_1}} ({{METHOD}})
-- {{ENDPOINT_2}} ({{METHOD}})
-- Entity: {{ENTITY_NAME}}
-- Tests: {{TEST_COUNT}} ({{TEST_TYPES}})
+- [ ] T001 [P] Write User entity validation tests • 2 SP (~3-4h) → tests/unit/User.entity.spec.ts
+- [ ] T002 Create User entity (email, password, role) • 2 SP (~3-4h) → src/entities/User.entity.ts
+- [ ] T003 Create IUserRepository interface • 1 SP (~1-2h) → src/repositories/IUserRepository.ts
+- [ ] T004 Implement UserRepository with Prisma • 2 SP (~3-4h) → src/repositories/UserRepository.ts (after T002, T003)
+- [ ] T005 Implement UserService business logic • 3 SP (~4-8h) → src/services/UserService.ts (after T004)
+- [ ] T006 Create UserController (CRUD endpoints) • 2 SP (~3-4h) → src/controllers/UserController.ts (after T005)
+- [ ] T007 [P] Write integration tests (4 tests) • 2 SP (~3-4h) → tests/integration/UserController.spec.ts
+- [ ] T008 [P] Update API docs • 1 SP (~1h) → docs/api.md
 
-**Tasks:** (Test-First ordering, execution sequence, hybrid estimation)
+**Parallel tasks:** T001, T007, T008 (different files)
 
-- [ ] [T0XX] [P] Write unit tests for {{ENTITY}} entity validation ({{COUNT}} tests) • {{SP}} SP (~{{TIME}})
-      File: tests/unit/entities/{{ENTITY}}.entity.spec.ts
-      Tests: {{TEST_SCENARIOS}}
-      Dependencies: None (can run parallel with other test tasks)
+**Done when:** GET/POST/PUT/DELETE /users working + 12 tests pass + coverage ≥ 80%
+`````
 
-- [ ] [T0YY] Create {{ENTITY}} entity with validation • {{SP}} SP (~{{TIME}})
-      File: src/entities/{{ENTITY}}.entity.ts
-      Implements: {{VALIDATION_RULES}}
-      Dependencies: None
+---
 
-- [ ] [T0ZZ] Create I{{REPOSITORY}} interface • {{SP}} SP (~{{TIME}})
-      File: src/repositories/interfaces/I{{REPOSITORY}}.ts
-      Methods: {{REPOSITORY_METHODS}}
-      Dependencies: T0YY (needs {{ENTITY}} entity type)
-
-- [ ] [T0AA] Implement {{REPOSITORY}} with {{ORM}} • {{SP}} SP (~{{TIME}})
-      File: src/repositories/{{REPOSITORY}}.ts
-      Implements: All CRUD methods from I{{REPOSITORY}} interface
-      Dependencies: T0YY (entity), T0ZZ (interface)
-
-- [ ] [T0BB] Implement {{SERVICE}} service with business logic • {{SP}} SP (~{{TIME}})
-      File: src/services/{{SERVICE}}.service.ts
-      Business Logic: {{SERVICE_LOGIC}}
-      Dependencies: T0AA (repository)
-
-- [ ] [T0CC] Create {{CONTROLLER}} controller • {{SP}} SP (~{{TIME}})
-      File: src/controllers/{{CONTROLLER}}.controller.ts
-      Endpoints: {{ENDPOINT_1}}, {{ENDPOINT_2}}
-      Dependencies: T0BB (service)
-
-- [ ] [T0DD] Write unit tests for {{SERVICE}} service ({{COUNT}} tests) • {{SP}} SP (~{{TIME}})
-      File: tests/unit/services/{{SERVICE}}.service.spec.ts
-      Tests: {{SERVICE_TEST_SCENARIOS}}
-      Dependencies: T0BB (service implementation)
-
-- [ ] [T0EE] Write integration tests for {{ENDPOINT_1}}, {{ENDPOINT_2}} ({{COUNT}} tests) • {{SP}} SP (~{{TIME}})
-      File: tests/integration/controllers/{{CONTROLLER}}.spec.ts
-      Tests: {{INTEGRATION_TEST_SCENARIOS}}
-      Dependencies: T0CC (controller)
-
-- [ ] [T0FF] Update API documentation • {{SP}} SP (~{{TIME}})
-      File: docs/api.md
-      Add: {{ENDPOINT_1}}, {{ENDPOINT_2}} with request/response schemas
-      Dependencies: T0CC (endpoints implemented)
-
-- [ ] [T0GG] Update data model documentation • {{SP}} SP (~{{TIME}})
-      File: docs/data-model.md
-      Add: {{ENTITY}} schema, relationships, validation rules
-      Dependencies: T0YY (entity complete)
+**Example (Simplified Format):**
 
-**Acceptance Criteria:**
+```markdown
+### Feature 2.1: User Entity & Repository • 12 SP (~2-3d)
 
-- [ ] All endpoints return correct responses
-- [ ] {{VALIDATION_RULES}} are enforced
-- [ ] Test coverage ≥ {{COVERAGE_TARGET}}%
-- [ ] API documentation is updated
-- [ ] Code passes linting and type-check
+**Scope:** User entity + CRUD endpoints + 12 tests
 
-**Ready-to-execute command:**
+**Tasks:**
 
-```bash
-/feature new "{{FEATURE_NAME}}"
+- [ ] T001 [P] Write User entity validation tests • 2 SP (~3-4h) → tests/unit/User.entity.spec.ts
+- [ ] T002 Create User entity (email, password, role) • 2 SP (~3-4h) → src/entities/User.entity.ts
+- [ ] T003 Create IUserRepository interface • 1 SP (~1-2h) → src/repositories/IUserRepository.ts
+- [ ] T004 Implement UserRepository with Prisma • 2 SP (~3-4h) → src/repositories/UserRepository.ts (after T002, T003)
+- [ ] T005 Implement UserService business logic • 3 SP (~4-8h) → src/services/UserService.ts (after T004)
+- [ ] T006 Create UserController (CRUD endpoints) • 2 SP (~3-4h) → src/controllers/UserController.ts (after T005)
+- [ ] T007 [P] Write integration tests (4 tests) • 2 SP (~3-4h) → tests/integration/UserController.spec.ts
+- [ ] T008 [P] Update API docs • 1 SP (~1h) → docs/api.md
+
+**Parallel tasks:** T001, T007, T008 (different files)
+
+**Done when:** GET/POST/PUT/DELETE /users working + 12 tests pass + coverage ≥ 80%
+
+**Start:** `/feature new "User Entity & Repository"`
 ```
-````
 
-````
+---
 
-**Example Feature Breakdown:**
+**Original Feature Breakdown Example:**
 
 ```markdown
 ## 💾 Epic 2: Data Layer • 34 SP
 
-### Feature 2.1: User Entity & Repository • 5 SP
+### Feature 2.1: User Entity & Repository (Detailed Version) • 5 SP
 
 ⏱️ **Est. Time:** 1-2 days (~12-16h total)
 🎯 **Priority:** P0
@@ -452,6 +448,7 @@ For each Epic:
 🏷️ **User Story:** [US1] As a system, I need to store user data securely
 
 **Scope:**
+
 - Entity: User (id, email, username, passwordHash, role, createdAt, updatedAt)
 - Repository: IUserRepository with CRUD operations
 - Validation: Email format, username constraints, password strength
@@ -505,15 +502,16 @@ For each Epic:
 - [ ] All 12 tests passing (8 unit + 4 integration)
 
 **Task Execution Graph:**
-
 ```
+
 T001 [P] ──┐
-           ├──> T002 ──┬──> T003 ──> T004 ──┬──> T006
-           │           │                     │
-           │           └──> T005 ────────────┘
-           │                                 │
-           └─────────────────────────────────┴──> T007
-```
+├──> T002 ──┬──> T003 ──> T004 ──┬──> T006
+│ │ │
+│ └──> T005 ────────────┘
+│ │
+└─────────────────────────────────┴──> T007
+
+````
 
 **Parallelization Notes:**
 - T001 can run parallel to other test tasks (different file)
@@ -798,14 +796,14 @@ With 3 developers: ~9 weeks (47% time savings)
 
 ### Step 9.5: Generate Roadmap Document (2-5 minutes - automatic)
 
-**Generate `.ai-flow/roadmap.md` with complete implementation plan:**
+**Generate `roadmap.md` with complete implementation plan:**
 
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 📝 Step 9.5/6: Generating Roadmap Document
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
-Writing to .ai-flow/roadmap.md...
+Writing to roadmap.md...
 ```
 
 **Roadmap Document Structure:**
@@ -1156,7 +1154,7 @@ Update this roadmap as you complete features:
 
 **Need to modify the roadmap?**
 
-- Update documentation first (`/flow-bootstrap` or `/flow-docs-sync`)
+- Update documentation first (`/flow-build` or `/flow-docs-sync`)
 - Re-run Phase 9 to regenerate roadmap
 
 ---
@@ -1169,7 +1167,7 @@ Update this roadmap as you complete features:
 
 ```
 ✅ Roadmap document generated
-✅ Location: .ai-flow/roadmap.md
+✅ Location: roadmap.md
 ✅ Total: {{TOTAL_EPICS}} Epics, {{TOTAL_FEATURES}} Features, {{TOTAL_TASKS}} Tasks
 ✅ Estimated: {{TOTAL_SP}} Story Points (~{{TOTAL_WEEKS}} weeks)
 ```
@@ -1194,7 +1192,7 @@ Update this roadmap as you complete features:
 ✅ Estimated time: {{SOLO_WEEKS}} weeks (1 dev) | {{TWO_DEV_WEEKS}} weeks (2 devs)
 ✅ Dependency graph: Generated
 ✅ Execution order: Optimized for parallelization
-✅ Roadmap document: .ai-flow/roadmap.md
+✅ Roadmap document: roadmap.md
 
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 🎯 What This Roadmap Guarantees
@@ -1223,14 +1221,14 @@ Update this roadmap as you complete features:
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 1. **Open the roadmap**
-   └─ Open .ai-flow/roadmap.md in your editor
+   └─ Open roadmap.md in your editor
 
 2. **Review and adjust priorities**
    └─ Decide which features are MVP vs future phases
    └─ Adjust P0/P1/P2/P3 priorities if needed
 
 3. **Commit the roadmap**
-   └─ git add .ai-flow/roadmap.md
+   └─ git add roadmap.md
    └─ git commit -m "docs: add implementation roadmap with Story Points"
 
 4. **Start implementation**
@@ -1262,13 +1260,13 @@ Update this roadmap as you complete features:
   time-to-market.
 
 • **Re-generate:** If documentation changes significantly, run
-  /flow-bootstrap again (Phases 0-9) to update everything.
+  /flow-build again (Phases 0-9) to update everything.
 
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 Ready to start building? 🚀
 
-Open .ai-flow/roadmap.md and let's ship this! 💪
+Open roadmap.md and let's ship this! 💪
 
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 ```
@@ -1282,10 +1280,10 @@ A) ✅ Start implementing first feature now (recommended)
    → Will execute: /feature new "{{FIRST_FEATURE_NAME}}"
 
 B) 📋 Review roadmap first
-   → Will open .ai-flow/roadmap.md
+   → Will open roadmap.md
 
 C) ✏️ Customize roadmap
-   → Will open .ai-flow/roadmap.md for editing
+   → Will open roadmap.md for editing
 
 Your choice (A/B/C): __
 ```
@@ -1404,7 +1402,7 @@ Please fix documentation and re-run Phase 9
 
 **9.5 Generate Roadmap Document:**
 
-- [ ] Create `.ai-flow/roadmap.md`
+- [ ] Create `roadmap.md`
 - [ ] Include project overview
 - [ ] Include Story Points reference table
 - [ ] Include Epic overview table

package/prompts/backend/{flow-bootstrap.md → flow-build.md}

@@ -4,6 +4,83 @@
 
 Your mission is to guide the user through creating **comprehensive, production-ready documentation** for their backend project through an interactive questionnaire that follows the dependency-aware order specified below.
 
+---
+
+## 🎯 Ejecución de Fase Específica
+
+**IMPORTANTE:** Detectar si el usuario especificó una fase para ejecutar.
+
+### Detectar Argumento de Fase
+
+Buscar en el mensaje del usuario patrones como:
+
+- "fase 0", "fase 1", "fase 2", ..., "fase 9"
+- "phase 0", "phase 1", etc.
+- "ejecutar fase N"
+- "run phase N"
+
+### Comportamiento
+
+**Si se detecta "fase N" (donde N = 0-9):**
+
+1. **Validar que la fase existe para backend:**
+   - Fase 0: Context Discovery (opcional, solo proyectos existentes)
+   - Fase 1: Discovery & Business
+   - Fase 2: Data Architecture
+   - Fase 3: System Architecture
+   - Fase 4: Security & Authentication
+   - Fase 5: Code Standards
+   - Fase 6: Testing Strategy
+   - Fase 7: Operations & Deployment
+   - Fase 8: Project Setup & Final Documentation
+   - Fase 9: Implementation Roadmap (opcional)
+
+2. **Si la fase es válida:**
+   - Leer el archivo: `.ai-flow/prompts/backend/flow-build-phase-N.md`
+   - Ejecutar SOLO esa fase
+   - NO continuar con otras fases
+   - Al finalizar, informar al usuario que puede continuar con la siguiente fase usando `/flow-build fase N+1`
+
+3. **Si la fase es inválida:**
+   - Mostrar mensaje de error amigable
+   - Listar las fases válidas (0-9) con descripción de una línea
+
+**Si NO se detecta "fase N":**
+
+- Ejecutar el flujo completo normal (todas las fases en orden)
+- Comenzar con Mode Selection (Interactive vs Smart Auto-Suggest)
+- Continuar con Scope Selection (MVP/Production-Ready/Enterprise)
+- Ejecutar Phases 0-9 según corresponda
+
+### Ejemplo de Lista de Fases Válidas
+
+Si el usuario especifica una fase inválida, mostrar:
+
+```
+❌ Fase inválida. Las fases válidas para backend son:
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+📋 Fases Disponibles - Backend
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+  /flow-build fase 0  - Context Discovery (solo proyectos existentes)
+  /flow-build fase 1  - Discovery & Business (problema, usuarios, objetivos)
+  /flow-build fase 2  - Data Architecture (entidades, relaciones, database)
+  /flow-build fase 3  - System Architecture (tech stack, patrones, APIs)
+  /flow-build fase 4  - Security & Authentication (auth, autorización, compliance)
+  /flow-build fase 5  - Code Standards (convenciones, formato, git workflow)
+  /flow-build fase 6  - Testing Strategy (tipos de tests, coverage, CI)
+  /flow-build fase 7  - Operations & Deployment (deployment, monitoreo, logging)
+  /flow-build fase 8  - Project Setup & Final Documentation (inicializar proyecto)
+  /flow-build fase 9  - Implementation Roadmap (plan con Story Points - opcional)
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+💡 Tip: Usa /flow-build sin argumentos para ejecutar todas las fases en orden.
+```
+
+---
+
 ## Important Instructions
 
 1. **Ask for Questionnaire Mode FIRST** - Before anything else, ask the user to select: Interactive Mode or Smart Auto-Suggest Mode (see "Mode Selection" section below)
@@ -87,24 +164,19 @@ Ask these 6 questions one by one with progress indicator:
 **Critical Questions:**
 
 1. **Project Name & Description** (if new project - skip if Phase 0 detected)
-
    - What is the project name?
    - Provide a short description (1 sentence)
 
 2. **Project Overview**
-
    - What problem does this backend system solve? (2-3 sentences)
 
 3. **Business Objectives**
-
    - What are the top 3 measurable objectives for this project?
 
 4. **System Type** (Critical for auto-suggestions)
-
    - What type of system are you building?
 
    **Options:**
-
    - A) E-commerce (Product catalog, cart, checkout)
    - B) SaaS (Multi-tenant, subscriptions, RBAC)
    - C) CRM (Contacts, leads, sales pipeline)
@@ -117,7 +189,6 @@ Ask these 6 questions one by one with progress indicator:
    - J) Other (will use generic defaults)
 
 5. **Core Data Entities** (if new project - skip if Phase 0 detected)
-
    - List the main entities/models your system needs (e.g., User, Product, Order)
 
 6. **Backend Framework** (if new project - skip if Phase 0 detected)
@@ -299,26 +370,26 @@ Generate all 17 documents using the confirmed values (either AI-suggested or use
 
 This documentation is **modularized** for better maintainability and performance. Each phase is in a separate file.
 
-### For Complete Bootstrap (All Phases)
+### For Complete Build (All Phases)
 
 Execute phases sequentially by reading each file in order:
 
-1. **Phase 0 (Optional - Existing Projects Only):** Read `.ai-flow/prompts/backend/flow-bootstrap-phase-0-context.md`
-2. **Phase 1 (Discovery & Business):** Read `.ai-flow/prompts/backend/flow-bootstrap-phase-1-business.md`
-3. **Phase 2 (Data Architecture):** Read `.ai-flow/prompts/backend/flow-bootstrap-phase-2-data.md`
-4. **Phase 3 (System Architecture):** Read `.ai-flow/prompts/backend/flow-bootstrap-phase-3-architecture.md`
-5. **Phase 4 (Security & Authentication):** Read `.ai-flow/prompts/backend/flow-bootstrap-phase-4-security.md`
-6. **Phase 5 (Code Standards):** Read `.ai-flow/prompts/backend/flow-bootstrap-phase-5-standards.md`
-7. **Phase 6 (Testing Strategy):** Read `.ai-flow/prompts/backend/flow-bootstrap-phase-6-testing.md`
-8. **Phase 7 (Operations & Deployment):** Read `.ai-flow/prompts/backend/flow-bootstrap-phase-7-operations.md`
-9. **Phase 8 (Project Setup & Final Documentation):** Read `.ai-flow/prompts/backend/flow-bootstrap-phase-8.md`
+1. **Phase 0 (Optional - Existing Projects Only):** Read `.ai-flow/prompts/backend/flow-build-phase-0-context.md`
+2. **Phase 1 (Discovery & Business):** Read `.ai-flow/prompts/backend/flow-build-phase-1-business.md`
+3. **Phase 2 (Data Architecture):** Read `.ai-flow/prompts/backend/flow-build-phase-2-data.md`
+4. **Phase 3 (System Architecture):** Read `.ai-flow/prompts/backend/flow-build-phase-3-architecture.md`
+5. **Phase 4 (Security & Authentication):** Read `.ai-flow/prompts/backend/flow-build-phase-4-security.md`
+6. **Phase 5 (Code Standards):** Read `.ai-flow/prompts/backend/flow-build-phase-5-standards.md`
+7. **Phase 6 (Testing Strategy):** Read `.ai-flow/prompts/backend/flow-build-phase-6-testing.md`
+8. **Phase 7 (Operations & Deployment):** Read `.ai-flow/prompts/backend/flow-build-phase-7-operations.md`
+9. **Phase 8 (Project Setup & Final Documentation):** Read `.ai-flow/prompts/backend/flow-build-phase-8.md`
 
 ### For Individual Phases
 
 You can execute any phase independently by reading its file. For example:
 
 ```
-Read .ai-flow/prompts/backend/flow-bootstrap-phase-4-security.md and execute only Phase 4
+Read .ai-flow/prompts/backend/flow-build-phase-4-security.md and execute only Phase 4
 ```
 
 ---
@@ -327,7 +398,7 @@ Read .ai-flow/prompts/backend/flow-bootstrap-phase-4-security.md and execute onl
 
 ### Phase 0: Context Discovery (Optional)
 
-**File:** `backend/flow-bootstrap-phase-0-context.md`
+**File:** `backend/flow-build-phase-0-context.md`
 **For:** Existing projects with code/documentation
 **Duration:** 1-5 minutes (automated analysis)
 **Output:** Pre-populated answers, project analysis
@@ -347,7 +418,7 @@ Read .ai-flow/prompts/backend/flow-bootstrap-phase-4-security.md and execute onl
 
 ### Phase 1: Discovery & Business
 
-**File:** `backend/flow-bootstrap-phase-1-business.md`
+**File:** `backend/flow-build-phase-1-business.md`
 **Duration:** 15-20 minutes
 **Key Questions:**
 
@@ -365,7 +436,7 @@ Read .ai-flow/prompts/backend/flow-bootstrap-phase-4-security.md and execute onl
 
 ### Phase 2: Data Architecture
 
-**File:** `backend/flow-bootstrap-phase-2-data.md`
+**File:** `backend/flow-build-phase-2-data.md`
 **Duration:** 15-20 minutes
 **Key Questions:**
 
@@ -383,7 +454,7 @@ Read .ai-flow/prompts/backend/flow-bootstrap-phase-4-security.md and execute onl
 
 ### Phase 3: System Architecture
 
-**File:** `backend/flow-bootstrap-phase-3-architecture.md`
+**File:** `backend/flow-build-phase-3-architecture.md`
 **Duration:** 15-20 minutes
 **Key Questions:**
 
@@ -403,7 +474,7 @@ Read .ai-flow/prompts/backend/flow-bootstrap-phase-4-security.md and execute onl
 
 ### Phase 4: Security & Authentication
 
-**File:** `backend/flow-bootstrap-phase-4-security.md`
+**File:** `backend/flow-build-phase-4-security.md`
 **Duration:** 15-20 minutes
 **Key Questions:**
 
@@ -421,7 +492,7 @@ Read .ai-flow/prompts/backend/flow-bootstrap-phase-4-security.md and execute onl
 
 ### Phase 5: Code Standards
 
-**File:** `backend/flow-bootstrap-phase-5-standards.md`
+**File:** `backend/flow-build-phase-5-standards.md`
 **Duration:** 15-20 minutes
 **Key Questions:**
 
@@ -439,7 +510,7 @@ Read .ai-flow/prompts/backend/flow-bootstrap-phase-4-security.md and execute onl
 
 ### Phase 6: Testing Strategy
 
-**File:** `backend/flow-bootstrap-phase-6-testing.md`
+**File:** `backend/flow-build-phase-6-testing.md`
 **Duration:** 15-25 minutes
 **Key Questions:**
 
@@ -457,7 +528,7 @@ Read .ai-flow/prompts/backend/flow-bootstrap-phase-4-security.md and execute onl
 
 ### Phase 7: Operations & Deployment
 
-**File:** `backend/flow-bootstrap-phase-7-operations.md`
+**File:** `backend/flow-build-phase-7-operations.md`
 **Duration:** 10 minutes
 **Key Questions:**
 
@@ -478,7 +549,7 @@ Read .ai-flow/prompts/backend/flow-bootstrap-phase-4-security.md and execute onl
 
 ### Phase 8: Project Setup & Final Documentation
 
-**File:** `backend/flow-bootstrap-phase-8.md`
+**File:** `backend/flow-build-phase-8.md`
 **Duration:** 10-15 minutes
 **Key Steps:**
 
@@ -503,7 +574,7 @@ Read .ai-flow/prompts/backend/flow-bootstrap-phase-4-security.md and execute onl
 
 ### Phase 9: Implementation Roadmap (Optional)
 
-**File:** `backend/flow-bootstrap-phase-9.md`
+**File:** `backend/flow-build-phase-9.md`
 **Duration:** 15-30 minutes
 **Key Steps:**
 
@@ -545,7 +616,7 @@ Read .ai-flow/prompts/backend/flow-bootstrap-phase-4-security.md and execute onl
 **Command:**
 
 ```
-Read .ai-flow/prompts/backend/flow-bootstrap-phase-1-business.md and execute Phase 1
+Read .ai-flow/prompts/backend/flow-build-phase-1-business.md and execute Phase 1
 ```
 
 ---
@@ -567,7 +638,7 @@ Read .ai-flow/prompts/backend/flow-bootstrap-phase-1-business.md and execute Pha
 **Command:**
 
 ```
-Read .ai-flow/prompts/backend/flow-bootstrap-phase-0-context.md and execute Phase 0
+Read .ai-flow/prompts/backend/flow-build-phase-0-context.md and execute Phase 0
 ```
 
 ---
@@ -638,7 +709,7 @@ Before starting Phase 1, you'll select a scope level:
 2. Customize as needed for your specific project
 3. Share `AGENT.md` with your team
 4. Update documents as your project evolves
-5. Use `/bootstrap-phase[N]` commands to regenerate individual sections
+5. Use `/flow-build-phase-[N]` commands to regenerate individual sections
 
 ---
 
@@ -703,8 +774,8 @@ As your project evolves, your documentation may become out of sync with your cod
 2. **Then:**
    - 🆕 **New Project + Mode A:** Execute all phases sequentially, ask all questions
    - 🆕 **New Project + Mode B:** Ask 6 critical questions, auto-suggest the rest, show summary
-   - 📁 **Existing Project + Mode A:** Read `flow-bootstrap-phase-0-context.md` first, then proceed with all phases
-   - 📁 **Existing Project + Mode B:** Read `flow-bootstrap-phase-0-context.md` first, then ask remaining critical questions
+   - 📁 **Existing Project + Mode A:** Read `flow-build-phase-0-context.md` first, then proceed with all phases
+   - 📁 **Existing Project + Mode B:** Read `flow-build-phase-0-context.md` first, then ask remaining critical questions
    - 🔄 **Update Docs:** Use `/flow-docs-sync` command
 
 ---
@@ -819,7 +890,7 @@ git add .ai-flow/
 # Create initial commit with documentation metadata
 git commit -m "docs: initial project documentation
 
-Generated by AI Flow /flow-bootstrap command:
+Generated by AI Flow /flow-build command:
 - 17 documentation files (backend)
 - Architecture: {{ARCHITECTURE_PATTERN}}
 - Tech stack: {{FRAMEWORK}}, {{DATABASE}}, {{ORM}}
@@ -866,7 +937,7 @@ Your choice (A): __
 
 1. Review documentation in .ai-flow/templates/
 2. When ready, run Phase 8:
-   → Read .ai-flow/prompts/backend/flow-bootstrap-phase-8.md
+   → Read .ai-flow/prompts/backend/flow-build-phase-8.md
    → Detects project state, initializes framework (optional), generates final docs
 3. (Optional) Continue to Phase 9: Implementation Roadmap (15-30 min)
    → Generates complete implementation plan with Story Points

package/prompts/backend/flow-docs-sync.md

@@ -464,7 +464,7 @@ Actualización cancelada. Ejecuta `/flow-docs-sync` cuando estés listo para act
 2. **Follow Existing Patterns:**
 
    - Use same format as existing documentation
-   - Follow conventions established in original bootstrap
+   - Follow conventions established in original build
    - Maintain consistency with existing docs
 
 3. **Update Analysis File:**
@@ -524,3 +524,4 @@ Documentación sincronizada exitosamente.
 
 **BEGIN EXECUTION when user runs `/flow-docs-sync`**
 
+

package/prompts/frontend/{flow-bootstrap-phase-0.md → flow-build-phase-0.md}

@@ -2,7 +2,7 @@
 
 **⚡ AUTOMATED ANALYSIS - Minimal User Input Required**
 
-This phase automatically analyzes your existing frontend codebase to pre-populate answers for the bootstrap questionnaire.
+This phase automatically analyzes your existing frontend codebase to pre-populate answers for the build questionnaire.
 
 ---
 
@@ -483,7 +483,7 @@ After Phase 0 completes:
 
 Next: Proceed to Phase 1 (Discovery & UX)
 
-Read: .ai-flow/prompts/frontend/flow-bootstrap-phase-1-discovery.md
+Read: .ai-flow/prompts/frontend/flow-build-phase-1-discovery.md
 ```
 
 ---
@@ -493,3 +493,4 @@ Read: .ai-flow/prompts/frontend/flow-bootstrap-phase-1-discovery.md
 **Version:** 1.2.0
 
 
+

package/prompts/frontend/{flow-bootstrap-phase-1.md → flow-build-phase-1.md}

@@ -438,7 +438,7 @@ Documents Generated:
 
 Next: Phase 2 - Components & Framework
 
-Read: .ai-flow/prompts/frontend/flow-bootstrap-phase-2-components.md
+Read: .ai-flow/prompts/frontend/flow-build-phase-2-components.md
 ```
 
 ---
@@ -448,3 +448,4 @@ Read: .ai-flow/prompts/frontend/flow-bootstrap-phase-2-components.md
 **Version:** 1.2.0
 
 
+