owflow 0.6.0 → 0.7.0

package/dist/skills/flow-init/references/architecture-template.md

@@ -1,45 +1,45 @@
-# Architecture Document Template
-
-Optional documentation — only generate if user selected "Architecture" in Phase 3.
-
-```markdown
-# System Architecture
-
-## Overview
-[High-level description of system architecture]
-
-## Architecture Pattern
-**Pattern**: [From analysis - e.g., "Layered monolithic with REST API"]
-
-[Description of how the pattern is implemented]
-
-## System Structure
-
-### [Component 1]
-- **Location**: [From analysis - e.g., "src/api/"]
-- **Purpose**: [What it does]
-- **Key Files**: [List from analysis]
-
-### [Component 2]
-- **Location**: [From analysis]
-- **Purpose**: [What it does]
-- **Key Files**: [List from analysis]
-
-## Data Flow
-[Describe how data flows through the system]
-
-## External Integrations
-[List integrations found in analysis - databases, APIs, services]
-
-## Database Schema
-[If ORM detected, reference schema file location]
-
-## Configuration
-[How configuration is managed]
-
-## Deployment Architecture
-[If detected - Docker, K8s, cloud services]
-
----
-*Based on codebase analysis performed [Date]*
-```
+# Architecture Document Template
+
+Optional documentation — only generate if user selected "Architecture" in Phase 3.
+
+```markdown
+# System Architecture
+
+## Overview
+[High-level description of system architecture]
+
+## Architecture Pattern
+**Pattern**: [From analysis - e.g., "Layered monolithic with REST API"]
+
+[Description of how the pattern is implemented]
+
+## System Structure
+
+### [Component 1]
+- **Location**: [From analysis - e.g., "src/api/"]
+- **Purpose**: [What it does]
+- **Key Files**: [List from analysis]
+
+### [Component 2]
+- **Location**: [From analysis]
+- **Purpose**: [What it does]
+- **Key Files**: [List from analysis]
+
+## Data Flow
+[Describe how data flows through the system]
+
+## External Integrations
+[List integrations found in analysis - databases, APIs, services]
+
+## Database Schema
+[If ORM detected, reference schema file location]
+
+## Configuration
+[How configuration is managed]
+
+## Deployment Architecture
+[If detected - Docker, K8s, cloud services]
+
+---
+*Based on codebase analysis performed [Date]*
+```

package/dist/skills/flow-init/references/roadmap-templates.md

