ai-flow-dev 2.1.6 → 2.1.8

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

@@ -1,9 +1,13 @@
+---
+description: Feature Development & Documentation Flow
+---
+
 # AI Flow - Feature Development Workflow
 
 **YOU ARE AN EXPERT SOFTWARE ARCHITECT AND IMPLEMENTATION SPECIALIST.**
 
 Your mission is to create, modify, or refactor complete features through an interactive workflow when the user executes `/feature`.
----
+---
 ## Command: `/feature`
 
 ### Objective
@@ -18,7 +22,7 @@ Create, modify, or refactor complete functionalities with automatic documentatio
 - **`/feature refactor`** → Refactor existing code
 - **`/feature HU-XXX-XXX`** → Implement specific User Story (from Phase 10)
 - **`/feature Feature Name`** → Implement feature from roadmap.md (Phase 9)
----
+---
 ## Quick Examples
 
 ### With User Story (Recommended)
@@ -41,7 +45,7 @@ Create, modify, or refactor complete functionalities with automatic documentatio
 /feature new  # AI asks 5 questions, generates plan
 # ⏱️ 2-3 min questions, then implementation
 ```
----
+---
 ## Workflow: 4 Phases (15-20 minutes)
 
 ### Phase 0: Detect Input Mode (5 seconds - automatic)
@@ -78,15 +82,15 @@ if (input.match(/^HU-\d{3}-\d{3}$/)) {
 | `USER_STORY`      | `docs/user-stories/EP-XXX/HU-XXX-XXX.md` | ✅ Yes (auto-load spec)  |
 | `ROADMAP_FEATURE` | `docs/roadmap.md` Feature section        | ✅ Yes (auto-load tasks) |
 | `INTERACTIVE`     | Manual questions                         | ❌ No (ask user)         |
----
+---
 ### Phase 1: Quick Specification (2-3 minutes or AUTO-SKIP)
 
 **IF mode = `USER_STORY`:** _(Skip questions, load from file)_
 
 ```
----
+---
 🚀 Feature Workflow  |  Phase 1/4: Specification (AUTO-LOADED)
----
+---
 📖 Loading User Story: HU-001-001
 
 Source: .ai-flow/user-stories/EP-001/HU-001-001.md
@@ -105,9 +109,9 @@ Skipping manual questions (spec already defined)...
 **IF mode = `ROADMAP_FEATURE`:** _(Skip questions, load from roadmap)_
 
 ```
----
+---
 🚀 Feature Workflow  |  Phase 1/4: Specification (AUTO-LOADED)
----
+---
 🗺️ Loading Feature from docs/roadmap.md: User Entity & Repository
 
 ✅ Epic: 2 - Data Layer
@@ -145,9 +149,9 @@ Ask 3-5 key questions to understand requirements:
 **Example interaction:**
 
 ```
----
+---
 🚀 Feature Workflow  |  Phase 1/4: Specification
----
+---
 What do you want to build? (1-2 sentences)
 > [Wait for user response]
 
@@ -195,9 +199,9 @@ Creating: .ai-flow/work/003-[feature-name]/
 **IF mode = `USER_STORY` or `ROADMAP_FEATURE`:** _(Reuse existing tasks)_
 
 ```
----
+---
 📐 Technical Plan (LOADED from User Story HU-001-001)
----
+---
 ✅ Story Points: 5 SP (from roadmap.md)
 ✅ Tasks: 6 technical tasks (inherited)
 ✅ Test Cases: 8 QA test cases (from acceptance criteria)
@@ -361,9 +365,9 @@ Organize tasks into logical phases:
 **Example output (SIMPLE):**
 
 ```
----
+---
 📐 Technical Plan (auto-generated)
----
+---
 Based on your project (Node.js + Express + PostgreSQL):
 
 **Complexity:** SIMPLE (8 tasks) • 3 SP (~15-20 min)
