ai-flow-dev 2.6.0 → 2.7.0

package/prompts/shared/smart-skip-preflight.md

@@ -1,214 +1,214 @@
-# Smart Skip Pre-Flight Check (Shared Template)
-
-## 🔍 Pre-Flight Check Logic
-
-**This section is automatically included in Phases 1-7 to enable smart skip functionality.**
-
-### How It Works
-
-1. **Read audit data** from Phase 0: `.ai-flow/cache/audit-data.json`
-2. **Check consistency score** for the current phase
-3. **Execute appropriate scenario** based on score
-
----
-
-## Execution Flow
-
-```javascript
-// Read audit data from Phase 0
-const auditData = readJSON('.ai-flow/cache/audit-data.json');
-const phaseData = auditData?.phases?.[currentPhase];
-
-if (phaseData?.exists) {
-  // Documentation exists, check consistency
-  if (phaseData.consistencyScore >= 95) {
-    executeScenarioA(); // SKIP
-  } else if (phaseData.consistencyScore >= 80) {
-    executeScenarioB(); // HYBRID
-  } else {
-    executeScenarioC(); // FULL
-  }
-} else {
-  // No existing docs, proceed with full phase
-  executeScenarioC();
-}
-```
-
----
-
-## Scenario A: High Confidence (≥95%) - SKIP
-
-**Display format:**
-
-```
----
-✅ [PHASE NAME] ALREADY DOCUMENTED
-
-File: [target-file]
-Consistency: [score]%
-Status: Complete documentation
-
-Documented Information:
-✅ [Key item 1]
-✅ [Key item 2]
-✅ [Key item 3]
-...
-
----
-
-Use existing documentation? (Y/n) ⭐
-> _
-```
-
-**User Actions:**
-- **Y**: Skip to next phase
-- **n**: Proceed with full phase questionnaire
-
----
-
-## Scenario B: Medium Confidence (80-94%) - HYBRID
-
-**Display format:**
-
-```
----
-📚 [PHASE NAME] PARTIALLY DOCUMENTED
-
-File: [target-file]
-Consistency: [score]%
-Status: Most information present, some gaps
-
-Documented:
-✅ [Item 1]
-✅ [Item 2]
-
-Missing:
-❌ [Gap 1]
-❌ [Gap 2]
-
----
-
-Options:
-A) Answer only [N] missing questions ⭐
-B) Re-answer everything (full phase)
-C) Skip entirely (use docs as-is)
-
-> _
-```
-
-**User Actions:**
-- **A**: Ask only missing questions, merge with existing docs
-- **B**: Full phase questionnaire
-- **C**: Skip with warning
-
----
-
-## Scenario C: Low Confidence (<80%) or No Docs - FULL PHASE
-
-**Display format:**
-
-```
----
-⚠️ [PHASE NAME] NEEDS DOCUMENTATION
-
-Reason: [target-file] is outdated or missing
-Consistency: [score]% (or N/A if file doesn't exist)
-
-Issues detected:
-❌ [Issue 1]
-❌ [Issue 2]
-
-Recommendation: Complete full phase questionnaire
-
-Proceeding with full phase...
-[Continue to first question]
-```
-
----
-
-## Phase-Specific Configuration
-
-Each phase references this template with specific parameters:
-
-### Phase 1: Discovery & Business
-- **Target File**: `project-brief.md`
-- **Phase Name**: "BUSINESS CONTEXT"
-- **Key Items**: Project name, description, users, objectives, system type, features, scope, constraints, metrics, business flows
-- **Typical Gaps**: Business objectives, success metrics, constraints
-
-### Phase 2: Data Architecture
-- **Target File**: `docs/data-model.md`
-- **Phase Name**: "DATA ARCHITECTURE"
-- **Key Items**: Entities, relationships, data patterns, indexes
-- **Typical Gaps**: Missing entities, undocumented relationships, missing fields
-
-### Phase 3: System Architecture
-- **Target File**: `docs/architecture.md`
-- **Phase Name**: "SYSTEM ARCHITECTURE"
-- **Key Items**: Framework, architecture pattern, API style, database, caching, background jobs, integrations
-- **Typical Gaps**: API versioning, rate limiting, caching strategy
-
-### Phase 4: Security & Authentication
-- **Target File**: `specs/security.md`
-- **Phase Name**: "SECURITY & AUTHENTICATION"
-- **Key Items**: Auth strategy, encryption, security patterns, compliance
-- **Typical Gaps**: Compliance requirements, audit logging, security policies
-
-### Phase 5: Code Standards
-- **Target File**: `docs/code-standards.md`
-- **Phase Name**: "CODE STANDARDS"
-- **Key Items**: Linters, formatters, naming conventions, code review process
-- **Typical Gaps**: Team-specific conventions, code review workflow
-
-### Phase 6: Testing Strategy
-- **Target File**: `docs/testing.md`
-- **Phase Name**: "TESTING STRATEGY"
-- **Key Items**: Test framework, coverage targets, test types, CI/CD integration
-- **Typical Gaps**: E2E strategy, load testing, performance testing
-
-### Phase 7: Operations & Deployment
-- **Target File**: `docs/deployment.md`
-- **Phase Name**: "OPERATIONS & DEPLOYMENT"
-- **Key Items**: CI/CD pipeline, deployment platform, monitoring, logging
-- **Typical Gaps**: Incident runbooks, disaster recovery, scaling strategy
-
----
-
-## Usage in Phase Prompts
-
-**In each phase prompt (1-7), add this reference:**
-
-```markdown
-## 🔍 Pre-Flight Check (Smart Skip Logic)
-
-> 📎 **Reference:** See [prompts/shared/smart-skip-preflight.md](../../.ai-flow/prompts/shared/smart-skip-preflight.md) for the complete smart skip logic.
-
-**Execute Pre-Flight Check for this phase:**
-
-- **Phase**: [Phase Number]
-- **Target File**: [file path]
-- **Phase Name**: [display name]
-
-[Proceed with appropriate scenario based on audit data]
-
----
-
-## Phase [N] Questions (Full Mode)
-
-[Continue with phase-specific questions...]
-```
-
----
-
-## Benefits of This Approach
-
-✅ **DRY Principle**: Single source of truth for skip logic
-✅ **Easy Maintenance**: Update once, applies to all phases
-✅ **Consistency**: Same UX across all phases
-✅ **Reduced File Size**: Each phase prompt is ~100 lines shorter
-✅ **Clear Separation**: Logic vs content
-
----
-
-**Last Updated:** 2025-12-22
-**Version:** 1.0
+# Smart Skip Pre-Flight Check (Shared Template)
+
+## 🔍 Pre-Flight Check Logic
+
+**This section is automatically included in Phases 1-7 to enable smart skip functionality.**
+
+### How It Works
+
+1. **Read audit data** from Phase 0: `.ai-flow/cache/audit-data.json`
+2. **Check consistency score** for the current phase
+3. **Execute appropriate scenario** based on score
+
+---
+
+## Execution Flow
+
+```javascript
+// Read audit data from Phase 0
+const auditData = readJSON('.ai-flow/cache/audit-data.json');
+const phaseData = auditData?.phases?.[currentPhase];
+
+if (phaseData?.exists) {
+  // Documentation exists, check consistency
+  if (phaseData.consistencyScore >= 95) {
+    executeScenarioA(); // SKIP
+  } else if (phaseData.consistencyScore >= 80) {
+    executeScenarioB(); // HYBRID
+  } else {
+    executeScenarioC(); // FULL
+  }
+} else {
+  // No existing docs, proceed with full phase
+  executeScenarioC();
+}
+```
+
+---
+
+## Scenario A: High Confidence (≥95%) - SKIP
+
+**Display format:**
+
+```
+---
+✅ [PHASE NAME] ALREADY DOCUMENTED
+
+File: [target-file]
+Consistency: [score]%
+Status: Complete documentation
+
+Documented Information:
+✅ [Key item 1]
+✅ [Key item 2]
+✅ [Key item 3]
+...
+
+---
+
+Use existing documentation? (Y/n) ⭐
+> _
+```
+
+**User Actions:**
+- **Y**: Skip to next phase
+- **n**: Proceed with full phase questionnaire
+
+---
+
+## Scenario B: Medium Confidence (80-94%) - HYBRID
+
+**Display format:**
+
+```
+---
+📚 [PHASE NAME] PARTIALLY DOCUMENTED
+
+File: [target-file]
+Consistency: [score]%
+Status: Most information present, some gaps
+
+Documented:
+✅ [Item 1]
+✅ [Item 2]
+
+Missing:
+❌ [Gap 1]
+❌ [Gap 2]
+
+---
+
+Options:
+A) Answer only [N] missing questions ⭐
+B) Re-answer everything (full phase)
+C) Skip entirely (use docs as-is)
+
+> _
+```
+
+**User Actions:**
+- **A**: Ask only missing questions, merge with existing docs
+- **B**: Full phase questionnaire
+- **C**: Skip with warning
+
+---
+
+## Scenario C: Low Confidence (<80%) or No Docs - FULL PHASE
+
+**Display format:**
+
+```
+---
+⚠️ [PHASE NAME] NEEDS DOCUMENTATION
+
+Reason: [target-file] is outdated or missing
+Consistency: [score]% (or N/A if file doesn't exist)
+
+Issues detected:
+❌ [Issue 1]
+❌ [Issue 2]
+
+Recommendation: Complete full phase questionnaire
+
+Proceeding with full phase...
+[Continue to first question]
+```
+
+---
+
+## Phase-Specific Configuration
+
+Each phase references this template with specific parameters:
+
+### Phase 1: Discovery & Business
+- **Target File**: `project-brief.md`
+- **Phase Name**: "BUSINESS CONTEXT"
+- **Key Items**: Project name, description, users, objectives, system type, features, scope, constraints, metrics, business flows
+- **Typical Gaps**: Business objectives, success metrics, constraints
+
+### Phase 2: Data Architecture
+- **Target File**: `docs/data-model.md`
+- **Phase Name**: "DATA ARCHITECTURE"
+- **Key Items**: Entities, relationships, data patterns, indexes
+- **Typical Gaps**: Missing entities, undocumented relationships, missing fields
+
+### Phase 3: System Architecture
+- **Target File**: `docs/architecture.md`
+- **Phase Name**: "SYSTEM ARCHITECTURE"
+- **Key Items**: Framework, architecture pattern, API style, database, caching, background jobs, integrations
+- **Typical Gaps**: API versioning, rate limiting, caching strategy
+
+### Phase 4: Security & Authentication
+- **Target File**: `specs/security.md`
+- **Phase Name**: "SECURITY & AUTHENTICATION"
+- **Key Items**: Auth strategy, encryption, security patterns, compliance
+- **Typical Gaps**: Compliance requirements, audit logging, security policies
+
+### Phase 5: Code Standards
+- **Target File**: `docs/code-standards.md`
+- **Phase Name**: "CODE STANDARDS"
+- **Key Items**: Linters, formatters, naming conventions, code review process
+- **Typical Gaps**: Team-specific conventions, code review workflow
+
+### Phase 6: Testing Strategy
+- **Target File**: `docs/testing.md`
+- **Phase Name**: "TESTING STRATEGY"
+- **Key Items**: Test framework, coverage targets, test types, CI/CD integration
+- **Typical Gaps**: E2E strategy, load testing, performance testing
+
+### Phase 7: Operations & Deployment
+- **Target File**: `docs/deployment.md`
+- **Phase Name**: "OPERATIONS & DEPLOYMENT"
+- **Key Items**: CI/CD pipeline, deployment platform, monitoring, logging
+- **Typical Gaps**: Incident runbooks, disaster recovery, scaling strategy
+
+---
+
+## Usage in Phase Prompts
+
+**In each phase prompt (1-7), add this reference:**
+
+```markdown
+## 🔍 Pre-Flight Check (Smart Skip Logic)
+
+> 📎 **Reference:** See [prompts/shared/smart-skip-preflight.md](../../.ai-flow/prompts/shared/smart-skip-preflight.md) for the complete smart skip logic.
+
+**Execute Pre-Flight Check for this phase:**
+
+- **Phase**: [Phase Number]
+- **Target File**: [file path]
+- **Phase Name**: [display name]
+
+[Proceed with appropriate scenario based on audit data]
+
+---
+
+## Phase [N] Questions (Full Mode)
+
+[Continue with phase-specific questions...]
+```
+
+---
+
+## Benefits of This Approach
+
+✅ **DRY Principle**: Single source of truth for skip logic
+✅ **Easy Maintenance**: Update once, applies to all phases
+✅ **Consistency**: Same UX across all phases
+✅ **Reduced File Size**: Each phase prompt is ~100 lines shorter
+✅ **Clear Separation**: Logic vs content
+
+---
+
+**Last Updated:** 2025-12-22
+**Version:** 1.0

