ai-flow-dev 1.3.0 → 2.0.1

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,104 +164,124 @@ 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**
-
-   - What type of system are you building? (E-commerce/SaaS/CRM/Social/etc.)
+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)
+   - D) Social Network (Users, posts, feeds, messaging)
+   - E) Content Management (Articles, media, publishing)
+   - F) Project Management (Projects, tasks, boards)
+   - G) API Platform (API keys, rate limiting, webhooks)
+   - H) Marketplace (Buyers, sellers, listings)
+   - I) IoT Platform (Devices, sensors, commands)
+   - 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)
    - Which backend framework will you use? (NestJS/FastAPI/Spring Boot/etc.)
 
-### Step 2: Auto-Generate Suggestions
+### Step 2: Auto-Generate Intelligent Suggestions
 
-Based on the 6 critical answers, automatically suggest values for the remaining 65 questions using this logic:
+Based on the 6 critical answers, automatically generate comprehensive suggestions using AI reasoning.
 
-**Auto-Suggestion Decision Tree:**
+**Suggestion Logic:**
 
-```
-// Phase 1 (Business) - Auto-suggest based on system type
-IF system_type == "E-commerce":
-  target_users = "B2C + Mobile/Web apps"
-  core_features = ["Authentication", "Product catalog", "Shopping cart", "Checkout", "Order management"]
+For each phase, suggest defaults based on:
 
-IF system_type == "SaaS":
-  target_users = "B2B + API consumers"
-  core_features = ["Authentication with SSO", "Multi-tenant workspaces", "RBAC", "Subscription billing"]
+- **System Type** - E-commerce needs cart/checkout, SaaS needs multi-tenancy, etc.
+- **Framework** - NestJS → Prisma, FastAPI → SQLAlchemy, Django → Django ORM
+- **Scope** - MVP → simple setup, Production → robust setup, Enterprise → full observability
 
-// Phase 2 (Data) - Auto-suggest based on entities and system type
-database = "PostgreSQL" (default for most projects)
-orm = MATCH framework:
-  NestJS → "Prisma"
-  FastAPI → "SQLAlchemy"
-  Spring Boot → "Hibernate/JPA"
+**What Gets Auto-Generated:**
 
-// Phase 3 (Architecture) - Auto-suggest based on framework
-api_style = "REST" (standard)
-architecture_pattern = "Clean Architecture" (modular, testable)
+**Phase 1 (Business):**
 
-// Phase 4 (Security) - Best practices
-auth_method = "JWT"
-authorization = "RBAC"
-password_policy = "8+ chars, bcrypt 12 rounds"
+- ✅ Target users based on system type
+- ✅ Core features typical for the system type
+- ✅ Success metrics appropriate for the domain
 
-// Phase 5 (Code Standards) - Based on framework
-formatter = MATCH framework:
-  NestJS/Node.js → "Prettier + ESLint"
-  Python → "Black + pylint"
-  Java → "Spotless + Checkstyle"
+**Phase 2 (Data):**
 
-// Phase 6 (Testing) - Based on scope
-IF scope == "MVP":
-  coverage_target = "15-25%"
-  test_types = ["Integration only"]
-ELSE:
-  coverage_target = "60-80%"
-  test_types = ["Unit (70%)", "Integration (20%)", "E2E (10%)"]
+- ✅ Database: PostgreSQL (most common)
+- ✅ ORM: Match framework idiomatically
+- ✅ Caching: Redis for Production/Enterprise
+- ✅ Search: Elasticsearch only for Enterprise
 
-// Phase 7 (Operations) - Based on scope
-IF scope == "MVP":
-  deployment = "PaaS (Heroku/Railway)"
-  monitoring = "Basic (Sentry for errors)"
-ELSE:
-  deployment = "Cloud (AWS/GCP)"
-  monitoring = "Full (Datadog APM + Sentry)"
-```
+**Phase 3 (Architecture):**
+
+- ✅ Pattern: Monolith (MVP) → Clean Architecture (Production) → Microservices (Enterprise)
+- ✅ API: REST only (MVP) → REST + GraphQL (Production) → + gRPC (Enterprise)
+- ✅ Scaling strategy based on scope
+
+**Phase 4 (Security):**
+
+- ✅ Auth: JWT for MVP/Production, OAuth2 + SSO for Enterprise
+- ✅ Authorization: RBAC standard, ABAC for Enterprise
+- ✅ Password policies per scope
+- ✅ Rate limiting and CORS enabled
+
+**Phase 5 (Code Standards):**
+
+- ✅ Formatter/Linter matching framework (Prettier+ESLint, Black+pylint, etc.)
+- ✅ Git workflow: GitHub Flow (MVP), Git Flow (Production)
+- ✅ Conventional Commits
+
+**Phase 6 (Testing):**
+
+- ✅ Framework matching tech stack
+- ✅ Coverage: 20% (MVP), 70% (Production), 85% (Enterprise)
+- ✅ Test types distribution
+
+**Phase 7 (Operations):**
+
+- ✅ Deployment: PaaS (MVP), Cloud (Production), Multi-region (Enterprise)
+- ✅ CI/CD: GitHub Actions
+- ✅ Monitoring: Basic (MVP), APM (Production), Full observability (Enterprise)
 
 ### Step 3: Present Summary for Review
 