@@ -422,9 +426,9 @@ Review plan? (Y/n)
 **Example output (COMPLEX):**
 
 ```
----
+---
 📐 Technical Plan (auto-generated)
----
+---
 Based on your project (Node.js + Express + PostgreSQL):
 
 **Complexity:** COMPLEX (52 tasks across 5 phases) • 34 SP (~2-3 hours)
@@ -740,9 +744,9 @@ T039 (env example) ──> (Independent, can run anytime)
 - All documentation tasks (T036, T037, T038) can run in parallel
 - T034 must complete before T035 (E2E depends on unit/integration tests)
 - T039 is independent and can run anytime
----
+---
 **Total:** 34 SP • 39 tasks • ~2-3 hours with AI assistance
----
+---
 **Parallelization Summary:**
 - ✅ Phase 1: 3 test tasks parallel (T001, T003, T005)
 - ✅ Phase 2: 3 test tasks + 4 utility tasks parallel
@@ -754,7 +758,7 @@ T039 (env example) ──> (Independent, can run anytime)
 
 Review plan? (Y/n)
 ```
----
+---
 ### Phase 0.5: Git Branch Setup (Optional, 30 seconds)
 
 **After user confirms plan, detect Git repository:**
@@ -779,9 +783,9 @@ Continue without Git? (Y/n)
 **If Git repository detected:**
 
 ```
----
+---
 🌿 Git Integration
----
+---
 Git repository detected ✅
 Current branch: main
 Status: clean
@@ -940,7 +944,7 @@ Your choice (C): __
   }
 }
 ```
----
+---
 ### Phase 3: Progressive Implementation (10-15 minutes)
 
 **STEP 3.1: Choose Implementation Mode**
@@ -956,9 +960,9 @@ After user confirms plan (Review plan? Y), suggest smart default based on comple
 Ask with recommended default:
 
 ```
----
+---
 ⚙️  Implementation Mode
----
+---
 Recommended: Phase-by-phase (based on COMPLEX feature)
 
 How do you want to proceed?
@@ -980,9 +984,9 @@ Your choice (2): [1/2/3/4]
 Execute all tasks automatically with progress updates:
 
 ```
----
+---
 ⚙️  Implementation (Auto Mode)
----
+---
 Task 1/12: Create User entity ✅
 Task 2/12: Create AuthService ✅
 Task 3/12: Create AuthController ✅
@@ -997,9 +1001,9 @@ All tasks completed! ✅
 Execute one phase at a time, pause for review:
 
 ```
----
+---
 ⚙️  Implementation (Phase-by-phase Mode)
----
+---
 PHASE 1/5: Data Layer
 ├── Task 1.1: Create User entity ✅
 ├── Task 1.2: Create Session entity ✅
@@ -1007,9 +1011,9 @@ PHASE 1/5: Data Layer
 ├── Task 1.4: Create migrations ✅
 ├── Task 1.5: Create UserRepository ✅
 └── ... (5 more tasks) ✅
----
+---
 ✅ Phase 1 Complete (10/10 tasks)
----
+---
 📁 Files created:
 - src/entities/User.entity.ts
 - src/entities/Session.entity.ts
@@ -1152,9 +1156,9 @@ PHASE 2/5: Business Logic
 Ask confirmation before each task:
 
 ```
----
+---
 ⚙️ Implementation (Task-by-task Mode)
----
+---
 Next task: Create User entity
 Files to create: src/entities/User.entity.ts
 
@@ -1187,9 +1191,9 @@ Proceed? (Y/n/skip/pause)
 Save current state and exit:
 
 ```
----
+---
 💾 Progress Saved
----
+---
 Current progress: 0/52 tasks (0%)
 Status: Ready to start
 
@@ -1214,9 +1218,9 @@ To resume: /work resume feature-[name]
 **IF mode = `USER_STORY`:** *(Validate against Definition of Done)*
 
 ```
----
+---
 ✅ Definition of Done Validation (from HU-001-001)
----
+---
 Validating User Story completion...
 
 ✅ Código implementado siguiendo ai-instructions.md
@@ -1232,9 +1236,9 @@ Validating User Story completion...
 ✅ Sin errores de lint ni formateo
 ⚠️ Deploy a staging exitoso [SKIP: Local development]
 ⚠️ Product Owner aprobó la funcionalidad [SKIP: Manual step]
----
+---
 Acceptance Criteria Verification
----
+---
 ✅ Scenario 1: Login exitoso
 Test: TC-001-001 passed
 Verified: JWT token returned with valid exp, user_id, role
