ai-flow-dev 2.1.1 → 2.1.3

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

@@ -59,7 +59,6 @@ Extracting structured information...
 **Extract and analyze:**
 
 1. **Business Context** (from `project-brief.md`):
-
    - Primary objectives
    - Target users
    - Success metrics
@@ -67,48 +66,41 @@ Extracting structured information...
    - Timeline (if specified)
 
 2. **Technical Stack** (from `ai-instructions.md`):
-
    - Language and version
    - Framework and version
    - Database and ORM
    - Key libraries
 
 3. **System Architecture** (from `docs/architecture.md`):
-
    - Architecture pattern (Clean, Hexagonal, Layered, MVC)
    - Layers/modules structure
    - Integration points
    - External services
 
 4. **Data Model** (from `docs/data-model.md`):
-
    - All entities/models
    - Relationships (1:1, 1:N, N:M)
    - Key fields per entity
    - Validation rules
 
 5. **API Endpoints** (from `docs/api.md`):
-
    - All routes
    - HTTP methods
    - Authentication requirements
    - Request/response schemas
 
 6. **Business Flows** (from `docs/business-flows.md`):
-
    - User journeys
    - Critical workflows
    - State transitions
 
 7. **Security Requirements** (from `specs/security.md`):
-
    - Authentication method
    - Authorization strategy (RBAC, ABAC, etc.)
    - Compliance requirements
    - Security features
 
 8. **Testing Strategy** (from `docs/testing.md`):
-
    - Unit test coverage target
    - Integration test scope
    - E2E test scenarios
@@ -796,14 +788,14 @@ With 3 developers: ~9 weeks (47% time savings)
 
 ### Step 9.5: Generate Roadmap Document (2-5 minutes - automatic)
 
-**Generate `roadmap.md` with complete implementation plan:**
+**Generate `docs/roadmap.md` with complete implementation plan:**
 
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 📝 Step 9.5/6: Generating Roadmap Document
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
-Writing to roadmap.md...
+Writing to docs/roadmap.md...
 ```
 
 **Roadmap Document Structure:**
@@ -1167,7 +1159,7 @@ Update this roadmap as you complete features:
 
 ```
 ✅ Roadmap document generated
-✅ Location: roadmap.md
+✅ Location: docs/roadmap.md
 ✅ Total: {{TOTAL_EPICS}} Epics, {{TOTAL_FEATURES}} Features, {{TOTAL_TASKS}} Tasks
 ✅ Estimated: {{TOTAL_SP}} Story Points (~{{TOTAL_WEEKS}} weeks)
 ```
@@ -1192,7 +1184,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: roadmap.md
+✅ Roadmap document: docs/roadmap.md
 
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 🎯 What This Roadmap Guarantees
@@ -1221,14 +1213,14 @@ Update this roadmap as you complete features:
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 1. **Open the roadmap**
-   └─ Open roadmap.md in your editor
+   └─ Open docs/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 roadmap.md
+   └─ git add docs/roadmap.md
    └─ git commit -m "docs: add implementation roadmap with Story Points"
 
 4. **Start implementation**
@@ -1266,7 +1258,7 @@ Update this roadmap as you complete features:
 
 Ready to start building? 🚀
 
-Open roadmap.md and let's ship this! 💪
+Open docs/roadmap.md and let's ship this! 💪
 
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 ```
@@ -1276,16 +1268,20 @@ Open roadmap.md and let's ship this! 💪
 ```
 Would you like to:
 
-A) ✅ Start implementing first feature now (recommended)
-   → Will execute: /feature new "{{FIRST_FEATURE_NAME}}"
+A) 📖 Continue to Phase 10: User Stories (RECOMMENDED)
+   → Generate detailed User Stories with acceptance criteria
+   → Will execute: /flow-build fase 10
+
+B) ✅ Start implementing from roadmap directly
+   → Will execute: /flow-dev-feature {{FIRST_FEATURE_ID}}
 
-B) 📋 Review roadmap first
-   → Will open roadmap.md
+C) 📋 Review roadmap first
+   → Will open docs/roadmap.md
 
-C) ✏️ Customize roadmap
-   → Will open roadmap.md for editing
+D) ✏️ Customize roadmap
+   → Will open docs/roadmap.md for editing
 
-Your choice (A/B/C): __
+Your choice (A/B/C/D): __
 ```
 
 ---