package/prompts/shared/story-points.md

@@ -1,65 +1,65 @@
-# Story Points Reference
-
-> **Canonical reference for Fibonacci-based Story Point estimation across all AI Flow phases.**
->
-> This file is the single source of truth for Story Points. All phases that require SP estimation MUST reference this file.
+# Story Points Reference
+
+> **Canonical reference for Fibonacci-based Story Point estimation across all AI Flow phases.**
+>
+> This file is the single source of truth for Story Points. All phases that require SP estimation MUST reference this file.
 ---
-## Story Points Scale (Fibonacci)
+## Story Points Scale (Fibonacci)
 ---
-| Story Points | Complexity | Typical Time | Examples                               |
-| ------------ | ---------- | ------------ | -------------------------------------- |
-| **1 SP**     | Trivial    | 1-2 hours    | Add simple field, update enum          |
-| **2 SP**     | Very Small | 2-4 hours    | Basic validation, simple test          |
-| **3 SP**     | Small      | 4-8 hours    | Simple CRUD endpoint, basic entity     |
-| **5 SP**     | Medium     | 1-2 days     | Complex endpoint with business logic   |
-| **8 SP**     | Complex    | 2-3 days     | Auth flow, complex validation          |
-| **13 SP**    | Large      | 1 week       | Complete module with full tests        |
-| **21 SP**    | Very Large | 2 weeks      | Major feature with integration         |
-| **34 SP**    | Epic       | 3 weeks      | Multiple related features (Epic-level) |
+| Story Points | Complexity | Typical Time | Examples                               |
+| ------------ | ---------- | ------------ | -------------------------------------- |
+| **1 SP**     | Trivial    | 1-2 hours    | Add simple field, update enum          |
+| **2 SP**     | Very Small | 2-4 hours    | Basic validation, simple test          |
+| **3 SP**     | Small      | 4-8 hours    | Simple CRUD endpoint, basic entity     |
+| **5 SP**     | Medium     | 1-2 days     | Complex endpoint with business logic   |
+| **8 SP**     | Complex    | 2-3 days     | Auth flow, complex validation          |
+| **13 SP**    | Large      | 1 week       | Complete module with full tests        |
+| **21 SP**    | Very Large | 2 weeks      | Major feature with integration         |
+| **34 SP**    | Epic       | 3 weeks      | Multiple related features (Epic-level) |
 ---
