ai-flow-dev 2.5.3 → 2.6.0

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

@@ -0,0 +1,439 @@
+## PHASE 9: Implementation Roadmap (5-10 min)
+
+> **Order for this phase:** OPTIONAL. Executed after Phase 8 or on demand.
+
+### Objective
+
+Translate all desktop application specifications into a prioritized, actionable implementation plan (Roadmap) with clear milestones and atomic tasks.
+
+---
+
+## Context Variables (Extract from docs)
+
+```
+From ai-instructions.md:
+├── LANG: Java
+├── EXT: .java
+├── SRC: src/main/java or src/
+├── TESTS: src/test/java or test/
+├── RESOURCES: src/main/resources or resources/
+└── ARCH: MVC / MVP / MVVM
+
+From docs/ARCHITECTURE.md:
+├── MODEL_DIR: model/ or domain/
+├── VIEW_DIR: view/ or ui/
+├── CONTROLLER_DIR: controller/ or presenter/
+├── SERVICE_DIR: service/
+├── DAO_DIR: dao/ or repository/
+├── UTIL_DIR: util/
+└── PKG_BASE: com.company.app
+```
+
+---
+
+## Task Format (MANDATORY)
+
+```
+- [ ] TXXX [CAT] Description • 1 SP → {{path}} | deps: TXXX
+```
+
+**Components:**
+
+- `TXXX` - Sequential ID (T001, T002...)
+- `[CAT]` - Category (see below)
+- `Description` - Specific action
+- `1 SP` - Story Points (1 or 2 only)
+- `→ {{path}}` - Target file path
+- `deps: TXXX` - Dependencies
+
+---
+
+## Categories [CAT]
+
+| Cat | Name       | Description                     | SP Range |
+| --- | ---------- | ------------------------------- | -------- |
+| [M] | Model      | Entities, data classes          | 1 SP     |
+| [V] | View       | UI components, windows, dialogs | 1-2 SP   |
+| [C] | Controller | Event handlers, presenters      | 1-2 SP   |
+| [S] | Service    | Business logic, services        | 1-2 SP   |
+| [D] | DAO        | Data access, repositories       | 1 SP     |
+| [T] | Test       | Unit, integration, UI tests     | 1-2 SP   |
+| [U] | UI/UX      | Layouts, styling, resources     | 1 SP     |
+| [I] | Infra      | Build, packaging, deployment    | 1-2 SP   |
+| [X] | Docs       | Documentation updates           | 1 SP     |
+
+---
+
+## Atomic Task Rules
+
+**Maximum 1-2 SP per task:**
+
+**BAD:**
+
+```
+- [ ] T001 [V] Create Main Window with all components • 5 SP
+```
+
+**GOOD:**
+
+```
+- [ ] T001 [V] Create MainWindow class skeleton • 1 SP → {{SRC}}/{{VIEW_DIR}}/MainWindow{{EXT}} | deps: none
+- [ ] T002 [U] Add MainWindow layout (BorderLayout) • 1 SP → {{SRC}}/{{VIEW_DIR}}/MainWindow{{EXT}} | deps: T001
+- [ ] T003 [U] Add MainWindow menu bar (File, Edit, Help) • 1 SP → {{SRC}}/{{VIEW_DIR}}/MainWindow{{EXT}} | deps: T002
+- [ ] T004 [U] Add MainWindow toolbar (New, Open, Save) • 1 SP → {{SRC}}/{{VIEW_DIR}}/MainWindow{{EXT}} | deps: T002
+- [ ] T005 [U] Add MainWindow status bar • 1 SP → {{SRC}}/{{VIEW_DIR}}/MainWindow{{EXT}} | deps: T002
+```
+
+---
+
+## Workflow: 6 Steps
+
+### Step 9.1: Extract Context & Inventory
+
+**1. Extract context variables:**
+
+```
+CONTEXT EXTRACTED
+├── Language: Java 17
+├── Extension: .java
+├── Source dir: src/main/java/
+├── Tests dir: src/test/java/
+├── Resources: src/main/resources/
+├── Architecture: MVC
+├── Model path: model/
+├── View path: view/
+├── Controller path: controller/
+├── Service path: service/
+└── DAO path: dao/
+```
+
+**2. Extract inventory from documentation:**
+
+**From Phase 1 (project-brief.md):**
+
+```
+WINDOWS:
+| Window           | Type   | Complexity |
+|------------------|--------|------------|
+| MainWindow       | Frame  | Complex    |
+| SettingsDialog   | Dialog | Medium     |
+| AboutDialog      | Dialog | Simple     |
+```
+
+**From Phase 2 (docs/ARCHITECTURE.md):**
+
+```
+MODELS:
+| Model    | Fields | Relations | Complexity |
+|----------|--------|-----------|------------|
+| User     | 5      | None      | Simple     |
+| Project  | 8      | 1:N       | Medium     |
+| Task     | 6      | N:1       | Medium     |
+```
+
+**From Phase 4:**
+
+```
+DATA ACCESS:
+| Entity  | CRUD | Search | Complexity |
+|---------|------|--------|------------|
+| User    | Yes  | Email  | Simple     |
+| Project | Yes  | Name   | Medium     |
+| Task    | Yes  | Status | Medium     |
+```
+
+**Show summary:**
+
+```
+INVENTORY COMPLETE
+├── UI Framework: Swing / JavaFX / SWT
+├── Windows: 3 (simple: 1, medium: 1, complex: 1)
+├── Models: 3 (simple: 1, medium: 2)
+├── Data Access: 3 entities with CRUD
+├── Build: Maven / Gradle / Ant
+└── Estimated tasks: 150-200
+```
+
+---
+
+### Step 9.2: Epic Definition
+
+**Standard Epic Structure for Desktop:**
+
+```
+EP-001: Foundation (ALWAYS FIRST)
+├── Build setup (Maven/Gradle/Ant)
+├── Main class, application launcher
+├── Logging, error handling
+├── Database connection (if applicable)
+└── Priority: P0 | Duration: Week 1
+
+EP-002: Data Layer
+├── Entity classes (models)
+├── DAO/Repository interfaces
+├── Database schema (if applicable)
+├── Unit tests for data layer
+└── Priority: P0 | Duration: Week 1-2
+
+EP-003: Business Logic
+├── Service classes
+├── Business rules, validation
+├── Unit tests for services
+└── Priority: P0 | Duration: Week 2-3
+
+EP-004: UI Foundation
+├── Main window skeleton
+├── Layout management
+├── Menu bar, toolbar, status bar
+├── Application theme/LAF
+└── Priority: P0 | Duration: Week 2-3
+
+EP-005: UI Components
+├── Forms, dialogs
+├── Tables, lists, trees
+├── Custom components
+├── UI event handling
+└── Priority: P1 | Duration: Week 3-4
+
+EP-006: Controllers/Presenters
+├── UI controllers
+├── Event handlers
+├── Data binding (MVVM)
+├── UI tests
+└── Priority: P1 | Duration: Week 4
+
+EP-007: Features
+├── Specific features (search, export, etc.)
+├── Integration with services
+├── Feature tests
+└── Priority: P1 | Duration: Week 5
+
+EP-008: Packaging & Deployment
+├── Executable JAR
+├── Native packaging (jpackage)
+├── Installers
+├── Code signing
+└── Priority: P2 | Duration: Week 6
+```
+
+---
+
+### Step 9.3: Task Generation
+
+**Example for EP-001 (Foundation):**
+
+```markdown
+## Epic 1: Foundation • 15 SP
+
+**Goal:** Set up build system, main class, and basic infrastructure.
+
+**Estimated Duration:** 3-5 days
+
+### Tasks
+
+#### Build Setup (3 SP)
+
+- [ ] T001 [I] Create pom.xml with Java 17 config • 1 SP → pom.xml | deps: none
+- [ ] T002 [I] Add UI framework dependency (Swing/JavaFX/SWT) • 1 SP → pom.xml | deps: T001
+- [ ] T003 [I] Add database dependency (H2/Derby) if needed • 1 SP → pom.xml | deps: T001
+
+#### Application Launcher (4 SP)
+
+- [ ] T004 [C] Create Main class with main() method • 1 SP → {{SRC}}/{{PKG_BASE}}/Main{{EXT}} | deps: T002
+- [ ] T005 [C] Initialize UI thread (SwingUtilities/Platform.runLater) • 1 SP → {{SRC}}/{{PKG_BASE}}/Main{{EXT}} | deps: T004
+- [ ] T006 [C] Set Look and Feel (FlatLaf/Modena) • 1 SP → {{SRC}}/{{PKG_BASE}}/Main{{EXT}} | deps: T004
+- [ ] T007 [T] Add Main class unit test • 1 SP → {{TESTS}}/{{PKG_BASE}}/MainTest{{EXT}} | deps: T004
+
+#### Infrastructure (4 SP)
+
+- [ ] T008 [S] Create Logger utility class • 1 SP → {{SRC}}/{{PKG_BASE}}/{{UTIL_DIR}}/Logger{{EXT}} | deps: none
+- [ ] T009 [S] Create ConfigManager for properties • 1 SP → {{SRC}}/{{PKG_BASE}}/{{UTIL_DIR}}/ConfigManager{{EXT}} | deps: none
+- [ ] T010 [S] Create global exception handler • 1 SP → {{SRC}}/{{PKG_BASE}}/{{UTIL_DIR}}/ExceptionHandler{{EXT}} | deps: T008
+- [ ] T011 [T] Add utility tests • 1 SP → {{TESTS}}/{{PKG_BASE}}/util/ | deps: T008,T009,T010
+
+#### Database Setup (4 SP, if applicable)
+
+- [ ] T012 [D] Create DatabaseManager class • 1 SP → {{SRC}}/{{PKG_BASE}}/{{DAO_DIR}}/DatabaseManager{{EXT}} | deps: T003
+- [ ] T013 [D] Implement connection pooling • 1 SP → {{SRC}}/{{PKG_BASE}}/{{DAO_DIR}}/DatabaseManager{{EXT}} | deps: T012
+- [ ] T014 [D] Create schema.sql (DDL) • 1 SP → {{RESOURCES}}/schema.sql | deps: none
+- [ ] T015 [T] Add DatabaseManager tests • 1 SP → {{TESTS}}/{{PKG_BASE}}/dao/DatabaseManagerTest{{EXT}} | deps: T012
+```
+
+---
+
+### Step 9.4: Generate planning/roadmap.md
+
+**File structure:**
+
+````markdown
+# Implementation Roadmap
+
+**Project:** [Project Name]
+**Type:** Desktop Application (Java)
+**UI Framework:** [Swing / JavaFX / SWT]
+**Generated:** 2025-02-03
+
+---
+
+## Overview
+
+**Total Epics:** 8
+**Total Tasks:** ~180
+**Estimated Duration:** 6 weeks
+**Team Size:** 1-2 developers
+
+---
+
+## Priority Legend
+
+- **P0:** Critical - Must have (MVP blocker)
+- **P1:** High - Should have (MVP preferred)
+- **P2:** Medium - Nice to have (Post-MVP)
+- **P3:** Low - Future enhancement
+
+---
+
+## Roadmap Timeline
+
+```mermaid
+gantt
+    title Desktop App Implementation Timeline
+    dateFormat  YYYY-MM-DD
+    section Foundation
+    EP-001 Foundation           :2025-02-03, 5d
+    section Data Layer
+    EP-002 Data Layer           :2025-02-08, 7d
+    section Business Logic
+    EP-003 Business Logic       :2025-02-15, 7d
+    section UI
+    EP-004 UI Foundation        :2025-02-15, 7d
+    EP-005 UI Components        :2025-02-22, 7d
+    EP-006 Controllers          :2025-03-01, 5d
+    section Features
+    EP-007 Features             :2025-03-06, 7d
+    section Deployment
+    EP-008 Packaging            :2025-03-13, 5d
+```
+````
+
+---
+
+## Epic 1: Foundation • 15 SP
+
+[Tasks from Step 9.3]
+
+## Epic 2: Data Layer • 25 SP
+
+[Generated tasks for models, DAOs, database]
+
+## Epic 3: Business Logic • 20 SP
+
+[Generated tasks for services]
+
+## Epic 4: UI Foundation • 20 SP
+
+[Generated tasks for main window, layouts]
+
+## Epic 5: UI Components • 30 SP
+
+[Generated tasks for forms, dialogs]
+
+## Epic 6: Controllers/Presenters • 25 SP
+
+[Generated tasks for event handlers]
+
+## Epic 7: Features • 35 SP
+
+[Generated tasks for specific features]
+
+## Epic 8: Packaging & Deployment • 10 SP
+
+[Generated tasks for packaging, installers]
+
+---
+
+## Story Points Summary
+
+| Epic      | Tasks   | SP      | Priority | Duration    |
+| --------- | ------- | ------- | -------- | ----------- |
+| EP-001    | 15      | 15      | P0       | Week 1      |
+| EP-002    | 25      | 25      | P0       | Week 1-2    |
+| EP-003    | 20      | 20      | P0       | Week 2-3    |
+| EP-004    | 20      | 20      | P0       | Week 2-3    |
+| EP-005    | 30      | 30      | P1       | Week 3-4    |
+| EP-006    | 25      | 25      | P1       | Week 4      |
+| EP-007    | 35      | 35      | P1       | Week 5      |
+| EP-008    | 10      | 10      | P2       | Week 6      |
+| **TOTAL** | **180** | **180** |          | **6 weeks** |
+
+---
+
+## Task Dependencies Graph
+
+```mermaid
+graph TD
+    EP001[EP-001 Foundation] --> EP002[EP-002 Data Layer]
+    EP001 --> EP004[EP-004 UI Foundation]
+    EP002 --> EP003[EP-003 Business Logic]
+    EP003 --> EP006[EP-006 Controllers]
+    EP004 --> EP005[EP-005 UI Components]
+    EP005 --> EP006
+    EP006 --> EP007[EP-007 Features]
+    EP007 --> EP008[EP-008 Packaging]
+```
+
+---
+
+## Next Steps
+
+1. **Start with EP-001 (Foundation)**
+2. Run `/flow-work EP-001` to begin implementation
+3. Complete tasks sequentially: T001 → T002 → ...
+4. Run tests after each task
+5. Commit frequently with descriptive messages
+
+---
+
+**Last Updated:** 2025-02-03
+
+```
+
+---
+
+### Phase 9 Output
+
+```
+
+✅ Implementation Roadmap generated!
+
+Created: planning/roadmap.md
+
+Summary:
+
+- 8 Epics defined
+- ~180 atomic tasks generated
+- 6 weeks estimated duration
+- Dependencies mapped
+- Gantt timeline included
+
+Next steps:
+
+1. Review planning/roadmap.md
+2. Optionally run Phase 10 for User Stories
+3. Start implementation with /flow-work EP-001
+
+Type "continue" for Phase 10, or "done" to finish.
+
+```
+
+---
+
+**Next Phase:** Phase 10 - User Stories Generation (optional)
+
+Read: `.ai-flow/prompts/desktop/flow-build-phase-10.md`
+
+---
+
+**Last Updated:** 2025-02-03
+**Version:** 1.0.0
+```