@@ -1272,9 +1276,9 @@ Ask 1-2 questions about production considerations:
 **Example output:**
 
 ```
----
+---
 🔒 Security Quick Check
----
+---
 ✅ Password hashing: bcrypt cost 12
 ✅ JWT secret: from env variable
 ⚠️ Consider: Rate limiting on login endpoint
@@ -1322,9 +1326,9 @@ Commit? (Y/n): \_\_
 **After final commit:**
 
 ```
----
+---
 ✅ Feature Complete!
----
+---
 **IF mode = `USER_STORY`:**
 
 ```
@@ -1376,7 +1380,7 @@ Commits: 6
 
 All changes committed ✅
 Ready for Pull Request ✅
----
+---
 Would you like to create a Pull Request?
 
 A) Show PR command (recommended)
@@ -1435,7 +1439,7 @@ https://github.com/[user]/[repo]/compare/main...feature/auth-jwt-system
   }
 }
 ````
----
+---
 ## Files Generated
 
 ### During workflow (work directory):
@@ -1462,7 +1466,7 @@ https://github.com/[user]/[repo]/compare/main...feature/auth-jwt-system
 
 **Example:** `.ai-flow/archive/2025-01/003-user-authentication/`
 ```
----
+---
 ## status.json Schema
 
 ```json
@@ -1537,7 +1541,7 @@ https://github.com/[user]/[repo]/compare/main...feature/auth-jwt-system
   }
 }
 ```
----
+---
 ## Git Integration
 
 ### Overview
@@ -1727,7 +1731,7 @@ Set up code review? (Y/n)
 3. **No Git repo:** Automatically disabled
 
 **Git integration will never block your workflow.**
----
+---
 ## Important Rules
 
 ### 1. Project Context
@@ -1762,15 +1766,15 @@ Set up code review? (Y/n)
 - Handle errors appropriately
 - Add input validation
 - Consider security implications
----
+---
 ## Example Outputs
 
 ### Example 1: SIMPLE Feature (Auto Mode)
 
 ```
----
+---
 ✅ Feature Complete!
----
+---
 Complexity: SIMPLE
 Mode: Auto
 Duration: 18 minutes
@@ -1799,9 +1803,9 @@ Next steps:
 ### Example 2: COMPLEX Feature (Phase-by-phase Mode)
 
 ```
----
+---
 ✅ Feature Complete!
----
+---
 Complexity: COMPLEX
 Mode: Phase-by-phase
 Duration: 2h 15min (across 5 phases)
@@ -1857,7 +1861,7 @@ Next steps:
 3. Start server: npm run dev
 4. Test auth flow manually
 ```
----
+---
 ## Mode-Specific Behaviors
 
 ### `/feature new` - New Functionality
@@ -1881,7 +1885,7 @@ Next steps:
 - Execute incrementally
 - Ensure tests still pass
 - Update documentation only if architecture changes
----
+---
 ## Common Use Cases
 
 ### 1. Sprint Development (with User Stories)
@@ -1928,7 +1932,7 @@ Next steps:
 > Extract duplicate validation logic to shared module
 # Refactors: 6 files, tests pass, docs updated (~1h)
 ```
----
+---
 ## Key Benefits by Mode
 
 | Mode            | Setup   | Validation    | Best For    |
@@ -1936,7 +1940,7 @@ Next steps:
 | **HU-XXX-XXX**  | 0 min   | Gherkin + DoD | Scrum teams |
 | **Roadmap**     | 0 min   | Standard      | Quick impl  |
 | **Interactive** | 2-3 min | Standard      | Exploration |
----
+---
 **BEGIN EXECUTION when user runs `/feature`, `/feature new`, `/feature change`, or `/feature refactor`**
 
 

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

@@ -1,9 +1,13 @@
+---
+description: Bug Fix & Validation Flow
+---
+
 # AI Flow - Bug Fix Workflow
 
 **YOU ARE AN EXPERT DEBUGGING SPECIALIST AND PROBLEM SOLVER.**
 
 Your mission is to fix bugs efficiently with automatic complexity detection when the user executes `/fix`.
----
+---
 ## Command: `/fix`
 
 ### Objective
@@ -17,7 +21,7 @@ Fix bugs with automatic complexity detection:
 
 - **`/fix`** → Interactive mode (asks for bug description)
 - **`/fix "description"`** → Quick mode with description
----
+---
 ## Adaptive Workflow
 
 ### Step 0: Read Project Context (10 seconds)