-## Story Points to Time Conversion (Hybrid Estimation)
+## Story Points to Time Conversion (Hybrid Estimation)
 ---
-Use this table to add time estimates to each task:
-
-| Story Points | Time Estimate (solo dev) | Time Range | Example Task                            |
-| ------------ | ------------------------ | ---------- | --------------------------------------- |
-| **1 SP**     | 1-2 hours                | (~1-2h)    | Add enum value, simple config change    |
-| **2 SP**     | 3-4 hours                | (~3-4h)    | Write 5-8 unit tests, basic validation  |
-| **3 SP**     | 4-8 hours                | (~4-8h)    | Simple CRUD endpoint, basic entity      |
-| **5 SP**     | 1-2 days                 | (~1-2d)    | Complex endpoint with business logic    |
-| **8 SP**     | 2-3 days                 | (~2-3d)    | Auth flow, complex validation           |
-| **13 SP**    | 1 week                   | (~1w)      | Complete module with full test coverage |
-| **21 SP**    | 2 weeks                  | (~2w)      | Major feature with integration          |
-| **34 SP**    | 3 weeks                  | (~3w)      | Multiple related features (Epic-level)  |
-
-> **Note:** Time assumes AI-assisted development (GitHub Copilot, Claude, etc.). Without AI assistance, multiply time estimates by 2-3x.
->
-> **Velocity Tracking:** After completing 2-3 features, compare actual time vs estimates to calibrate your team's velocity. Adjust remaining estimates accordingly.
+Use this table to add time estimates to each task:
+
+| Story Points | Time Estimate (solo dev) | Time Range | Example Task                            |
+| ------------ | ------------------------ | ---------- | --------------------------------------- |
+| **1 SP**     | 1-2 hours                | (~1-2h)    | Add enum value, simple config change    |
+| **2 SP**     | 3-4 hours                | (~3-4h)    | Write 5-8 unit tests, basic validation  |
+| **3 SP**     | 4-8 hours                | (~4-8h)    | Simple CRUD endpoint, basic entity      |
+| **5 SP**     | 1-2 days                 | (~1-2d)    | Complex endpoint with business logic    |
+| **8 SP**     | 2-3 days                 | (~2-3d)    | Auth flow, complex validation           |
+| **13 SP**    | 1 week                   | (~1w)      | Complete module with full test coverage |
+| **21 SP**    | 2 weeks                  | (~2w)      | Major feature with integration          |
+| **34 SP**    | 3 weeks                  | (~3w)      | Multiple related features (Epic-level)  |
+
+> **Note:** Time assumes AI-assisted development (GitHub Copilot, Claude, etc.). Without AI assistance, multiply time estimates by 2-3x.
+>
+> **Velocity Tracking:** After completing 2-3 features, compare actual time vs estimates to calibrate your team's velocity. Adjust remaining estimates accordingly.
 ---
