ai-flow-dev 2.2.0 → 2.2.1

package/prompts/backend/flow-build-phase-4.md

@@ -12,6 +12,25 @@
 
 Define security policies, authentication, authorization, and compliance requirements.
 
+---
+
+## 🔍 Pre-Flight Check (Smart Skip Logic)
+
+> 📎 **Reference:** See [prompts/shared/smart-skip-preflight.md](../shared/smart-skip-preflight.md) for the complete smart skip logic.
+
+**Execute Pre-Flight Check for Phase 4:**
+
+- **Target File**: `specs/security.md`
+- **Phase Name**: "SECURITY & AUTHENTICATION"
+- **Key Items**: Auth strategy, encryption, security patterns, compliance
+- **Typical Gaps**: Compliance requirements, audit logging, security policies
+
+**Proceed with appropriate scenario based on audit data from `.ai-flow/cache/audit-data.json`**
+
+---
+
+## Phase 4 Questions (Full Mode)
+
 **4.1 Authentication Method**
 
 ```

package/prompts/backend/flow-build-phase-5.md

@@ -12,6 +12,25 @@
 
 Establish code quality rules, naming conventions, and development practices.
 
+---
+
+## 🔍 Pre-Flight Check (Smart Skip Logic)
+
+> 📎 **Reference:** See [prompts/shared/smart-skip-preflight.md](../shared/smart-skip-preflight.md) for the complete smart skip logic.
+
+**Execute Pre-Flight Check for Phase 5:**
+
+- **Target File**: `docs/code-standards.md`
+- **Phase Name**: "CODE STANDARDS"
+- **Key Items**: Linters, formatters, naming conventions, code review process
+- **Typical Gaps**: Team-specific conventions, code review workflow
+
+**Proceed with appropriate scenario based on audit data from `.ai-flow/cache/audit-data.json`**
+
+---
+
+## Phase 5 Questions (Full Mode)
+
 **5.1 Code Style & Formatting**
 
 ```

package/prompts/backend/flow-build-phase-6.md

@@ -18,6 +18,25 @@ Define testing approach, tools, and quality gates.
 
 **🚨 Important: All projects require basic testing. Scope determines depth, not whether to test.**
 
+---
+
+## 🔍 Pre-Flight Check (Smart Skip Logic)
+
+> 📎 **Reference:** See [prompts/shared/smart-skip-preflight.md](../shared/smart-skip-preflight.md) for the complete smart skip logic.
+
+**Execute Pre-Flight Check for Phase 6:**
+
+- **Target File**: `docs/testing.md`
+- **Phase Name**: "TESTING STRATEGY"
+- **Key Items**: Test framework, coverage targets, test types, CI/CD integration
+- **Typical Gaps**: E2E strategy, load testing, performance testing
+
+**Proceed with appropriate scenario based on audit data from `.ai-flow/cache/audit-data.json`**
+
+---
+
+## Phase 6 Questions (Full Mode)
+
 **6.1 Testing Framework**
 
 ```

package/prompts/backend/flow-build-phase-7.md

@@ -12,6 +12,25 @@
 
 Define deployment, monitoring, and operational practices.
 
+---
+
+## 🔍 Pre-Flight Check (Smart Skip Logic)
+
+> 📎 **Reference:** See [prompts/shared/smart-skip-preflight.md](../shared/smart-skip-preflight.md) for the complete smart skip logic.
+
+**Execute Pre-Flight Check for Phase 7:**
+
+- **Target File**: `docs/deployment.md`
+- **Phase Name**: "OPERATIONS & DEPLOYMENT"
+- **Key Items**: CI/CD pipeline, deployment platform, monitoring, logging
+- **Typical Gaps**: Incident runbooks, disaster recovery, scaling strategy
+
+**Proceed with appropriate scenario based on audit data from `.ai-flow/cache/audit-data.json`**
+
+---
+
+## Phase 7 Questions (Full Mode)
+
 **7.1 Deployment Environment**
 
 ```

package/prompts/backend/flow-build-phase-9.md

@@ -298,6 +298,20 @@ COVERAGE VALIDATION
 
 ### Step 9.6: Generate Document (5-10 min)
 