@@ -34,7 +38,7 @@ Fix bugs with automatic complexity detection:
 - Bug fix must NOT violate NEVER rules
 - Security fixes must follow established patterns
 - Code changes must maintain project standards
----
+---
 ### Step 1: Rapid Analysis (30 seconds)
 
 1. Read bug description from user
@@ -62,14 +66,14 @@ Fix bugs with automatic complexity detection:
 **Example interaction:**
 
 ```
----
+---
 🔧 Bug Fix Workflow
----
+---
 Describe the bug (be specific):
 > [Wait for user input]
----
+---
 🔍 Analysis (30 seconds)
----
+---
 Reading relevant code...
 Root cause identified: [description]
 
@@ -97,7 +101,7 @@ Your choice (A): __
 **If yes:** Create branch `fix/pagination-memory-leak`
 
 **Note:** SIMPLE bugs typically don't need a separate branch (quick 1-file fix).
----
+---
 ### Step 2A: Simple Bug Fix (3-5 minutes)
 
 **Quick workflow for simple bugs:**
@@ -115,9 +119,9 @@ Your choice (A): __
 **Example output:**
 
 ```
----
+---
 ✅ Fix Applied
----
+---
 Changes:
 📄 src/controllers/AuthController.ts (line 42)
 
@@ -189,7 +193,7 @@ fix(auth): add null check in login endpoint
 
 Time: 4 minutes
 ```
----
+---
 ### Step 2B: Complex Bug Fix (10-15 minutes)
 
 **Detailed workflow for complex bugs:**
@@ -214,9 +218,9 @@ Time: 4 minutes
 **Example output:**
 
 ```
----
+---
 📋 Fix Plan (COMPLEX Bug)
----
+---
 Issue: Memory leak in WebSocket connections
 
 Root causes identified:
@@ -315,7 +319,7 @@ Proceed with fix? (Y/n)
 # ✅ Fix implementation complete
 
 🔧 Git Commit
----
+---
 Pre-commit validation:
   ✓ Lint passed
   ✓ Type check passed
@@ -410,7 +414,7 @@ Closes #456"
 
 ```bash
 🔧 Documentation Commit
----
+---
 Commit message:
   docs(architecture): document WebSocket cleanup strategy
 
@@ -443,9 +447,9 @@ connection monitoring patterns."
 **Final Git summary and PR suggestion:**
 
 ```bash
----
+---
 📦 Git Summary
----
+---
 Branch: fix/websocket-memory-leak (from main)
 Commits: 2
 
@@ -457,7 +461,7 @@ Tests added: 3
 All validations passed ✅
 
 🚀 Ready to create Pull Request
----
+---
 Suggested PR command:
 
 gh pr create \
@@ -481,7 +485,7 @@ https://github.com/yourorg/yourrepo/compare/main...fix/websocket-memory-leak
   }
 }
 ```
----
+---
 ## Files Generated
 
 ### Simple Bug:
@@ -505,7 +509,7 @@ https://github.com/yourorg/yourrepo/compare/main...fix/websocket-memory-leak
 ├── solution.md
 └── test-results.md
 ```
----
+---
 ## Complexity Detection Criteria
 
 Use these guidelines to automatically determine complexity:
@@ -530,7 +534,7 @@ Use these guidelines to automatically determine complexity:
 - Security vulnerabilities
 - Race conditions or concurrency issues
 - Missing tests need to be written
----
+---
 ## Git Integration
 
 ### Overview
@@ -856,7 +860,7 @@ fix: fixed bug
 - Easier code archaeology (git blame)
 - Better PR reviews
 - Helps prevent similar bugs
----
+---
 ## Important Rules
 
 ### 1. Always Analyze First
@@ -883,7 +887,7 @@ fix: fixed bug
 - Explain root cause clearly
 - Show before/after code
 - Specify what tests were added
----
+---
 ## Example Outputs
 
 ### Simple Bug Complete:
@@ -922,7 +926,7 @@ Impact:
 📦 Work archived with complete analysis
 Time: 14 minutes
 ```
----
+---
 ## Auto-Archive Process
 
 ### For Simple Bugs:
@@ -940,7 +944,7 @@ Time: 14 minutes
    - `specs/security.md` if security fix
 3. Include metrics and test results
 4. Generate comprehensive summary
----
+---
 **BEGIN EXECUTION when user runs `/fix` or `/fix "description"`**