@@ -1,93 +1,93 @@
-# Roadmap Document Templates
-
-Select the appropriate template based on project type detected by project-analyzer.
-
-## New Project (Feature-Based)
-
-```markdown
-# Development Roadmap
-
-This roadmap outlines the planned features and development phases for [PROJECT_NAME].
-
-## Phase 1: MVP (Minimum Viable Product)
-**Timeline**: [Estimated]
-
-- [ ] **Feature 1** — [Description] `[Effort: S/M/L]`
-- [ ] **Feature 2** — [Description] `[Effort: S/M/L]`
-- [ ] **Feature 3** — [Description] `[Effort: S/M/L]`
-
-## Phase 2: Core Features
-**Timeline**: [Estimated]
-
-- [ ] **Feature 4** — [Description] `[Effort: S/M/L]`
-- [ ] **Feature 5** — [Description] `[Effort: S/M/L]`
-
-## Future Enhancements
-- [ ] **Feature X** — [Nice to have]
-
----
-**Effort Scale**: `S`: 2-3 days | `M`: 1 week | `L`: 2+ weeks
-```
-
-## Existing Project (Evolution)
-
-```markdown
-# Development Roadmap
-
-## Current State
-- **Version**: [From analysis]
-- **Key Features**: [List major current features]
-- **Recent Updates**: [From git history]
-
-## Planned Enhancements (Next 3-6 Months)
-
-### High Priority
-- [ ] **Enhancement 1** — [Description and why it matters]
-- [ ] **Enhancement 2** — [Description and why it matters]
-
-### Medium Priority
-- [ ] **Enhancement 3** — [Description]
-
-### Technical Debt
-- [ ] **Debt Item 1** — [From analysis, if applicable]
-- [ ] **Debt Item 2** — [From analysis, if applicable]
-
-## Future Considerations
-- **Feature Ideas**: [Long-term possibilities]
-- **Scalability**: [Performance improvements needed]
-```
-
-## Legacy Project (Modernization)
-
-```markdown
-# Modernization Roadmap
-
-## Current State Assessment
-- **Technology Age**: [From analysis]
-- **Technical Debt**: [High/Medium/Low]
-- **Outdated Components**: [List from analysis]
-- **Security Concerns**: [If identified]
-
-## Modernization Goals
-
-### Critical (Must Do)
-- [ ] **Upgrade [Component]** — [e.g., "Java 8 → Java 17 LTS"] `Risk: High if delayed`
-- [ ] **Security Patch** — [Address known vulnerabilities]
-
-### Important (Should Do)
-- [ ] **Framework Update** — [e.g., "Spring 3.x → Spring Boot 3.x"]
-- [ ] **Improve Test Coverage** — [Current: X%, Target: Y%]
-
-### Improvements (Nice to Do)
-- [ ] **Refactor Module X** — [Reduce technical debt]
-- [ ] **Add Documentation** — [Architecture, deployment]
-
-## Migration Strategy
-[Step-by-step approach if major migration needed]
-
-## Risk Mitigation
-[How to reduce risk during modernization]
-
----
-*Assessment based on project analysis performed [Date]*
-```
+# Roadmap Document Templates
+
+Select the appropriate template based on project type detected by project-analyzer.
+
+## New Project (Feature-Based)
+
+```markdown
+# Development Roadmap
+
+This roadmap outlines the planned features and development phases for [PROJECT_NAME].
+
+## Phase 1: MVP (Minimum Viable Product)
+**Timeline**: [Estimated]
+
+- [ ] **Feature 1** — [Description] `[Effort: S/M/L]`
+- [ ] **Feature 2** — [Description] `[Effort: S/M/L]`
+- [ ] **Feature 3** — [Description] `[Effort: S/M/L]`
+
+## Phase 2: Core Features
+**Timeline**: [Estimated]
+
+- [ ] **Feature 4** — [Description] `[Effort: S/M/L]`
+- [ ] **Feature 5** — [Description] `[Effort: S/M/L]`
+
+## Future Enhancements
+- [ ] **Feature X** — [Nice to have]
+
+---
+**Effort Scale**: `S`: 2-3 days | `M`: 1 week | `L`: 2+ weeks
+```
+
+## Existing Project (Evolution)
+
+```markdown
+# Development Roadmap
+
+## Current State
+- **Version**: [From analysis]
+- **Key Features**: [List major current features]
+- **Recent Updates**: [From git history]
+
+## Planned Enhancements (Next 3-6 Months)
+
+### High Priority
+- [ ] **Enhancement 1** — [Description and why it matters]
+- [ ] **Enhancement 2** — [Description and why it matters]
+
+### Medium Priority
+- [ ] **Enhancement 3** — [Description]
+
+### Technical Debt
+- [ ] **Debt Item 1** — [From analysis, if applicable]
+- [ ] **Debt Item 2** — [From analysis, if applicable]
+
+## Future Considerations
+- **Feature Ideas**: [Long-term possibilities]
+- **Scalability**: [Performance improvements needed]
+```
+
+## Legacy Project (Modernization)
+
+```markdown
+# Modernization Roadmap
+
+## Current State Assessment
+- **Technology Age**: [From analysis]
+- **Technical Debt**: [High/Medium/Low]
+- **Outdated Components**: [List from analysis]
+- **Security Concerns**: [If identified]
+
+## Modernization Goals
+
+### Critical (Must Do)
+- [ ] **Upgrade [Component]** — [e.g., "Java 8 → Java 17 LTS"] `Risk: High if delayed`
+- [ ] **Security Patch** — [Address known vulnerabilities]
+
+### Important (Should Do)
+- [ ] **Framework Update** — [e.g., "Spring 3.x → Spring Boot 3.x"]
+- [ ] **Improve Test Coverage** — [Current: X%, Target: Y%]
+
+### Improvements (Nice to Do)
+- [ ] **Refactor Module X** — [Reduce technical debt]
+- [ ] **Add Documentation** — [Architecture, deployment]
+
+## Migration Strategy
+[Step-by-step approach if major migration needed]
+
+## Risk Mitigation
+[How to reduce risk during modernization]
+
+---
+*Assessment based on project analysis performed [Date]*
+```