@@ -1297,7 +1293,6 @@ Your choice (A/B/C): __
 The Story Point estimates are based on:
 
 1. **Complexity factors:**
-
    - Number of entities involved
    - Business logic complexity
    - Integration complexity
@@ -1305,7 +1300,6 @@ The Story Point estimates are based on:
    - Security requirements
 
 2. **Historical data:**
-
    - Simple CRUD: 3-5 SP
    - Auth systems: 13-21 SP
    - Payment integrations: 13-21 SP
@@ -1402,7 +1396,7 @@ Please fix documentation and re-run Phase 9
 
 **9.5 Generate Roadmap Document:**
 
-- [ ] Create `roadmap.md`
+- [ ] Create `docs/roadmap.md`
 - [ ] Include project overview
 - [ ] Include Story Points reference table
 - [ ] Include Epic overview table
@@ -1445,7 +1439,6 @@ Please fix documentation and re-run Phase 9
 
 ---
 
-**CONTINUE TO:** End (Phase 9 is the final phase)
-
-**SUCCESS:** Complete implementation roadmap with Story Points generated! Ready to start building! 🚀
+**CONTINUE TO:** Phase 10 (User Stories) - OPTIONAL
 
+**SUCCESS:** Complete implementation roadmap with Story Points generated! Ready to start building or continue to Phase 10 for detailed User Stories! 🚀

package/prompts/backend/flow-build.md

@@ -587,7 +587,7 @@ Read .ai-flow/prompts/backend/flow-build-phase-4-security.md and execute only Ph
 
 **Generates:**
 
-- `.ai-flow/roadmap.md` (complete implementation plan)
+- `docs/roadmap.md` (complete implementation plan)
 
 **Output includes:**
 
@@ -733,12 +733,12 @@ As your project evolves, your documentation may become out of sync with your cod
 
 **How it works:**
 
-1. Compares current code state with last documented state (`.ai-flow/analysis.json`)
+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 `analysis.json` with new state
+6. Updates `docs-analysis.json` with new state
 
 **When to use:**
 

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

@@ -36,17 +36,30 @@ Automate commit creation with:
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 ```
 
+**CRITICAL: Execute ALL detection methods in parallel to catch:**
+
+- Modified files (unstaged/staged)
+- **NEW untracked files** (not detected by get_changed_files)
+- Deleted files
+
 **Execute these tools automatically in parallel (NO user confirmation):**
 
 ```typescript
-// Gather all changes
+// 1. Standard Git Changes (modified/staged files)
 await Promise.all([
   get_changed_files({ sourceControlState: ['unstaged'] }),
   get_changed_files({ sourceControlState: ['staged'] }),
   get_changed_files({}), // All states
 ]);
 
