ai-flow-dev 2.5.4 → 2.7.0

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

@@ -1,61 +1,61 @@
----
-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. Context Analysis (auto-skip if User Story with detailed tasks)
-
-- Extract requirements from User Story or Roadmap
-- If User Story has detailed tasks: Skip to work.md generation
-- If Roadmap or Manual: Analyze and refine
-- Read relevant documentation (ai-instructions.md, architecture.md, etc.)
-
-### 2. work.md Generation
-
-- Generate consolidated work.md (see Phase 2 in flow-work.md)
-- Include: Context, Objective, Constraints, Approach, Tasks, Validation
-- **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
-
-Follow tasks in `work.md`:
-
-- Update checkboxes as completed
-- Update `status.json` progress
-- Follow patterns and constraints specified
-
-### 4. Definition of Done (DoD)
-
-- If HU mode: Validate against Gherkin scenarios
-- Run tests and linting
-- Perform security check
-- **Update completion status** in source documents (see Phase 4 in flow-work.md)
-
----
-
-## 🌿 Git Branching Strategy
-
-- Generate slug from name
-- Execute `git checkout -b feature/[slug]`
-- **Note:** Creating feature branches FROM `main`/`master`/`develop`/`development` is correct workflow
-- **Never commit directly TO protected branches** - always work on feature branch
-- Maintain `status.json` with commit history
-
----
-
-## 📦 status.json Persistence
-
-Ensure `progress`, `git`, and `metadata` sections are always updated.
+---
+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. Context Analysis (auto-skip if User Story with detailed tasks)
+
+- Extract requirements from User Story or Roadmap
+- If User Story has detailed tasks: Skip to work.md generation
+- If Roadmap or Manual: Analyze and refine
+- Read relevant documentation (ai-instructions.md, architecture.md, etc.)
+
+### 2. work.md Generation
+
+- Generate consolidated work.md (see Phase 2 in flow-work.md)
+- Include: Context, Objective, Constraints, Approach, Tasks, Validation
+- **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
+
+Follow tasks in `work.md`:
+
+- Update checkboxes as completed
+- Update `status.json` progress
+- Follow patterns and constraints specified
+
+### 4. Definition of Done (DoD)
+
+- If HU mode: Validate against Gherkin scenarios
+- Run tests and linting
+- Perform security check
+- **Update completion status** in source documents (see Phase 4 in flow-work.md)
+
+---
+
+## 🌿 Git Branching Strategy
+
+- Generate slug from name
+- Execute `git checkout -b feature/[slug]`
+- **Note:** Creating feature branches FROM `main`/`master`/`develop`/`development` is correct workflow
+- **Never commit directly TO protected branches** - always work on feature branch
+- 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

@@ -1,46 +1,46 @@
----
-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. Analysis & work.md Generation
-
-- **QUICK**: Minimal work.md (objective + 1-2 tasks)
-- **COMPLEX**: Full work.md with root cause analysis
-  - Document root cause in Objective section
-  - Map side effects in Approach section
-  - Generate detailed tasks
-
-### 3. Implementation
-
-- **Test-First Approach**: Add failing test that reproduces bug
-- Apply the fix following work.md tasks
-- Verify tests pass
-- **Update completion status** if fix was tracked in roadmap/user stories (see Phase 4 in flow-work.md)
-
----
-
-## 🌿 Git Branching Strategy
-
-- **QUICK**: Usually work on current branch
-  - ⚠️ **Exception:** If on protected branch (`main`, `master`, `develop`, `development`), create fix branch even for quick fixes
-- **COMPLEX**: Execute `git checkout -b fix/[slug]`
-- **Never commit directly TO protected branches**
-
----
-
-## 📦 status.json Persistence
-
-Track root cause details and verification test status.
+---
+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. Analysis & work.md Generation
+
+- **QUICK**: Minimal work.md (objective + 1-2 tasks)
+- **COMPLEX**: Full work.md with root cause analysis
+  - Document root cause in Objective section
+  - Map side effects in Approach section
+  - Generate detailed tasks
+
+### 3. Implementation
+
+- **Test-First Approach**: Add failing test that reproduces bug
+- Apply the fix following work.md tasks
+- Verify tests pass
+- **Update completion status** if fix was tracked in roadmap/user stories (see Phase 4 in flow-work.md)
+
+---
+
+## 🌿 Git Branching Strategy
+
+- **QUICK**: Usually work on current branch
+  - ⚠️ **Exception:** If on protected branch (`main`, `master`, `develop`, `development`), create fix branch even for quick fixes
+- **COMPLEX**: Execute `git checkout -b fix/[slug]`
+- **Never commit directly TO protected branches**
+
+---
+
+## 📦 status.json Persistence
+
+Track root cause details and verification test status.

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