-## Epic Estimation Guidelines
+## Epic Estimation Guidelines
 ---
-- **Foundation Epic:** 13-21 SP (depends on framework complexity)
-- **Data Layer Epic:** 3-5 SP per simple entity, 8-13 SP per complex entity
-- **Auth Epic:** 8 SP (basic JWT) to 21 SP (multi-provider + RBAC + 2FA)
-- **Business Epics:** Varies by domain complexity
-- **Integration Epic:** 5-8 SP per external service
-- **Operations Epic:** 13 SP (standard CI/CD + monitoring)
+- **Foundation Epic:** 13-21 SP (depends on framework complexity)
+- **Data Layer Epic:** 3-5 SP per simple entity, 8-13 SP per complex entity
+- **Auth Epic:** 8 SP (basic JWT) to 21 SP (multi-provider + RBAC + 2FA)
+- **Business Epics:** Varies by domain complexity
+- **Integration Epic:** 5-8 SP per external service
+- **Operations Epic:** 13 SP (standard CI/CD + monitoring)
 ---
-## Feature Size Classification
+## Feature Size Classification
 ---
-| Size        | Task Count | Phases  | Characteristics                                    |
-| ----------- | ---------- | ------- | -------------------------------------------------- |
-| **SMALL**   | 1-10 tasks | 1 phase | Single file changes, isolated                      |
-| **MEDIUM**  | 11-40      | 2-4     | Multiple files, some cross-layer dependencies      |
-| **COMPLEX** | 41-80      | 4-8     | Multiple modules, integration, extensive testing   |
-| **LARGE**   | 81+        | 8-N     | Feature affecting entire system, major refactoring |
+| Size        | Task Count | Phases  | Characteristics                                    |
+| ----------- | ---------- | ------- | -------------------------------------------------- |
+| **SMALL**   | 1-10 tasks | 1 phase | Single file changes, isolated                      |
+| **MEDIUM**  | 11-40      | 2-4     | Multiple files, some cross-layer dependencies      |
+| **COMPLEX** | 41-80      | 4-8     | Multiple modules, integration, extensive testing   |
+| **LARGE**   | 81+        | 8-N     | Feature affecting entire system, major refactoring |
 ---
-## How to Use Hybrid Estimation
+## How to Use Hybrid Estimation
 ---
-- Each task shows **both** Story Points and time: `• 2 SP (~3-4h)`
-- Story Points measure **complexity** (stable across teams)
-- Time estimates measure **effort** (varies by team velocity)
-- Track both to improve estimation accuracy over time
-
-
-
+- Each task shows **both** Story Points and time: `• 2 SP (~3-4h)`
+- Story Points measure **complexity** (stable across teams)
+- Time estimates measure **effort** (varies by team velocity)
+- Track both to improve estimation accuracy over time
+
+
+