+## Architectural Markers Key
+
+| Marker | Name | Description |
+|--------|------|-------------|
+| **[I]** | Infrastructure | Technical setup, configuration, and core utilities |
+| **[E]** | Entity | Database models and schema definitions |
+| **[R]** | Repository | Data access layer (Prisma ORM) |
+| **[S]** | Service | Business logic and use cases |
+| **[C]** | Controller | API endpoints and request handling |
+| **[T]** | Tests | Unit, integration, and E2E testing |
+| **[D]** | Documentation | Technical and API documentation |
+
+---
+
 **Write `docs/roadmap.md` with this structure:**
 
 ```markdown

package/prompts/backend/flow-check-review.md

@@ -0,0 +1,20 @@
+---
+description: Internal logic for Code Review within flow-check
+---
+
+# AI Flow - Review Logic
+
+Performs professional multi-aspect code review.
+
+---
+## 🔍 Review Aspects
+1. **Security**: OWASP patterns, secrets, auth.
+2. **Performance**: N+1, leaks, async blocking.
+3. **Tests**: Edge cases, quality, coverage.
+4. **Architecture**: SOLID, DRY, Patterns.
+5. **Quality**: Naming, complexity, linting.
+
+---
+## 📊 Reporting
+- Prioritize: 🔴 Critical, 🟡 Warning, 🟢 Suggestion.
+- Save report to `.ai-flow/reviews/`.

package/prompts/backend/flow-check-test.md

@@ -0,0 +1,14 @@
+---
+description: Internal logic for Testing within flow-check
+---
+
+# AI Flow - Testing Logic
+
+Executes automated tests and analyzes results.
+
+---
+## 🧪 Test Flow
+1. Identify project test runner (detected from `package.json`, etc.).
+2. Execute full suite or targeted tests.
+3. Parse results (Passing/Failing/Coverage).
+4. Update `status.json` validation section.

package/prompts/backend/flow-check.md

@@ -0,0 +1,65 @@
+---
+description: Combined Validation workflow for Tests and Code Review
+---
+
+# AI Flow - Unified Check Workflow
+
+**YOU ARE AN EXPERT QUALITY ASSURANCE AND CODE REVIEW SPECIALIST.**
+
+Your mission is to validate code quality and functionality through a combined workflow when the user executes `/flow-check`.
+
+---
+## Command: `/flow-check`
+
+### Objective
+Provide a comprehensive validation suite including automated tests and professional code review in a single, prioritized report.
+
+---
+## Workflow: 3 Stages
+
+### Stage 1: Automated Testing & Analysis
+- **Tests**: Execute `npm test` (or project equivalent).
+- **Lint**: Execute linting rules.
+- **Types**: Execute type checking (`tsc`).
+- **Update `status.json`**: Record results in `validation` section.
+
+### Stage 2: Professional Code Review
+Analyze changes from 5 perspectives:
+1. **🔒 Security**: SQLi, XSS, Secrets, Auth patterns.
+2. **⚡ Performance**: N+1 queries, memory leaks, blocking ops.
+3. **🧪 Testing**: Coverage, edge cases, test quality.
+4. **📐 Architecture**: SOLID, DRY, Coupling.
+5. **🎨 Code Quality**: Naming, complexity, consistency.
+
+### Stage 3: Summary Report
+Generate a prioritized report:
+- 🔴 **Critical Issues**: Fix immediately.
+- 🟡 **Warnings**: Fix before merge.
+- 🟢 **Suggestions**: Improvement opportunities.
+
+---
+## Integration with `status.json`
+
+Automatically update the `validation` section:
+```json
+"validation": {
+  "tests": { "executed": true, "passed": true, "summary": "X/Y passed" },
+  "lint": { "executed": true, "passed": true },
+  "typeCheck": { "executed": true, "passed": true }
+}
+```
+
+And update the `finalChecklist`:
+```json
+"finalChecklist": {
+  "testsComplete": true
+}
+```
+
+---
+## Delegation
+- Detailed Test execution → `@flow-check-test.md`
+- Detailed Review logic → `@flow-check-review.md`
+
+---
+**BEGIN EXECUTION when user runs `/flow-check`**

package/prompts/backend/flow-commit.md

@@ -0,0 +1,51 @@
+---
+description: Conventional Commits Automation
+---
+
+# AI Flow - Commit Automation
+
+**YOU ARE AN EXPERT GIT WORKFLOW SPECIALIST.**
+
+Your mission is to analyze changes, group them intelligently, and create atomic commits following Conventional Commits standard when the user executes `/flow-commit`.
+
+---
+## Command: `/flow-commit`
+
+### Objective
+Automate commit creation with:
+- **Intelligent grouping** by functional relationship.
+- **Conventional Commits** compliance (type, scope, description).
+- **Atomic commits** (one logical change per commit).
+
+---
+## Workflow: 4 Steps
+
+### Step 1: Detect Changes
+- Modified files (unstaged/staged).
+- **Untracked files** (`git status --porcelain`).
+- Deleted files.
+
+### Step 2: Intelligent Grouping
+Group files by:
+- **Feature Complete**: Entity + Service + Controller + Tests + Docs.
+- **Refactoring**: Helper + Tests + Usages.
+- **Configuration**: Docker, Env, CI/CD.
+- **Independent Tests/Docs**.
+
+### Step 3: Create Commits
+1. Generate Conventional Commit message.
+2. `git add [files] && git commit -m "[message]"`.
+3. **Wait for user confirmation.**
+
+### Step 4: Summary & Push
+- Show `git log` of new commits.
+- Suggest `git push origin [branch]`.
+
+---
+## Integration with `status.json`
+- Update `git.commits` array.
+- Set `git.uncommittedChanges: false` when done.
+- Update `finalChecklist.committed: true`.
+
+---
+**BEGIN EXECUTION when user runs `/flow-commit`**

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

@@ -18,37 +18,43 @@ Detect changes in the codebase compared to the last documented state (stored in
 
 ### Step 1: Check for Analysis File
 
+// turbo
+```bash
+cat .ai-flow/cache/docs-analysis.json
 ```
-First, check if `.ai-flow/cache/docs-analysis.json` exists:
 
 - ✅ If exists → Proceed to Step 2 (Compare Changes)
 - ❌ If NOT exists → Execute full Phase 0 analysis first:
-  - Run complete code analysis (as described in Phase 0)
+  - Run complete code analysis (Project Discovery)
   - Create `.ai-flow/cache/docs-analysis.json` with current state
   - Then proceed to Step 2
-```
 
 ### Step 2: Detect Changes
 
 **Reuse Phase 0 Analysis Logic:**
 
 1. **Perform Current Code Analysis:**