-// Search for modified files by extension
+// 2. CRITICAL: Detect untracked files (new files never added to git)
+await run_in_terminal({
+  command: 'git status --porcelain',
+  explanation: 'Detect untracked files (??), modified (M), added (A), deleted (D)',
+  isBackground: false,
+});
+
+// 3. Search for modified files by extension (backup detection)
 await Promise.all([
   file_search({ query: '**/*.{ts,js,tsx,jsx}', maxResults: 200 }),
   file_search({ query: '**/*.{cs,fs,vb}', maxResults: 200 }),
@@ -54,7 +67,7 @@ await Promise.all([
   file_search({ query: '**/*.{md,json,yaml,yml}', maxResults: 100 }),
 ]);
 
-// Detect code patterns
+// 4. Detect code patterns (helps with grouping)
 await Promise.all([
   grep_search({
     query: 'class|interface|type|struct|enum',
@@ -69,6 +82,41 @@ await Promise.all([
 ]);
 ```
 
+**Parse `git status --porcelain` output:**
+
+```typescript
+// Output format:
+// ?? file.ts       → Untracked (new file)
+// M  file.ts       → Modified (staged)
+//  M file.ts       → Modified (unstaged)
+// A  file.ts       → Added (staged)
+// D  file.ts       → Deleted (staged)
+// ?? src/          → Untracked directory
+
+// Parse logic:
+const parseGitStatus = (output: string) => {
+  const lines = output.split('\n').filter(Boolean);
+  const files = {
+    untracked: [],
+    modified: [],
+    added: [],
+    deleted: [],
+  };
+
+  lines.forEach((line) => {
+    const status = line.slice(0, 2);
+    const filePath = line.slice(3);
+
+    if (status === '??') files.untracked.push(filePath);
+    else if (status.includes('M')) files.modified.push(filePath);
+    else if (status.includes('A')) files.added.push(filePath);
+    else if (status.includes('D')) files.deleted.push(filePath);
+  });
+
+  return files;
+};
+```
+
 **If NO changes detected:**
 
 ```
@@ -84,16 +132,26 @@ Working directory is clean.
 ```
 ✅ Changes detected:
 
-Unstaged: [N] files
-Staged: [N] files
+Untracked: [N] files (new files never added to git)
+Unstaged: [N] files (modified files not staged)
+Staged: [N] files (files ready to commit)
+Deleted: [N] files
 
 File types:
 - Source code: [N] files
 - Tests: [N] files
 - Documentation: [N] files
 - Configuration: [N] files
+
+Examples:
+?? .gitignore (untracked)
+?? src/ (untracked directory)
+ M README.md (modified, unstaged)
+A  package.json (added, staged)
 ```
 
+**IMPORTANT:** Untracked files (`??`) are NEW files that must be detected with `git status --porcelain` because `get_changed_files()` does NOT see them.
+
 ---
 
 ### Step 2: Intelligent Grouping (Automatic)
@@ -503,12 +561,14 @@ Click "Allow" to execute →
 
 Error: [error message]
 
-Suggestions:
-- Run: git pull origin [branch] --rebase
-- Resolve conflicts if any
-- Run: /flow-dev-commit again to retry
-```
+| Step   | Actions                                                                    | User Interaction       |
+| ------ | -------------------------------------------------------------------------- | ---------------------- |
+| Step 1 | `get_changed_files()`, `git status --porcelain`, `file_search()`, `grep_search()` | Automatic (read-only)  |
+| Step 2 | Analyze and group files                                                    | Automatic              |
+| Step 3 | `git add` + `git commit` (per group)                                       | Click Allow per commit |
+| Step 4 | `git log` (automatic) + `git push` (manual)                                | Auto log / Allow push  |
 
+**CRITICAL:** Always run `git status --porcelain` in Step 1 to detect untracked files (`??`) that `get_changed_files()` cannot see.
 ---
 
 ## 🎯 Execution Model
@@ -553,6 +613,7 @@ Universal patterns that work across languages/frameworks:
 **Changes detected:**
 
 ```
+
 src/modules/products/entities/product.entity.ts
 src/modules/products/dto/create-product.dto.ts
 src/modules/products/dto/update-product.dto.ts
@@ -560,16 +621,17 @@ src/modules/products/dto/product-response.dto.ts
 src/modules/products/products.service.ts
 src/modules/products/products.controller.ts
 src/modules/products/products.module.ts
-src/modules/products/__tests__/products.service.spec.ts
-src/modules/products/__tests__/products.controller.spec.ts
+src/modules/products/**tests**/products.service.spec.ts
+src/modules/products/**tests**/products.controller.spec.ts
 docs/api.md (products section)
-```
+
+````
 
 **Commits generated (1 commit):**
 
 ```bash
 git add src/modules/products/entities/product.entity.ts src/modules/products/dto/create-product.dto.ts src/modules/products/dto/update-product.dto.ts src/modules/products/dto/product-response.dto.ts src/modules/products/products.service.ts src/modules/products/products.controller.ts src/modules/products/products.module.ts src/modules/products/__tests__/products.service.spec.ts src/modules/products/__tests__/products.controller.spec.ts docs/api.md && git commit -m "feat(products): implement product management with CRUD operations"
-```
+````
 
 ### Example 2: Refactoring Across Modules