package/dist/skills/flow-init/references/tech-stack-template.md

@@ -1,70 +1,70 @@
-# Tech Stack Document Template
-
-Always generated (required documentation). Fill in all detected technologies, versions, and rationale from project analysis.
-
-```markdown
-# Technology Stack
-
-## Overview
-This document describes the technology choices and rationale for [PROJECT_NAME].
-
-## Languages
-
-### [Primary Language] ([Version])
-- **Usage**: [percentage]% of codebase
-- **Rationale**: [Why this language?]
-- **Key Features Used**: [Notable language features]
-
-## Frameworks
-
-### Frontend
-[List detected frontend frameworks with versions and rationale]
-
-### Backend
-[List detected backend frameworks with versions and rationale]
-
-### Testing
-[List detected testing frameworks]
-
-## Database
-
-### [Database Name] ([Version])
-- **Type**: [Relational/NoSQL/etc.]
-- **ORM/Client**: [Detected library]
-- **Rationale**: [Why this database?]
-
-## Build Tools & Package Management
-[From analysis: npm, Maven, pip, etc.]
-
-## Infrastructure
-
-### Containerization
-[Docker, Docker Compose - if detected]
-
-### CI/CD
-[GitHub Actions, GitLab CI - if detected]
-
-### Hosting
-[Vercel, AWS, Heroku - if detected or known]
-
-## Development Tools
-
-### Linting & Formatting
-[ESLint, Prettier, Black - from analysis]
-
-### Type Checking
-[TypeScript, MyPy - from analysis]
-
-## Key Dependencies
-[List major dependencies from package files]
-
-## Version Management
-[How versions are managed]
-
-## Migration Path (for legacy projects)
-[If applicable - planned upgrades]
-
----
-*Last Updated*: [Date]
-*Auto-detected*: [List what was auto-detected vs user-provided]
-```
+# Tech Stack Document Template
+
+Always generated (required documentation). Fill in all detected technologies, versions, and rationale from project analysis.
+
+```markdown
+# Technology Stack
+
+## Overview
+This document describes the technology choices and rationale for [PROJECT_NAME].
+
+## Languages
+
+### [Primary Language] ([Version])
+- **Usage**: [percentage]% of codebase
+- **Rationale**: [Why this language?]
+- **Key Features Used**: [Notable language features]
+
+## Frameworks
+
+### Frontend
+[List detected frontend frameworks with versions and rationale]
+
+### Backend
+[List detected backend frameworks with versions and rationale]
+
+### Testing
+[List detected testing frameworks]
+
+## Database
+
+### [Database Name] ([Version])
+- **Type**: [Relational/NoSQL/etc.]
+- **ORM/Client**: [Detected library]
+- **Rationale**: [Why this database?]
+
+## Build Tools & Package Management
+[From analysis: npm, Maven, pip, etc.]
+
+## Infrastructure
+
+### Containerization
+[Docker, Docker Compose - if detected]
+
+### CI/CD
+[GitHub Actions, GitLab CI - if detected]
+
+### Hosting
+[Vercel, AWS, Heroku - if detected or known]
+
+## Development Tools
+
+### Linting & Formatting
+[ESLint, Prettier, Black - from analysis]
+
+### Type Checking
+[TypeScript, MyPy - from analysis]
+
+## Key Dependencies
+[List major dependencies from package files]
+
+## Version Management
+[How versions are managed]
+
+## Migration Path (for legacy projects)
+[If applicable - planned upgrades]
+
+---
+*Last Updated*: [Date]
+*Auto-detected*: [List what was auto-detected vs user-provided]
+```

