ai-flow-dev 2.1.8 → 2.2.0

package/prompts/backend/flow-build.md

@@ -14,19 +14,20 @@ Your mission is to guide the user through creating **comprehensive, production-r
 
 ### Detectar Argumento de Fase
 
+// turbo
 Buscar en el mensaje del usuario patrones como:
 
-- "fase 0", "fase 1", "fase 2", ..., "fase 9"
+- "fase 0", "fase 1", "fase 2", ..., "fase 10"
 - "phase 0", "phase 1", etc.
 - "ejecutar fase N"
 - "run phase N"
 
 ### Comportamiento
 
-**Si se detecta "fase N" (donde N = 0-9):**
+**Si se detecta "fase N" (donde N = 0-10):**
 
 1. **Validar que la fase existe para backend:**
-   - Fase 0: Context Discovery (opcional, solo proyectos existentes)
+   - Fase 0: Context Discovery
    - Fase 1: Discovery & Business
    - Fase 2: Data Architecture
    - Fase 3: System Architecture
@@ -35,851 +36,100 @@ Buscar en el mensaje del usuario patrones como:
    - Fase 6: Testing Strategy
    - Fase 7: Operations & Deployment
    - Fase 8: Project Setup & Final Documentation
-   - Fase 9: Implementation Roadmap (opcional)
+   - Fase 9: Implementation Roadmap
+   - Fase 10: User Stories Generation
 
 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`
+   - Ejecutar SOLO esa fase y seguir sus instrucciones internas.
+   - Al finalizar, informar 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
+   - Listar las fases válidas (0-10) 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.
-```
+- Ejecutar el flujo completo comenzando por la Selección de Modo (A/B).
 ---
 ## 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)
-2. **Ask for Project Scope SECOND** - After mode selection, ask the user to select: MVP, Production-Ready, or Enterprise
-3. **Adapt questions based on mode and scope** - Skip or simplify questions according to the selected mode and scope level
-4. **Execute ALL applicable phases in order** - Do not skip phases, but adjust depth based on scope
-5. **Ask questions ONE BY ONE** - Do not present multiple questions at once. Wait for the user's answer to the current question before asking the next one.
-6. **Show progress indicator before EVERY question** - Use this format:
-   ```
----
-   📋 Phase [N]: [Phase Name]  |  Question [X]/[Total]  |  Phase Progress: [%]%
----
-   ```
-   Example for Phase 1, Question 3 of 8:
-   ```
----
-   📋 Phase 1: Discovery & Business  |  Question 3/8  |  Phase Progress: 37%
----
-   ```
-7. **Provide recommendations** using these markers:
-   - ⭐ **Recommended** - Best choice for most projects
-   - 🔥 **Popular** - Widely used in industry
-   - ⚡ **Modern** - Cutting-edge, newer approach
-   - 🏆 **Enterprise** - Best for large-scale projects
-8. **Use multiple choice when possible** - Give 3-4 options (A, B, C, D)
-9. **Validate completeness** - Ensure all critical information is gathered
-10. **Generate documents incrementally** - After each phase, generate corresponding documents with validation
-11. **Show summary at the end** - Present both a quick summary (1 paragraph) and an extended report
+1. **Ask for Questionnaire Mode FIRST** (Interactive vs Smart Auto-Suggest).
+2. **Ask for Project Scope SECOND** (MVP, Production-Ready, or Enterprise).
+3. **Execute ALL applicable phases in order**, adjusting depth based on scope.
+4. **Ask questions ONE BY ONE**. Wait for the user's answer.
+5. **Show progress indicator before EVERY question**.
+6. **Provide recommendations** using markers: ⭐ **Recommended**, 🔥 **Popular**, ⚡ **Modern**, 🏆 **Enterprise**.
+7. **Generate documents incrementally** after each phase.
 ---
 ## 🚀 Mode Selection
 
 **BEFORE STARTING ANY PHASE**, ask the user to select the questionnaire mode:
 