@@ -1,48 +1,48 @@
----
-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 & work.md Generation
-
-- Map affected files and dependencies
-- Confirm no behavior change expected
-- Validate against architecture patterns
-- Generate work.md with:
-  - Clear scope (what to extract/move/rename)
-  - Affected files list
-  - Step-by-step tasks
-  - "No behavior change" constraint
-
-### 2. Implementation
-
-- Follow work.md tasks sequentially
-- Update imports and references across codebase
-- **Critical**: Existing tests must pass without modification (unless test itself is refactored)
-
-### 3. Validation
-
-- Run `/flow-check` to verify no regressions
-- Confirm all tests pass
-- **Update completion status** if refactor was tracked in roadmap/user stories (see Phase 4 in flow-work.md)
-
----
-
-## 🌿 Git Branching Strategy
-
-- Execute `git checkout -b refactor/[slug]`
-- **Note:** Creating refactor branches FROM `main`/`master`/`develop`/`development` is correct
-- **Never commit directly TO protected branches**
-
----
-
-## 📦 status.json Persistence
-
-Track `percentage` of updated occurrences and updated file paths.
+---
+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 & work.md Generation
+
+- Map affected files and dependencies
+- Confirm no behavior change expected
+- Validate against architecture patterns
+- Generate work.md with:
+  - Clear scope (what to extract/move/rename)
+  - Affected files list
+  - Step-by-step tasks
+  - "No behavior change" constraint
+
+### 2. Implementation
+
+- Follow work.md tasks sequentially
+- Update imports and references across codebase
+- **Critical**: Existing tests must pass without modification (unless test itself is refactored)
+
+### 3. Validation
+
+- Run `/flow-check` to verify no regressions
+- Confirm all tests pass
+- **Update completion status** if refactor was tracked in roadmap/user stories (see Phase 4 in flow-work.md)
+
+---
+
+## 🌿 Git Branching Strategy
+
+- Execute `git checkout -b refactor/[slug]`
+- **Note:** Creating refactor branches FROM `main`/`master`/`develop`/`development` is correct
+- **Never commit directly TO protected branches**
+
+---
+
+## 📦 status.json Persistence
+
+Track `percentage` of updated occurrences and updated file paths.

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

@@ -1,34 +1,34 @@
----
-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 `.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 `work.md` and `status.json`
-- Verify Git branch:
-  - If mismatch: Prompt to switch to `git.branchName`
-- Identify the first incomplete task in `work.md`
-- Read Documentation Constraints section to refresh context
-
-### 4. Implementation Continuation
-- Resume with the previously saved `implementationMode`
-- Continue execution from where it was paused
-- Follow remaining tasks in `work.md`
-
----
-## 📦 status.json Persistence
-Update `timestamps.lastUpdated` upon resuming.
+---
+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 `.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 `work.md` and `status.json`
+- Verify Git branch:
+  - If mismatch: Prompt to switch to `git.branchName`
+- Identify the first incomplete task in `work.md`
+- Read Documentation Constraints section to refresh context
+
+### 4. Implementation Continuation
+- Resume with the previously saved `implementationMode`
+- Continue execution from where it was paused
+- Follow remaining tasks in `work.md`
+
+---
+## 📦 status.json Persistence
+Update `timestamps.lastUpdated` upon resuming.