-After auto-generating all suggestions, present a two-tier summary:
+After auto-generating all suggestions, present a clear summary:
 
-#### **Quick Summary (1 paragraph max)**
+#### **Quick Summary (1 paragraph)**
 
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 ✅ Configuration Complete - Quick Summary
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
-Your [System Type] backend will use [Framework] with [Database], following Clean Architecture with [X] entities ([list main entities]). Security includes JWT auth with RBAC, bcrypt passwords, and rate limiting. Code follows [Language] best practices with [Formatter/Linter], targeting [X]% test coverage. Deployment to [Platform] with [Monitoring] for production readiness.
+Your [System Type] backend will use [Framework] with [Database], following
+[Architecture Pattern] with [X] entities ([entity names]). Security includes
+[Auth Method] with [Authorization], [Password Policy]. Code follows
+[Formatter] + [Linter], targeting [Coverage Target] test coverage. Deployment
+to [Deployment Platform] with [Monitoring] for production readiness.
 
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 ```
 
-**Example:**
+**Example (E-commerce + NestJS + Production):**
 
 ```
-Your E-commerce backend will use NestJS (TypeScript) with PostgreSQL and Prisma, following Clean Architecture with 8 entities (User, Product, Category, Cart, Order, Payment, Address, Review). Security includes JWT auth with RBAC (admin, user roles), bcrypt passwords, and rate limiting on all endpoints. Code follows TypeScript strict mode with Prettier + ESLint, targeting 60-80% test coverage with Jest. Deployment to Heroku for MVP with Sentry error tracking for production readiness.
+Your E-commerce backend will use NestJS with PostgreSQL, following Clean
+Architecture with 8 entities (User, Product, Category, Cart, Order, Payment,
+Address, Review). Security includes JWT + Refresh Tokens with RBAC,
+12+ characters bcrypt 12 rounds. Code follows Prettier + ESLint +
+@typescript-eslint, targeting 70% test coverage. Deployment to Cloud
+(AWS/GCP/Azure) with APM (Datadog/New Relic) + Sentry for production
+readiness.
 ```
 
 #### **Extended Report (Organized by Phase)**
@@ -195,67 +292,43 @@ Your E-commerce backend will use NestJS (TypeScript) with PostgreSQL and Prisma,
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 **Phase 1: Business & Discovery**
-• System Type: [E-commerce]
-• Target Users: External end-users (B2C) + Mobile/Web apps
-• Core Features: Authentication, Product catalog with search/filters, Shopping cart, Checkout and payment, Order management, Inventory tracking, Admin dashboard
-• Scope: V1 includes auth + catalog + cart + checkout; V2 defers advanced analytics, third-party integrations
-• Constraints: Time (MVP by Q2 2025)
-• Success Metrics: 1k→10k users, <200ms response, 99% uptime
+• System Type: [From user input]
+• Target Users: [AI-suggested based on system type]
+• Core Features: [AI-suggested based on system type]
+• Success Metrics: [AI-suggested based on system type]
 
 **Phase 2: Data Architecture**
-• Database: PostgreSQL 15 (ACID, relational, JSON support)
-• ORM: Prisma 5.x (type-safe, auto-migrations)
-• Entities: User, Product, Category, Cart, Order, OrderItem, Payment, Address
-• Relationships: User→Order (1:N), Order→OrderItem (1:N), User→Cart (1:N), Category→Product (1:N)
-• Data Volume: Low (<10k records), Moderate growth, Low complexity (text-based)
-• Retention: Keep forever (no auto-deletion)
+• Database: [AI-suggested from scope]
+• ORM: [AI-suggested from framework]
+• Caching: [AI-suggested from scope]
+• Core Entities: [From user input]
 
 **Phase 3: System Architecture**
-• Framework: NestJS 10.x (TypeScript, enterprise-ready)
-• Language: TypeScript 5.3 with strict mode
-• API Style: REST with OpenAPI/Swagger auto-docs
-• Architecture: Clean Architecture (feature-based modules)
-• External Services: SendGrid (email), Stripe (payments), AWS S3 (file storage)
-• Caching: None for MVP (defer to V2)
-• Background Jobs: None for MVP
-
-**Phase 4: Security & Authentication**
-• Auth Method: JWT (stateless, scalable)
-• Token Config: 15min access, 7d refresh, RS256 algorithm
-• Authorization: RBAC with roles (admin, user, moderator)
-• Password Policy: 8+ chars, uppercase + lowercase + number, bcrypt 12 rounds
-• Rate Limiting: 5/15min (auth), 100/min (read), 30/min (write)
-• CORS: Specific origins (https://myapp.com + localhost:3000 for dev)
-• Encryption: TLS 1.2+ in transit, AES-256 for PII fields at rest
-• Compliance: GDPR (if EU users) - data export, deletion rights
+• Framework: [From user input]
+• Pattern: [AI-suggested from scope]
+• API Style: [AI-suggested from scope]
+• Scaling: [AI-suggested from scope]
+
+**Phase 4: Security**
+• Authentication: [AI-suggested from scope]
+• Authorization: [AI-suggested from scope]
+• Password Policy: [AI-suggested from scope]
 
 **Phase 5: Code Standards**
-• Formatter: Prettier + ESLint (2 spaces, single quotes, semicolons)
-• Naming: kebab-case files, PascalCase classes, camelCase functions
-• Structure: Feature-based modules (users/, products/, orders/)
-• Documentation: JSDoc for public APIs and complex logic
-• Error Handling: Centralized exception handler with custom error classes
-• Logging: Winston with JSON structured logs
-• Git Workflow: Feature branch + PR with 1 reviewer approval
-• Commits: Conventional Commits (feat/fix/docs/chore)
-
-**Phase 6: Testing Strategy**
-• Framework: Jest (unit + integration + e2e)
-• Coverage Target: 60-80% overall
-• Test Distribution: 70% unit, 20% integration, 10% e2e
-• Test Database: In-memory SQLite for fast tests
-• Mocking: External APIs, payment gateways, email service
-• CI Integration: GitHub Actions with automated test runs on PR
-
-**Phase 7: Operations & Deployment**
-• Platform: Heroku (PaaS for fast MVP deployment)
-• Containerization: Docker + Docker Compose for local dev
-• Environments: Development (local), Staging (Heroku pipeline), Production (Heroku)
-• CI/CD: GitHub Actions (test → build → deploy to staging → manual approval → production)
-• Monitoring: Sentry for error tracking, basic console logs
-• Health Checks: /health endpoint with database connectivity check
-• Backups: Daily automated PostgreSQL backups (Heroku addon)
+• Formatter: [AI-suggested from framework]
+• Linter: [AI-suggested from framework]
+• Git Workflow: [AI-suggested from scope]
+
+**Phase 6: Testing**
+• Coverage Target: [AI-suggested from scope]
+• Framework: [AI-suggested from framework]
 
+**Phase 7: Operations**
+• Deployment: [AI-suggested from scope]
+• Monitoring: [AI-suggested from scope]
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+💡 These suggestions can be customized during document review.
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 ```
 
