ai-flow-dev 2.1.7 → 2.1.9

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

@@ -2,9 +2,18 @@
 
 > **Order for this phase:** 1.1 → 1.2 → 1.3 → 1.4 → 1.5 → 1.6 → 1.7 → 1.8 → 1.9 → 1.10
 
+> **📌 Scope-based behavior:**
+> - **MVP/Basic Scope:** Focus only on core requirements. Skip advanced business logic questions.
+> - **Production-Ready Scope:** In-depth exploration of compliance, scalability, and long-term business goals.
+
+### Objective
+Define the project's core purpose, business rules, and high-level requirements to ensure the foundation is solid before technical design begins.
+
 > **📌 Note:** If Phase 0 was executed, some questions may already be answered. Skip those and only ask what's missing.
 
-**1.1 Project Name & Description**
+**1.1 Project Name & Description (with Smart Refinement)**
+
+> **🧠 Intelligent Refinement System**: This question detects vague descriptions and guides the developer to enrich them. It only asks what's missing and responds in the developer's language.
 
 ```
 [If detected from Phase 0, show:]
@@ -17,26 +26,178 @@ If no, please provide correct values.
 [If NOT detected, ask:]
 What is the project name?
 
-Provide a short description (1 sentence) for README and package.json
+Provide an initial description of your project.
+(Don't worry about perfection - we'll refine it together if needed!)
+
+Example: "A backend for managing gym memberships"
+```
+
+**🔍 AI Internal: Ambiguity Analysis**
+
+After receiving the description, silently analyze for these criteria:
+
+| Criterion | Check For | Score +1 if present |
+|-----------|-----------|---------------------|
+| **WHO** | Specific user type mentioned (not just "users") | "gym members", "restaurant owners" |
+| **WHAT** | Specific action/function (not just "manage") | "track workouts", "process payments" |
+| **WHY** | Purpose or value mentioned | "to replace spreadsheets", "to launch app" |
+| **DOMAIN** | Industry/vertical indicated | "fitness", "fintech", "healthcare" |
+| **DETAIL** | Description has 10+ meaningful words | Not counting articles |
+
+**Scoring Rules:**
+- Score 4-5: ✅ Accept immediately → Proceed to 1.2
+- Score 0-3: ⚠️ Enter refinement loop → Ask ONLY missing criteria
+
+---
+
+**🔄 Conditional Refinement Loop (only if score < 4)**
+
+> **CRITICAL**: Only ask about criteria that are MISSING. Do NOT repeat questions already answered. Respond in the SAME LANGUAGE the developer used.
+
+```
+[LANGUAGE: Match the developer's language]
+
+🔍 I'd like to understand your project better.
+
+Your description: "[original description]"
+
+[ONLY show questions for MISSING criteria:]
+
+[If WHO is missing:]
+1️⃣ WHO will use this system?
+   A) End consumers (B2C)
+   B) Business users (B2B)
+   C) Internal team
+   D) Other systems (APIs)
+   E) Other: __
+
+[If WHAT is missing:]
+2️⃣ WHAT is the core action users will perform?
+   A) Buy/sell products or services
+   B) Manage/organize information
+   C) Communicate/collaborate
+   D) Monitor/analyze data
+   E) Create/publish content
+   F) Other: __
+
+[If WHY is missing:]
+3️⃣ WHY is this project needed?
+   A) Replace manual/legacy process
+   B) Launch new product/business
+   C) Improve existing system
+   D) Enable new capability
+   E) Other: __
+
+[If DOMAIN is missing:]
+4️⃣ What INDUSTRY/DOMAIN is this for?
+   A) E-commerce/Retail
+   B) Fitness/Health
+   C) Finance/Payments
+   D) Education
+   E) Social/Community
+   F) Business tools (CRM, ERP)
+   G) Other: __
+
+Your answers: __ (e.g., "A, B, A, E" or describe freely)
 ```
 