-   - Execute the same analysis as Phase 0 (section 0.1):
-     - File structure analysis
-     - AST-based code parsing (endpoints, entities, dependencies)
-     - Database schema analysis
-     - Pattern detection
+   - Execute project-wide discovery using cross-platform commands:
+     // turbo
+     ```bash
+     ls -R . --exclude-standard
+     ```
+   - Analyze current state for:
+     - File structure and major modules
+     - Interface definitions (API endpoints, CLI commands, RPC methods)
+     - Data structures (Models, Entities, Schemas)
+     - Core dependencies and configuration
    - Generate current state snapshot
 
 2. **Compare with Previous State:**
    - Load `.ai-flow/cache/docs-analysis.json`
    - Compare current state vs previous state
    - Detect changes in:
-     - **Endpoints:** New, modified, or deleted endpoints
-     - **Entities:** New fields, relationships, or deleted entities
-     - **Dependencies:** New libraries, updated versions
-     - **Architecture:** New modules, changed patterns
-     - **Configuration:** New environment variables, external services
+     - **Interfaces:** New, modified, or deleted "entry points" (API, CLI, etc.)
+     - **Data Forms:** New, modified, or deleted core data structures/entities
+     - **Dependencies:** Manifest changes (version bumps, new packages)
+     - **Architecture:** Structural changes (new modules, moved folders)
+     - **Configuration:** New environment keys or external integrations
 
 3. **Generate Change Report:**
    - Categorize changes by type
@@ -63,9 +69,9 @@ First, check if `.ai-flow/cache/docs-analysis.json` exists:
 📊 CAMBIOS DETECTADOS:
 
 🔴 Documentos que requieren actualización:
-- docs/api.md (3 nuevos endpoints en UsersController)
-- docs/data-model.md (campo "email" agregado a User)
-- ai-instructions.md (nueva dependencia "@nestjs/swagger")
+- docs/api.md (3 nuevas rutas en AuthModule)
+- docs/data-model.md (campo "active" agregado a User)
+- ai-instructions.md (nueva dependencia "zod")
 
 ⚠️ Cambios moderados detectados:
 - docs/architecture.md (cambio en estructura de carpetas)
@@ -184,15 +190,15 @@ No se requiere ninguna actualización.
 ✅ DOCUMENTACIÓN ACTUALIZADA:
 
 📝 docs/api.md
-- Agregados 3 nuevos endpoints de UsersController
-- Actualizada sección de autenticación
+- Agregados 3 nuevos puntos de entrada (AuthModule)
+- Actualizada sección de seguridad
 
 📝 docs/data-model.md