@@ -289,7 +362,7 @@ Your choice (A/B/C): __
 
 ### Step 5: Generate Documentation
 
-Generate all 17 documents using the confirmed values (either auto-suggested or user-customized).
+Generate all 17 documents using the confirmed values (either AI-suggested or user-customized).
 
 ---
 
@@ -297,26 +370,26 @@ Generate all 17 documents using the confirmed values (either auto-suggested or u
 
 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
 ```
 
 ---
@@ -325,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
@@ -345,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:**
 
@@ -363,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:**
 
@@ -381,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:**
 
@@ -401,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:**
 
@@ -419,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:**
 
@@ -437,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:**
 
@@ -455,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:**
 
@@ -476,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:**
 
@@ -501,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:**
 
@@ -543,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
 ```
 
 ---
@@ -565,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
 ```
 
 ---
@@ -636,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
 
 ---
 
@@ -701,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
 
 ---
@@ -817,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}}
@@ -864,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
@@ -882,4 +955,3 @@ _Version: 4.0 (Phase 9 integrated - Implementation Roadmap with Story Points)_
 _Last Updated: 2025-12-09_
 _Version: 3.0 (Unified workflow: Phase 8 integrates project setup + final docs generation)_
 _AI Flow - Transform your idea into production-ready code in minutes_
-