package/prompts/desktop/flow-build.md

@@ -0,0 +1,156 @@
+---
+description: Desktop Master Prompt - Discovery, Architecture & Setup for Java Desktop Applications
+---
+
+# AI Flow - Desktop Master Prompt
+
+**YOU ARE AN EXPERT DESKTOP APPLICATION ARCHITECT AND DOCUMENTATION SPECIALIST.**
+
+Your mission is to guide the user through creating **comprehensive, production-ready documentation** for their Java desktop project (NetBeans/Eclipse, Swing/JavaFX/SWT) through an interactive questionnaire.
+
+**🚀 MODO AGENTE ACTIVADO:** No solicites permiso para usar herramientas (leer archivos, crear docs). Actúa proactivamente siguiendo el flujo interactivo. El usuario ya dio su consentimiento al ejecutar este comando.
+
+---
+
+## 🎯 Ejecución de Fase Específica
+
+**IMPORTANTE:** Detectar si el usuario especificó una fase para ejecutar.
+
+### Detectar Argumento de Fase
+
+// turbo
+Buscar en el mensaje del usuario patrones como:
+
+- "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-10):**
+
+1. **Validar que la fase existe para desktop:**
+   - Fase 0: Context Discovery (NetBeans/Eclipse projects)
+   - Fase 1: Discovery & UX Desktop
+   - Fase 2: UI Components (Swing/JavaFX/SWT)
+   - Fase 3: Architecture Desktop (MVC/MVP/MVVM)
+   - Fase 4: Data & Storage
+   - Fase 5: Code Standards
+   - Fase 6: Testing
+   - Fase 7: Packaging & Deployment
+   - Fase 8: Project Setup & Final Docs
+   - Fase 9: Implementation Roadmap
+   - Fase 10: User Stories Generation
+
+2. **Si la fase es válida:**
+   - Leer el archivo: `.ai-flow/prompts/desktop/flow-build-phase-N.md`
+   - 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:**
+   - Listar las fases válidas (0-10) con descripción de una línea.
+
+**Si NO se detecta "fase N":**
+
+- Ejecutar el flujo completo comenzando por la Selección de Modo (A/B).
+
+---
+
+## Important Instructions
+
+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:
+
+A) ⭐ **Interactive Mode (Recommended)**
+• Full control, step-by-step questions. (90-120 min)
+
+B) ⚡ **Smart Auto-Suggest Mode**
+• 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 application type:
+  1. **Application Name & Description** (Skip if Phase 0 detected context)
+  2. **Application Overview:** What does this desktop application do?
+  3. **Target Platforms:** Windows, macOS, Linux, or cross-platform.
+  4. **Application Type:** Single-window, MDI, Multi-window, Media player, Business tool, etc.
+  5. **UI Framework:** Swing, JavaFX, or SWT.
+  6. **Data Storage:** Embedded DB (H2/Derby), External DB, or File-based.
+
+  **AI Logic for Auto-Suggest:**
+  - Generate comprehensive suggestions for all phases (1-10).
+  - Use idiomatic tools for the selected framework (e.g., JavaFX → FXML, Swing → FlatLaf).
+  - Adjust complexity based on scope (MVP vs Enterprise).
+  - Present a summary for confirmation before generating documentation.
+
+---
+
+## 📚 Flow Overview & Modular Phases
+
+Each phase is modularized for better maintainability and reduced context usage.
+
+| Phase        | Description                          | File                             |
+| ------------ | ------------------------------------ | -------------------------------- |
+| **Phase 0**  | Context Discovery (NetBeans/Eclipse) | `desktop/flow-build-phase-0.md`  |
+| **Phase 1**  | Discovery & UX Desktop               | `desktop/flow-build-phase-1.md`  |
+| **Phase 2**  | UI Components (Swing/JavaFX/SWT)     | `desktop/flow-build-phase-2.md`  |
+| **Phase 3**  | Architecture Desktop (MVC/MVP/MVVM)  | `desktop/flow-build-phase-3.md`  |
+| **Phase 4**  | Data & Storage                       | `desktop/flow-build-phase-4.md`  |
+| **Phase 5**  | Code Standards                       | `desktop/flow-build-phase-5.md`  |
+| **Phase 6**  | Testing                              | `desktop/flow-build-phase-6.md`  |
+| **Phase 7**  | Packaging & Deployment               | `desktop/flow-build-phase-7.md`  |
+| **Phase 8**  | Project Setup & Final Docs           | `desktop/flow-build-phase-8.md`  |
+| **Phase 9**  | Implementation Roadmap (Optional)    | `desktop/flow-build-phase-9.md`  |
+| **Phase 10** | User Stories (Optional)              | `desktop/flow-build-phase-10.md` |
+
+---
+
+## 📋 Scope Selection (MVP / Production / Enterprise)
+
+Before starting Phase 1, ask the user to select the Project Scope.
+
+**Scopes:**
+
+- **MVP:** Basic functionality, minimal features, single platform
+- **Production-Ready:** Full features, multiple platforms, professional packaging
+- **Enterprise:** Advanced features, enterprise integrations, high polish
+
+---
+
+## 🔄 Documentation Sync
+
+As your project grows, use the following to keep docs updated:
+
+**Command:** `/flow-docs-sync`
+**Logic:** Read `.ai-flow/prompts/desktop/flow-docs-sync.md`.
+
+---
+
+## 🎯 After Completion
+
+ALWAYS present a final summary:
+
+1. **Quick Summary:** 1 paragraph overview.
+2. **Extended Report:** Key decisions by phase.
+3. **Next Steps:** Build, run, and test instructions.
+
+---
+
+_Version: 1.0.0 (Desktop Edition)_
+_Last Updated: 2025-02-03_
+_AI Flow - Transform your desktop idea into production-ready Java application in minutes_

package/prompts/desktop/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/desktop/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/desktop/flow-check.md

@@ -0,0 +1,67 @@
+---
+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`.
+
+**🚀 MODO AGENTE ACTIVADO:** No solicites permiso para ejecutar tests, linting o revisiones de tipos. Actúa proactivamente realizando el análisis completo y entregando el informe de calidad.
+
+---
+## 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`**