-- Agregado campo "email" a entidad User
+- Agregado campo "active" a estructura User
 - Actualizado diagrama ER (mermaid)
 
 📝 ai-instructions.md
-- Agregada dependencia "@nestjs/swagger"
+- Agregada dependencia "zod"
 - Actualizada sección de herramientas
 
 ✅ docs-analysis.json actualizado con nuevo estado
@@ -208,54 +214,48 @@ Actualización cancelada. Ejecuta `/flow-docs-sync` cuando estés listo para act
 ---
 ## Change Detection Rules
 
-### Endpoints Detection
+### Interface Detection (Agnostic)
 
-**What triggers `docs/api.md` update:**
+**What triggers document update (e.g., `docs/api.md`, `README.md`):**
 
-- New `@Controller()`, `@Get()`, `@Post()`, `@Put()`, `@Delete()`, `@Patch()` decorators
-- New `app.get()`, `app.post()`, `router.get()`, etc. (Express)
-- New `@app.get()`, `@app.post()`, `@router.get()` (FastAPI)
-- Modified route paths or methods
-- Deleted endpoints
+- New interface markers (e.g., Decorators like `@Get`, Route definitions like `app.get`, or exported public functions)
+- Modified interface paths, methods, or naming
+- Deleted interfaces
 
 **How to update:**
 
-- Add new endpoints following existing API conventions from Phase 3
-- Use same format, authentication, pagination rules as existing endpoints
-- Maintain all existing endpoints unchanged
+- Add new interfaces following the established patterns in the project
+- Use consistent formatting for parameters, responses, and security
+- Maintain existing documentation for unchanged segments
 
-### Entities Detection
+### Data Structure Detection (Agnostic)
 
-**What triggers `docs/data-model.md` update:**
+**What triggers document update (e.g., `docs/data-model.md`):**
 
-- New `@Entity()` classes (TypeORM)
-- New `model` definitions (Prisma)
-- New `@Column()` fields
-- New relationships (`@OneToMany`, `@ManyToOne`, etc.)
-- Modified field types or constraints
-- Deleted entities or fields
+- New schema definitions (e.g., `class User`, `struct User`, `type User`)
+- New ORM/ODM mappings (e.g., Prisma models, SQL tables, NoSQL schemas)
+- Field changes (additions, deletions, type modifications)
+- Relationship changes (Associations, Foreign Keys, Embedded docs)
 
 **How to update:**
 
-- Add new entities to entity catalog
-- Update entity definitions with new fields
-- Update ER diagram (mermaid) to include new relationships
-- Maintain all existing entities unchanged
+- Update data structure catalog with new definitions
+- Refresh ER diagrams (Mermaid) to reflect new relationships
+- Preserve documentation for unchanged structures
 
-### Dependencies Detection
+### Dependencies Detection (Agnostic)
 
-**What triggers `ai-instructions.md` update:**
+**What triggers update (e.g., `ai-instructions.md`, `package.json`):**
 
-- New entries in `package.json` / `requirements.txt` / `pom.xml` / etc.
-- Updated version numbers
-- New framework or ORM
+- Changes in dependency manifests (package.json, requirements.txt, go.mod, pom.xml, etc.)
+- Significant version updates (+Major or +Minor depending on project)
+- Changes in build systems or package managers
 
 **How to update:**
 
-- Add to dependencies section
-- Update version information
-- Add to tools/libraries list if significant
-- Maintain all existing dependencies
+- Update the tech stack or libraries section
+- Link to new requirements if necessary
+- Maintain information about stable core dependencies
 
 ### Architecture Detection
 
@@ -334,11 +334,11 @@ AI:
 ✅ DOCUMENTACIÓN ACTUALIZADA:
 
 📝 docs/api.md
-- Agregados 2 nuevos endpoints de UsersController (POST/DELETE /users/:id/avatar)
+- Agregados 2 nuevos puntos de entrada (Update/Delete Profile)
 - Mantenida toda la documentación existente
 
 📝 docs/data-model.md
-- Agregado campo "avatarUrl" (String, nullable) a entidad User
+- Agregado campo "display_name" (String, nullable) a estructura User
 - Actualizado diagrama ER (mermaid) con nuevo campo
 
 ✅ docs-analysis.json actualizado con nuevo estado

package/prompts/backend/flow-work-feature.md