-**1.2 Project Overview**
+---
+
+**✨ Generate Professional Description Options**
+
+After gathering missing info, generate 3 polished versions:
 
 ```
-What problem does this backend system solve?
+[LANGUAGE: Match the developer's language]
+
+✨ Based on your input, here are 3 professional descriptions:
+
+A) Concise (for package.json):
+   "[Generated 1-line description with WHO + WHAT]"
+
+B) Descriptive (for README.md):
+   "[Generated 2-3 line description with WHO + WHAT + WHY]"
+
+C) Technical (for AGENT.md):
+   "[Generated technical description with DOMAIN + WHAT]"
+
+Which do you prefer? (1-3, or 4 to edit, 5 to start over)
+```
+
+---
+
+**✅ Final Confirmation**
+
+```
+✅ Your final project description:
+
+📋 Name: [project name]
+📝 Description: "[final polished description]"
+
+Proceed to next question? (Y to continue)
+```
+
+---
+
+**1.2 Project Overview (Confirmation + Expansion)**
+
+> **📌 Smart Skip**: If 1.1 already captured WHO/WHAT/WHY completely, this becomes a quick confirmation.
+
+```
+[If 1.1 refinement was complete (score >= 4), show:]
+
+✅ Based on your description, I understand:
+   • Users: [WHO from 1.1]
+   • Core Action: [WHAT from 1.1]
+   • Purpose: [WHY from 1.1]
 
-Describe in 2-3 sentences:
-- Who are the users?
-- What is the core value proposition?
-- What makes this project necessary?
+Is this complete? (Y) Or would you like to add more context? (N)
+
+[If user says Y → Skip to 1.3]
+[If user says N → Ask:]
+What additional context would you like to add?
+
+---
+
+[If 1.1 was NOT refined OR any WHO/WHAT/WHY still missing, ask:]
+
+[ONLY ask for MISSING elements - check what was NOT captured in 1.1:]
+
+[If WHO still unclear:]
+Who are the primary users of this system?
+
+[If WHAT still unclear:]
+What is the core value proposition?
+
+[If WHY still unclear:]
+What makes this project necessary?
 
 Example:
 "A backend for a fitness tracking mobile app used by gym-goers (users). It allows users to log workouts, track progress over time, and share achievements with friends (value). This project is necessary to replace our legacy spreadsheet-based system and support our new iOS app launch."
 ```
 
-**1.3 Target Users**
+**1.3 Target Users (Confirmation + Additional Types)**
+
+> **📌 Smart Skip**: If 1.1 already identified user types, this confirms and expands.
 
 ```
+[If WHO was captured in 1.1, show:]
+
+✅ Based on your description, your target users are: [WHO from 1.1]
+
+Would you like to add any additional user types? Select any that apply:
+
+A) 🌐 External end-users (B2C) - Public-facing application
+B) 🏢 Internal employees (B2B/Enterprise) - Company internal tool
+C) 🔌 Other systems/services (API consumers) - Integration platform
+D) 👥 Partners/Third-parties - Partner ecosystem
+E) 📱 Mobile/Web apps - Backend for frontend
+F) ✅ No additional users - [WHO from 1.1] is complete
+
+---
+
+[If WHO was NOT captured in 1.1, ask normally:]
+
 Who will use this system? Select all that apply:
 
 A) 🌐 External end-users (B2C) - Public-facing application
@@ -65,9 +226,24 @@ Your objectives:
 3.
 ```
 
-**1.5 System Type**
+**1.5 System Type (Confirmation + Validation)**
+
+> **📌 Smart Skip**: If 1.1 already identified the domain/industry, this confirms it.
 
 ```
+[If DOMAIN was captured in 1.1, show:]
+
+✅ Based on your description, this appears to be a: [DOMAIN from 1.1] system
+
+Is this correct?
+
+A) ✅ Yes, that's correct
+B) 🔄 No, it's actually: [show options below]
+
+---
+
+[If DOMAIN was NOT captured in 1.1, OR user selected B above:]
+
 What type of system are you building? (This helps suggest common features)
 
 A) 🛒 E-commerce/Marketplace
@@ -141,7 +317,7 @@ This helps us focus the documentation on what you're building now, while noting
 📋 What will you build in this first version? (Select from the features listed above)
 
 [Show features from question 1.6 and allow selection]
----
+---
 ⏭️ What will you leave for future versions? (What you're NOT building now)
 
 Common things to defer:
@@ -229,7 +405,7 @@ Example:
 - Invoicing: Invoice generation after purchase.
 
 The AI will automatically generate flow diagrams (mermaid) for each documented process.
----
+---
 #### 🎨 MERMAID BUSINESS FLOW DIAGRAM FORMAT - CRITICAL
 
 **Use this exact format** for business process flows:
@@ -356,7 +532,7 @@ flowchart TD
 - Customer Support Ticket Lifecycle
 
 **Validation:** Test at https://mermaid.live/ before saving
----
+---
 ```
 
 ### Phase 1 Output