-```
----
-🚀 Welcome to AI Flow!
----
-Let's create comprehensive documentation for your backend project.
-
-**How would you like to proceed?**
-
 A) ⭐ **Interactive Mode (Recommended)**
-   • You answer each question step-by-step
-   • Full control over every decision
-   • Takes 90-120 min for new projects, 35-70 min for existing
-   • Best for: Custom requirements, specific needs
+   • Full control, step-by-step questions. (90-120 min)
 
 B) ⚡ **Smart Auto-Suggest Mode**
-   • AI suggests best practices for most questions
-   • You only answer 6 critical business questions
-   • Takes 15-25 minutes
-   • Best for: MVPs, standard projects, quick setup
+   • AI suggests best practices, you answer 6 critical questions. (15-25 min)
 
 Your choice (A/B): __
-```
 
 **Based on the selection:**
+- **Mode A (Interactive):** Proceed with normal sequential flow (Phases 0-10).
+- **Mode B (Smart Auto-Suggest):** Ask the following 6 critical questions one by one, then auto-generate all suggestions based on industry standards and the system type:
 
-- **Mode A (Interactive):** Proceed with normal flow - execute all phases, ask all questions one by one
-- **Mode B (Smart Auto-Suggest):** Execute "Smart Auto-Suggest Flow" (see section below)
----
-## ⚡ Smart Auto-Suggest Flow (Mode B)
-
-**This flow only asks 6 critical business questions and auto-suggests the rest based on best practices.**
-
-### Step 1: Ask Critical Questions Only
-
-Ask these 6 questions one by one with progress indicator:
-
-```
----
-⚡ Smart Auto-Suggest Mode  |  Question 1/6  |  Progress: 17%
----
-```
-
-**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)
-   - 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 Intelligent Suggestions
-
-Based on the 6 critical answers, automatically generate comprehensive suggestions using AI reasoning.
-
-**Suggestion Logic:**
-
-For each phase, suggest defaults based on:
-
-- **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
-
-**What Gets Auto-Generated:**
-
-**Phase 1 (Business):**
-
-- ✅ Target users based on system type
-- ✅ Core features typical for the system type
-- ✅ Success metrics appropriate for the domain
-
-**Phase 2 (Data):**
-
-- ✅ Database: PostgreSQL (most common)
-- ✅ ORM: Match framework idiomatically
-- ✅ Caching: Redis for Production/Enterprise
-- ✅ Search: Elasticsearch only for Enterprise
-
-**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 clear summary:
-
-#### **Quick Summary (1 paragraph)**
-
-```
----
-✅ Configuration Complete - Quick Summary
----
-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 (E-commerce + NestJS + Production):**
-
-```
-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)**
-
-```
----
-📋 Extended Configuration Report
----
-**Phase 1: Business & Discovery**
-• 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: [AI-suggested from scope]
-• ORM: [AI-suggested from framework]
-• Caching: [AI-suggested from scope]
-• Core Entities: [From user input]
-
-**Phase 3: System Architecture**
-• 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: [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.
----
-```
-
-### Step 4: Confirmation & Override Option
-
-```
-Would you like to:
-
-A) ✅ **Accept all suggestions** (Generate documentation now - 2 minutes)
-B) 📝 **Review & customize specific sections** (Show which phase to modify)
-C) ❌ **Cancel and switch to Interactive Mode** (Full control)
-
-Your choice (A/B/C): __
-```
-
-**If user selects B:**
-
-- Show list of phases
-- Ask which phase they want to customize
-- Show that phase's suggested values
-- Allow modifications
-- Return to confirmation
-
-**If user selects A:**
-
-- Proceed directly to document generation with all suggested values
-
-**If user selects C:**
-
-- Restart with Interactive Mode (Mode A)
-
-### Step 5: Generate Documentation
-
-Generate all 17 documents using the confirmed values (either AI-suggested or user-customized).
----
-## 📚 How to Use This Guide
-
-This documentation is **modularized** for better maintainability and performance. Each phase is in a separate file.
-
-### 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-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-build-phase-4-security.md and execute only Phase 4
-```
----
-## 🎯 Phase Overview
-
-### Phase 0: Context Discovery (Optional)
-
-**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
-
-**What it does:**
-
-- **Layer 0:** Checks cache (0-2 seconds)
-- **Layer 1:** Fast metadata scan (10-20 seconds) - Detects language, framework, ORM
-- **Layer 2:** Structural analysis (30-90 seconds) - Analyzes directory structure, entities
-- **Layer 3:** Selective deep analysis (optional) - Extracts endpoints, relationships, security patterns
-
-**Supports:** 12 languages, 60+ frameworks, 35+ ORMs (98% market coverage)
-
-**Skip if:** Starting a completely new project from scratch
----
-### Phase 1: Discovery & Business
-
-**File:** `backend/flow-build-phase-1-business.md`
-**Duration:** 15-20 minutes
-**Key Questions:**
-
-- What problem are you solving?
-- Who are your target users?
-- What are your business objectives?
-- What is your project scope?
-
-**Generates:**
-
-- `project-brief.md`
-- Parts of `AGENT.md`
----
-### Phase 2: Data Architecture
-
-**File:** `backend/flow-build-phase-2-data.md`
-**Duration:** 15-20 minutes
-**Key Questions:**
-
-- What entities/models do you need?
-- How are they related?
-- What database will you use?
-- What are the data ownership rules?
-
-**Generates:**
-
-- `docs/data-model.md`
-- Parts of `ai-instructions.md`
----
-### Phase 3: System Architecture
-
-**File:** `backend/flow-build-phase-3-architecture.md`
-**Duration:** 15-20 minutes
-**Key Questions:**
-
-- What tech stack will you use?
-- How will you structure your code?
-- What external services do you need?
-- How will you handle caching and background jobs?
-
-**Generates:**
-
-- `docs/architecture.md`
-- `docs/business-flows.md`
-- `docs/api.md`
-- Parts of `ai-instructions.md`
----
-### Phase 4: Security & Authentication
-
-**File:** `backend/flow-build-phase-4-security.md`
-**Duration:** 15-20 minutes
-**Key Questions:**
+  1. **Project Name & Description** (Skip if Phase 0 detected context)
+  2. **Project Overview:** What problem does this system solve?
+  3. **Business Objectives:** Top 3 measurable objectives.
+  4. **System Type:** E-commerce, SaaS, CRM, Social, CMS, API Platform, etc.
+  5. **Core Data Entities:** Main models (User, Product, Order, etc.).
+  6. **Backend Framework:** NestJS, FastAPI, Spring Boot, Go, etc.
 
-- How will users authenticate?
-- What authorization model will you use?
-- What compliance requirements do you have?
-- How will you handle sensitive data?
-
-**Generates:**
-
-- `specs/security.md`
-- Parts of `ai-instructions.md`
----
-### Phase 5: Code Standards
-
-**File:** `backend/flow-build-phase-5-standards.md`
-**Duration:** 15-20 minutes
-**Key Questions:**
-
-- What naming conventions will you use?
-- How will you handle errors?
-- What logging strategy will you use?
-- What validation approach will you use?
-
-**Generates:**
-
-- `docs/code-standards.md`
-- Parts of `ai-instructions.md`
----
-### Phase 6: Testing Strategy
-
-**File:** `backend/flow-build-phase-6-testing.md`
-**Duration:** 15-25 minutes
-**Key Questions:**
-
-- What types of tests will you write?
-- What coverage targets do you have?
-- How will you structure your tests?
-- What testing tools will you use?
-
-**Generates:**
-
-- `docs/testing.md`
-- Parts of `ai-instructions.md`
----
-### Phase 7: Operations & Deployment
-
-**File:** `backend/flow-build-phase-7-operations.md`
-**Duration:** 10 minutes
-**Key Questions:**
-
-- Where will you deploy?
-- How will you handle environments?
-- What monitoring will you use?
-- How will you handle logging and errors?
-
-**Generates:**
-
-- `docs/operations.md`
-- `specs/configuration.md`
-- `.env.example`
-
-**Next:** Transitions to Phase 8 for project setup and final documentation
----
-### Phase 8: Project Setup & Final Documentation
-
-**File:** `backend/flow-build-phase-8.md`
-**Duration:** 10-15 minutes
-**Key Steps:**
-
-- Detect project state (new vs existing)
-- Initialize framework (optional, for new projects)
-- Generate final documentation
-- Create master index (AGENT.md)
-- Generate README.md with intelligent merge
-
-**Generates:**
-
-- `docs/business-flows.md`
-- `docs/api.md`
-- `docs/contributing.md`
-- `AGENT.md` (master index)
-- `README.md`
-- Tool-specific configs (`.clauderules`, `.cursorrules`, `.github/copilot-instructions.md`)
-
-**Next:** Offers optional Phase 9 for implementation roadmap generation
----
-### Phase 9: Implementation Roadmap (Optional)
-
-**File:** `backend/flow-build-phase-9.md`
-**Duration:** 15-30 minutes
-**Key Steps:**
-
-- Analyze all generated documentation
-- Define Epics by domain
-- Break down Features with Story Points (Fibonacci scale)
-- Generate dependency graph and execution order
-- Identify parallelization opportunities
-- Create production readiness checklist
-
-**Generates:**
-
-- `docs/roadmap.md` (complete implementation plan)
-
-**Output includes:**
-
-- Epics organized by priority
-- Features with Story Point estimations
-- Task breakdown with acceptance criteria
-- Ready-to-execute `/feature` commands
-- Dependency graph (Mermaid)
-- Time estimates (1 dev, 2 devs, 3 devs)
-
-**Skip if:** You prefer to start coding immediately without a detailed roadmap
+  **AI Logic for Auto-Suggest:**
+  - Generate comprehensive suggestions for all phases (1-10).
+  - Use idiomatic tools for the selected framework (e.g., NestJS -> Prisma).
+  - Adjust complexity based on scope (MVP vs Enterprise).
+  - Present a summary for confirmation before generating documentation.
 ---
-## 🚀 Quick Start Guide
 
-### For New Projects
+## 📚 Flow Overview & Modular Phases
 
-```
-1. Skip Phase 0
-2. Start with Phase 1 (Discovery & Business)
-3. Continue through Phases 2-7 sequentially
-4. Review and refine generated documentation
-```
+Each phase is modularized for better maintainability and reduced context usage.
 
-**Command:**
+| Phase | Description | File |
+|-------|-------------|------|
+| **Phase 0** | Context Discovery | `backend/flow-build-phase-0.md` |
+| **Phase 1** | Business & Discovery | `backend/flow-build-phase-1.md` |
+| **Phase 2** | Data Architecture | `backend/flow-build-phase-2.md` |
+| **Phase 3** | System Architecture | `backend/flow-build-phase-3.md` |
+| **Phase 4** | Security & Auth | `backend/flow-build-phase-4.md` |
+| **Phase 5** | Code Standards | `backend/flow-build-phase-5.md` |
+| **Phase 6** | Testing Strategy | `backend/flow-build-phase-6.md` |
+| **Phase 7** | Operations & Deployment | `backend/flow-build-phase-7.md` |
+| **Phase 8** | Setup & Final Docs | `backend/flow-build-phase-8.md` |
+| **Phase 9** | Roadmap (Optional) | `backend/flow-build-phase-9.md` |
+| **Phase 10** | User Stories (Optional) | `backend/flow-build-phase-10.md` |
 
-```
-Read .ai-flow/prompts/backend/flow-build-phase-1-business.md and execute Phase 1
-```
 ---
-### For Existing Projects
-
-```
-1. START with Phase 0 (Context Discovery)
-   - AI will analyze your code and pre-populate answers
-   - Saves 40-60% of time
+## 📋 Scope Selection (MVP / Production / Enterprise)
 