package/dist/skills/flow-init/references/vision-templates.md

@@ -1,75 +1,75 @@
-# Vision Document Templates
-
-Select the appropriate template based on project type detected by project-analyzer.
-
-## New Project
-
-```markdown
-# Project Vision
-
-## Pitch
-[PROJECT_NAME] is a [TYPE] that helps [TARGET_USERS] [SOLVE_PROBLEM] by [VALUE_PROPOSITION].
-
-## Problem Statement
-[What problem are you solving? Why does it matter?]
-
-## Target Users
-[Who will use this? What are their needs?]
-
-## Key Features
-[Core features that deliver value]
-
-## Success Criteria
-[How will you measure success?]
-
-## Differentiators
-[What makes this unique?]
-```
-
-## Existing Project
-
-```markdown
-# Project Vision
-
-## Overview
-[PROJECT_NAME] is a [TYPE] that [CURRENT_PURPOSE].
-
-## Current State
-- **Age**: [X years/months]
-- **Status**: [Active development/Maintenance/etc.]
-- **Users**: [Current user base]
-- **Tech Stack**: [Primary technologies]
-
-## Purpose
-[Why this project exists, what problem it solves]
-
-## Goals (Next 6-12 Months)
-[Planned improvements and new features]
-
-## Evolution
-[How the project has changed, where it's headed]
-```
-
-## Legacy Project
-
-```markdown
-# Project Vision
-
-## Overview
-[PROJECT_NAME] is a [TYPE] built [X years ago] to [ORIGINAL_PURPOSE].
-
-## Current State
-- **Age**: [X years]
-- **Tech Stack**: [Current technologies - note outdated items]
-- **Technical Debt**: [Assessment from analysis]
-- **Status**: [Production/Maintenance/Migration planned]
-
-## Modernization Goals
-[What needs to be updated and why]
-
-## Migration Strategy
-[If applicable - path from legacy to modern stack]
-
-## Business Value
-[Why maintain/modernize this system]
-```
+# Vision Document Templates
+
+Select the appropriate template based on project type detected by project-analyzer.
+
+## New Project
+
+```markdown
+# Project Vision
+
+## Pitch
+[PROJECT_NAME] is a [TYPE] that helps [TARGET_USERS] [SOLVE_PROBLEM] by [VALUE_PROPOSITION].
+
+## Problem Statement
+[What problem are you solving? Why does it matter?]
+
+## Target Users
+[Who will use this? What are their needs?]
+
+## Key Features
+[Core features that deliver value]
+
+## Success Criteria
+[How will you measure success?]
+
+## Differentiators
+[What makes this unique?]
+```
+
+## Existing Project
+
+```markdown
+# Project Vision
+
+## Overview
+[PROJECT_NAME] is a [TYPE] that [CURRENT_PURPOSE].
+
+## Current State
+- **Age**: [X years/months]
+- **Status**: [Active development/Maintenance/etc.]
+- **Users**: [Current user base]
+- **Tech Stack**: [Primary technologies]
+
+## Purpose
+[Why this project exists, what problem it solves]
+
+## Goals (Next 6-12 Months)
+[Planned improvements and new features]
+
+## Evolution
+[How the project has changed, where it's headed]
+```
+
+## Legacy Project
+
+```markdown
+# Project Vision
+
+## Overview
+[PROJECT_NAME] is a [TYPE] built [X years ago] to [ORIGINAL_PURPOSE].
+
+## Current State
+- **Age**: [X years]
+- **Tech Stack**: [Current technologies - note outdated items]
+- **Technical Debt**: [Assessment from analysis]
+- **Status**: [Production/Maintenance/Migration planned]
+
+## Modernization Goals
+[What needs to be updated and why]
+
+## Migration Strategy
+[If applicable - path from legacy to modern stack]
+
+## Business Value
+[Why maintain/modernize this system]
+```