@@ -381,7 +557,7 @@ Business Flows: [list of main flows]
 Is this correct? (Yes/No)
 If corrections needed, specify which section.
 ```
----
+---
 ### 📄 Generate Phase 1 Documents
 
 **Generate `project-brief.md` automatically:**
@@ -403,11 +579,26 @@ The document has been created with all the information from Phase 1.
 
 **If user edits the file:**
 Execute `read_file('project-brief.md')` to refresh context before continuing.
----
-**Proceed to Phase 2 after document is generated and optionally reviewed.**
+---
+
+## 📝 Generated Documents
+
+After Phase 1, generate/update:
+- `project-brief.md` - Core project discovery and requirements
+
+---
+
+**Next Phase:** Phase 2 - Data Architecture (15-20 min)
+
+Read: `.ai-flow/prompts/backend/flow-build-phase-2.md`
+
+---
+
+**Last Updated:** 2025-12-20
+**Version:** 2.1.8
+
+---
 
-> ⚠️ **CRITICAL:** DO NOT generate README.md in Phase 1. README.md is ONLY generated in Phase 8 (step 8.5) after framework initialization.
----
 ## PHASE 2: Data Architecture (15-20 min)
 
 ````

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

@@ -1,15 +1,12 @@
-# AI Flow - Phase 10: User Stories Generation
+## PHASE 10: Agile Planning - User Stories (5-10 min)
 
-**YOU ARE AN EXPERT PRODUCT OWNER AND AGILE SPECIALIST.**
+> **Order for this phase:** OPTIONAL. Executed after Phase 9 or on demand.
 
-Generate detailed User Stories from the roadmap created in Phase 9.
+> **📌 Scope-based behavior:**
+> - **All Scopes:** Generate detailed User Stories for each milestone in the Roadmap.
 
-## Prerequisites
-
-- Phase 9 completed (`docs/roadmap.md` exists with context variables)
-- All Phase 1-8 documentation exists
-
-## Duration
+### Objective
+Break down technical roadmap tasks into user-centric Agile requirements (User Stories) to facilitate development, testing, and acceptance criteria definition.
 
 - All Epics: 30-60 minutes
 - One Epic: 5-10 minutes
@@ -321,3 +318,22 @@ Next steps:
 2. Start implementing: /flow-dev-feature HU-001-001
 3. Generate more: /flow-build fase 10 EP-XXX
 ```
+
+---
+
+## 📝 Generated Documents
+
+After Phase 10, generate/update:
+
+- `docs/user-stories/*.md` - Detailed Agile requirements
+- `docs/roadmap.md` - (updated with story links)
+
+---
+
+**CONGRATULATIONS!** Project documentation and planning are complete. 🚀
+
+---
+
+**Last Updated:** 2025-12-20
+**Version:** 2.1.8
+

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

@@ -2,7 +2,9 @@
 
 > **Order for this phase:** 2.1 → 2.2 → 2.3 → 2.4 → 2.5 → 2.6 → 2.7
 
-> **📌 Note:** If Phase 0 detected database/entities from code, those will be pre-filled. Review and confirm.
+> **📌 Scope-based behavior:**
+> - **MVP/Basic Scope:** Focus only on essential entities and basic relationships.
+> - **Production-Ready Scope:** In-depth modeling including indexes, constraints, and audit fields.
 
 ### Objective
 
@@ -531,6 +533,22 @@ Execute `read_file('docs/data-model.md')` to refresh context before continuing.
 
 ---
 