@@ -0,0 +1,42 @@
+---
+description: Internal logic for Feature implementation within flow-work
+---
+
+# AI Flow - Feature Logic
+
+This file contains the detailed execution logic for implementing new features, imported by `@flow-work.md`.
+
+---
+## 🚀 Feature Implementation Flow
+
+### 1. Specification (auto-skip if User Story)
+- Extract requirements from User Story or Roadmap.
+- If interactive, ask clarification questions (Multiple Choice).
+- Save to `specs/ai-flow/work/[feature]/spec.md`.
+
+### 2. Technical Planning
+- Analyze codebase for patterns.
+- Generate `plan.md` with Fibonacci estimation.
+- Organize tasks into layers (Data, Logic, API, Test, Docs).
+- **User Confirmation Required.**
+
+### 3. Progressive Implementation
+Choose mode:
+- **Auto**: Complete all tasks without pausing.
+- **Phase-by-phase**: Pause and validate after each phase.
+- **Task-by-task**: Pause after each task.
+
+### 4. Definition of Done (DoD)
+- If HU mode: Validate against Gherkin scenarios.
+- Run tests and linting.
+- Perform security check.
+
+---
+## 🌿 Git Branching Strategy
+- Generate slug from name.
+- Execute `git checkout -b feature/[slug]`.
+- Maintain `status.json` with commit history.
+
+---
+## 📦 status.json Persistence
+Ensure `progress`, `git`, and `metadata` sections are always updated.

package/prompts/backend/flow-work-fix.md

@@ -0,0 +1,33 @@
+---
+description: Internal logic for Bug Fixes within flow-work
+---
+
+# AI Flow - Fix Logic
+
+This file contains the detailed execution logic for bug fixes, imported by `@flow-work.md`.
+
+---
+## 🔧 Bug Fix Workflow
+
+### 1. Classification
+- **QUICK**: 1 file, obvious cause (typo, null check).
+- **COMPLEX**: Multiple files, investigation needed.
+
+### 2. Deep Analysis (Complex Fix)
+- Create work directory.
+- Document root cause in `analysis.md`.
+- Map side effects.
+
+### 3. Implementation
+- **Test-First Approach**: Add a failing test case that reproduces the bug before fixing it.
+- Apply the fix.
+- Verify tests pass.
+
+---
+## 🌿 Git Branching Strategy
+- **QUICK**: Usually work on current branch.
+- **COMPLEX**: Execute `git checkout -b fix/[slug]`.
+
+---
+## 📦 status.json Persistence
+Track root cause details and verification test status.

package/prompts/backend/flow-work-refactor.md

@@ -0,0 +1,32 @@
+---
+description: Internal logic for Refactor implementation within flow-work
+---
+
+# AI Flow - Refactor Logic
+
+This file contains the detailed execution logic for code refactoring, imported by `@flow-work.md`.
+
+---
+## 🔄 Refactoring Workflow
+
+### 1. Scope Identification
+- Map affected files and dependencies.
+- Confirm no behavior change is expected.
+- Validate against architecture patterns.
+
+### 2. Implementation Strategy
+- Use `plan.md` to map extraction/renaming/moving steps.
+- Set "No behavior change" as the primary constraint.
+
+### 3. Execution & Safety
+- Update imports and references across the codebase.
+- **Critical**: Existing tests must pass without modification (unless test itself is refactored).
+- Run `/flow-check` to verify no regressions.
+
+---
+## 🌿 Git Branching Strategy
+- Execute `git checkout -b refactor/[slug]`.
+
+---
+## 📦 status.json Persistence
+Track `percentage` of updated occurrences and updated file paths.

package/prompts/backend/flow-work-resume.md

@@ -0,0 +1,32 @@
+---
+description: Internal logic for Resuming work within flow-work
+---
+
+# AI Flow - Resume Logic
+
+This file contains the logic for detecting and resuming paused work items, imported by `@flow-work.md`.
+
+---
+## ⏸️ Resume Workflow
+
+### 1. Work Detection
+- Scan `specs/ai-flow/work/` for any directories.
+- Group by type and last updated timestamp.
+
+### 2. Selection Menu
+- Show active tasks with percentage and current branch.
+- Identify current Git branch and match with work items (⭐⭐ marker).
+
+### 3. Context Restoration
+- Load `spec.md`, `plan.md`, `task.md`, and `status.json`.
+- Verify Git branch:
+  - If mismatch: Prompt to switch to `git.branchName`.
+- Identify the first incomplete task in `task.md`.
+
+### 4. Implementation Continuation
+- Resume with the previously saved `implementationMode`.
+- Continue execution from where it was paused.
+
+---
+## 📦 status.json Persistence
+Update `timestamps.lastUpdated` upon resuming.