-2. Continue with Phases 1-7
-   - Skip questions already answered in Phase 0
-   - Only fill gaps in documentation
+Before starting Phase 1, ask the user to select the Project Scope.
+> 📎 **Reference:** See [shared/scope-levels.md](../shared/scope-levels.md)
 
-3. Review and refine generated documentation
-```
-
-**Command:**
-
-```
-Read .ai-flow/prompts/backend/flow-build-phase-0-context.md and execute Phase 0
-```
 ---
-## 📋 Scope Selection
-
-Before starting Phase 1, you'll select a scope level:
-
-> 📎 **Reference:** See [prompts/shared/scope-levels.md](../shared/scope-levels.md) for detailed scope definitions (MVP, Production-Ready, Enterprise).
+## 🔄 Documentation Sync
 
-### A) ⭐ MVP / Prototype
+As your project grows, use the following to keep docs updated:
+**Command:** `/flow-docs-sync`
+**Logic:** Read `.ai-flow/prompts/backend/flow-docs-sync.md`.
 
-**Focus:** Core functionality + basic tests. Best for POCs and internal tools.
-
-### B) 🚀 Production-Ready
-
-**Focus:** Production-grade with best practices. Best for SaaS and customer-facing APIs.
-
-### C) 🏢 Enterprise / Mission-Critical
-
-**Focus:** Enterprise governance, compliance, and high scalability.
 ---
-## 📊 Benefits of Modular Structure
-
-✅ **Faster Loading** - Load only the phase you need (~8-50 KB vs 140 KB)
-✅ **Better Maintainability** - Changes to one phase don't affect others
-✅ **Independent Execution** - Run individual phases without loading entire file
-✅ **Reduced Context Usage** - AI assistants use 50-70% less context
-✅ **Clearer Git Diffs** - Changes are isolated to specific phase files
-✅ **Easier Collaboration** - Multiple people can work on different phases
-✅ **Better Performance** - Smaller files process faster in AI tools
----
-## 🎓 Best Practices
-
-### Before Starting
+## 🎯 After Completion
 
-1. Have a clear problem statement
-2. Know your approximate tech stack (or let Phase 0 detect it)
-3. Understand your target users
-4. Choose your scope (MVP/Production-Ready/Enterprise)
-5. Set aside appropriate time based on scope
+ALWAYS present a final summary:
+1. **Quick Summary:** 1 paragraph overview.
+2. **Extended Report:** Key decisions by phase.
+3. **Scaffolding:** Offer to initialize or commit changes.
 
-### During Execution
-
-1. Take your time with each question
-2. Use recommendations (⭐🔥⚡🏆) as guides
-3. Be specific - more detail = better docs
-4. Confirm each phase before proceeding
-5. Review generated docs after each phase
-
-### After Completion
-
-1. Review all generated documents
-2. Customize as needed for your specific project
-3. Share `AGENT.md` with your team
-4. Update documents as your project evolves
-5. Use `/flow-build-phase-[N]` commands to regenerate individual sections
 ---
-## 💡 Tips
-
-- **Use cache:** If you run Phase 0, it saves results for instant re-runs
-- **Start selective:** For quick updates, run only the phases you need
-- **Iterate:** You can re-run phases to refine documentation
-- **Universal support:** Works with 12 languages, 60+ frameworks, 35+ ORMs
-- **AI-agnostic:** Works with Claude, Copilot, Cursor, Gemini, any AI tool
----
-## 🔄 Maintaining Documentation
-
-As your project evolves, your documentation may become out of sync with your code. Use the `/flow-docs-sync` command to keep documentation synchronized.
-
-### Command: `/flow-docs-sync`
-
-**Purpose:** Detect code changes and automatically update affected documentation files.
-
-**How it works:**
-
-1. Compares current code state with last documented state (`.ai-flow/cache/docs-analysis.json`)
-2. Detects changes in endpoints, entities, dependencies, architecture, configuration
-3. Shows report of documents that need updating
-4. Asks for confirmation to update all detected documents
-5. Updates documents incrementally (only changed sections)
-6. Updates `docs-analysis.json` with new state
-
-**When to use:**
-
-- After adding new API endpoints
-- After modifying database entities
-- After adding new dependencies
-- After changing project structure
-- After adding new environment variables
-- Periodically to ensure documentation stays current
-
-**Usage:**
-
-```
-/flow-docs-sync
-```
-
-**For detailed instructions:** Read `.ai-flow/prompts/backend/flow-docs-sync.md`
----
-## 📞 Need Help?
-
-- **Issues:** [GitHub Issues](https://github.com/victorvelazquez/ai-flow/issues)
-- **Documentation:** [README.md](../../README.md)
-- **Contributing:** [CONTRIBUTING.md](../../CONTRIBUTING.md)
-- **Maintaining Docs:** Use `/flow-docs-sync` command (see AI Flow README for details)
----
-**Ready to start?** Choose your path:
-
-1. **First:** Ask user to select Mode (A: Interactive or B: Smart Auto-Suggest)
-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-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
----
-## 📊 Final Summary (After Completion)
-
-**CRITICAL:** After generating all documentation, ALWAYS present a two-tier summary:
-
-### **Tier 1: Quick Summary (1 paragraph max)**
-
-Present a concise overview in 1-2 sentences covering:
-
-- System type and framework
-- Database and main entities (count + examples)
-- Key architectural decisions
-- Security approach
-- Deployment platform
-
-**Format:**
-
-```
----
-✅ Configuration Complete - Quick Summary
----
-Your [System Type] backend will use [Framework] with [Database], following [Architecture] with [X] entities ([list 2-3 main ones]). Security includes [Auth Method] with [Authorization], and deployment to [Platform] with [Monitoring].
----
-```
-
-### **Tier 2: Extended Report (Organized, Not Too Long)**
-
-Present a structured report covering each phase's key decisions (3-5 bullets per phase max):
-
-```
----
-📋 Extended Configuration Report
----
-**Phase 1: Business**
-• System Type: [Type]
-• Target Users: [Who]
-• Core Features: [3-5 main features]
-• Success Metrics: [Key goals]
-
-**Phase 2: Data Architecture**
-• Database: [Type + Version]
-• ORM: [Tool]
-• Entities: [List main entities]
-• Relationships: [Key patterns]
-
-**Phase 3: System Architecture**
-• Framework: [Name + Version]
-• Language: [Name + Version]
-• API Style: [REST/GraphQL/etc.]
-• Architecture: [Pattern]
-• External Services: [List]
-
-**Phase 4: Security**
-• Auth: [Method + token config]
-• Authorization: [Model + roles]
-• Password: [Policy]
-• Rate Limiting: [Strategy]
-
-**Phase 5: Code Standards**
-• Formatter: [Tool + config]
-• Naming: [Conventions]
-• Structure: [Pattern]
-• Git Workflow: [Strategy]
-
-**Phase 6: Testing**
-• Framework: [Tool]
-• Coverage: [Target %]
-• Types: [Unit/Integration/E2E split]
-• CI: [Platform]
-
-**Phase 7: Operations**
-• Platform: [Deployment]
-• Containerization: [Docker/etc.]
-• Environments: [Dev/Staging/Prod]
-• Monitoring: [Tools]
----
-✅ **Documentation Generated Successfully!**
-
-Created 17 professional documents in your project:
-• AGENT.md, ai-instructions.md, project-brief.md, README.md
-• 9 technical docs (architecture, data-model, api, etc.)
-• 2 specs (security, configuration)
-• .env.example
----
-Ready to commit the documentation?
-
-A) ✅ Yes, create initial commit now
-B) No, I'll review first and commit manually later
-
-Your choice (A): __
-```
-
-**If choice A (recommended):**
-
-```bash
-# Initialize git repository (if not already initialized)
-git init
-
-# Stage all generated documentation
-git add .ai-flow/
-
-# Create initial commit with documentation metadata
-git commit -m "docs: initial project documentation
-
-Generated by AI Flow /flow-build command:
-- 17 documentation files (backend)
-- Architecture: {{ARCHITECTURE_PATTERN}}
-- Tech stack: {{FRAMEWORK}}, {{DATABASE}}, {{ORM}}
-- Testing strategy: {{TEST_STRATEGY}}
-- Deployment: {{DEPLOYMENT_PLATFORM}}
-
-Ready for project scaffold with /project-scaffold"
-```
-
-```
-✅ Initial commit created
-
-Commit hash: {{COMMIT_HASH}}
-Files tracked: 17 documentation files
----
-🎯 Next Step: Initialize Project & Optional Roadmap
----
-Your documentation is ready! Now let's initialize your project.
-
-Continue with Phase 8?
-
-A) ✅ Yes, continue to Phase 8 (recommended) - 10-15 min
-   → Initialize project + Generate final docs
-   → Then option to continue to Phase 9 (roadmap)
-
-B) No, I'll review documentation first
-
-Your choice (A): __
-```
-
-**If choice A:** Automatically transitions to Phase 8
-
-- Phase 8 will detect project state and offer framework initialization
-- Generates final documentation (business-flows, api, contributing)
-- Creates AGENT.md and README.md
-- Sets up AI tool configs
-
-**If choice B:** Show manual workflow:
-
-```
-**Manual Workflow (resume anytime):**
-
-1. Review documentation in .ai-flow/templates/
-2. When ready, run Phase 8:
-   → 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
-   → Includes Epics, Features, Tasks, and execution order
-4. Start implementing: /feature <feature-name>
-   → Implements features following your architecture
-
-💡 Tip: All phases are independent and re-executable.
----
-```
----
-_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)_
+_Version: 4.2 (v2.1.9) (Antigravity Optimized - Modularized & Turbo-Enabled)_
+_Last Updated: 2025-12-21_
 _AI Flow - Transform your idea into production-ready code in minutes_
-
-
-
-