-## **Proceed to Phase 3 after document is generated and optionally reviewed.**
+## 📝 Generated Documents
+
+After Phase 2, generate/update:
+- `docs/data-model.md` - Database schema and entity relationships
+
+---
+
+**Next Phase:** Phase 3 - System Architecture (15-20 min)
+
+Read: `.ai-flow/prompts/backend/flow-build-phase-3.md`
+
+---
+
+**Last Updated:** 2025-12-20
+**Version:** 2.1.8
+
+---
 
 ## PHASE 3: System Architecture (15-20 min)

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

@@ -741,4 +741,23 @@ Execute `read_file()` for both documents to refresh context before continuing.
 
 ---
 
+## 📝 Generated Documents
+
+After Phase 3, generate/update:
+- `docs/architecture.md` - Technical stack and patterns
+- `ai-instructions.md` - Instructions for AI agents
+
+---
+
+**Next Phase:** Phase 4 - Security & Authentication (15-20 min)
+
+Read: `.ai-flow/prompts/backend/flow-build-phase-4.md`
+
+---
+
+**Last Updated:** 2025-12-20
+**Version:** 2.1.8
+
+---
+
 ## PHASE 4: Security & Authentication (15-20 min)

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

@@ -461,7 +461,7 @@ Input Validation: [strategy + sanitization rules + size limits + file upload val
 
 Is this correct? (Yes/No)
 ```
----
+---
 ### 📄 Generate Phase 4 Documents
 
 **Before starting generation:**
@@ -501,12 +501,35 @@ Documents have been created with all Phase 4 information.
 
 **If user edits files:**
 Re-read files to refresh context before continuing.
----
+---
 **Proceed to Phase 5 only after documents are validated.**
 
 > ⚠️ **CRITICAL:** DO NOT generate README.md in this phase. README.md is ONLY generated in Phase 8 (step 8.5) after framework initialization.
----
+---
+---
+
+---
+
+## 📝 Generated Documents
+
+After Phase 4, generate/update:
+- `specs/security.md` - Security policies and authentication details
+
+---
+
+**Next Phase:** Phase 5 - Development Standards (15-20 min)
+
+Read: `.ai-flow/prompts/backend/flow-build-phase-5.md`
+
+---
+
+**Last Updated:** 2025-12-20
+**Version:** 2.1.8
+
+---
+
 ## PHASE 5: Development Standards (15-20 min)
 
 
 
+

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

@@ -662,4 +662,23 @@ Re-read files to refresh context before continuing.
 
 ---
 
-## PHASE 6: Testing Strategy (10 min)
+## 📝 Generated Documents
+
+After Phase 5, generate/update:
+- `docs/code-standards.md` - Development practices and quality rules
+
+---
+
+**Next Phase:** Phase 6 - Testing Strategy (15-20 min)
+
+Read: `.ai-flow/prompts/backend/flow-build-phase-6.md`
+
+---
+
+**Last Updated:** 2025-12-20
+**Version:** 2.1.8
+
+---
+
+## PHASE 6: Testing Strategy (15-20 min)
+

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

@@ -1,4 +1,4 @@
-## PHASE 6: Testing Strategy (15-25 min)
+## PHASE 6: Testing Strategy (15-20 min)
 
 > **Order for this phase:**
 >
@@ -481,5 +481,25 @@ Re-read file to refresh context before continuing.
 
 > ⚠️ **CRITICAL:** DO NOT generate README.md in this phase. README.md is ONLY generated in Phase 8 (step 8.5) after framework initialization.
 ---
-## PHASE 7: Operations & Deployment (10 min)
+
+## 📝 Generated Documents
+
+After Phase 6, generate/update:
+- `docs/testing.md` - Testing strategy and quality gates
+
+---
+
+**Next Phase:** Phase 7 - Operations & Deployment (10-15 min)
+
+Read: `.ai-flow/prompts/backend/flow-build-phase-7.md`
+
+---
+
+**Last Updated:** 2025-12-20
+**Version:** 2.1.8
+
+---
+
+## PHASE 7: Operations & Deployment (10-15 min)
+
 ````