owflow 0.6.0 → 0.7.0

package/dist/commands/reviews-code.md

@@ -1,90 +1,90 @@
----
-name: owflow:reviews-code
-description: Run automated code quality, security, and performance analysis on your code
----
-
-**ACTION REQUIRED**: This command delegates to a subagent. The `<command-name>` tag refers to THIS command, not the target. Invoke the code-reviewer subagent via the Task tool NOW. Pass path and scope arguments. Do not read files, explore code, or execute workflow steps yourself.
-
-You are running a comprehensive code review using the `code-reviewer` subagent.
-
-## Your Task
-
-You are performing automated code analysis to identify quality, security, and performance issues.
-
-## Parse User Request
-
-**Determine the following from the user's request:**
-
-1. **Path to analyze**:
-   - If provided: Use the specified path
-   - If not provided: Use question to ask what to analyze
-
-2. **Analysis scope**:
-   - If `--scope=quality`: Only code quality analysis
-   - If `--scope=security`: Only security analysis
-   - If `--scope=performance`: Only performance analysis
-   - If `--scope=all` or no scope: Complete analysis (recommended)
-
-## Your Instructions
-
-**Invoke the code-reviewer subagent NOW using the Task tool:**
-
-```
-Use Task tool:
-  subagent_type: "code-reviewer"
-  description: "Code quality review"
-  prompt: |
-    Analyze code at: [path from user or from question]
-    Scope: [quality|security|performance|all]
-    Report path: [path]/code-review-report.md
-```
-
-**Wait for the subagent to complete before proceeding.**
-
-The code-reviewer subagent will:
-
-1. Analyze code for complexity, duplication, and code smells
-2. Detect security vulnerabilities and hardcoded secrets
-3. Identify performance issues (N+1 queries, missing indexes, caching opportunities)
-4. Generate comprehensive report with findings categorized by severity
-5. Provide actionable recommendations with code examples
-
-## Examples
-
-**Example 1**: Review specific task
-
-```
-User: /owflow:reviews-code .owflow/tasks/development/2025-10-24-auth/
-```
-
-**Example 2**: Review with specific scope
-
-```
-User: /owflow:reviews-code src/api/ --scope=security
-```
-
-**Example 3**: Review entire project
-
-```
-User: /owflow:reviews-code src/
-```
-
-## What to Expect
-
-The code-reviewer will provide:
-
-- Summary of issues found (critical, warnings, info)
-- Detailed findings with file locations and line numbers
-- Code examples showing issues and fixes
-- Metrics on code quality, security, and performance
-- Prioritized recommendations
-- Go/no-go assessment for code review
-
-## Notes
-
-- This is analysis only - no code will be modified
-- Focus on actionable findings
-- Severity levels guide prioritization:
-  - **Critical**: Must fix before production
-  - **Warning**: Should fix before merge
-  - **Info**: Nice to have improvements
+---
+name: owflow:reviews-code
+description: Run automated code quality, security, and performance analysis on your code
+---
+
+**ACTION REQUIRED**: This command delegates to a subagent. The `<command-name>` tag refers to THIS command, not the target. Invoke the code-reviewer subagent via the Task tool NOW. Pass path and scope arguments. Do not read files, explore code, or execute workflow steps yourself.
+
+You are running a comprehensive code review using the `code-reviewer` subagent.
+
+## Your Task
+
+You are performing automated code analysis to identify quality, security, and performance issues.
+
+## Parse User Request
+
+**Determine the following from the user's request:**
+
+1. **Path to analyze**:
+   - If provided: Use the specified path
+   - If not provided: Use question to ask what to analyze
+
+2. **Analysis scope**:
+   - If `--scope=quality`: Only code quality analysis
+   - If `--scope=security`: Only security analysis
+   - If `--scope=performance`: Only performance analysis
+   - If `--scope=all` or no scope: Complete analysis (recommended)
+
+## Your Instructions
+
+**Invoke the code-reviewer subagent NOW using the Task tool:**
+
+```
+Use Task tool:
+  subagent_type: "code-reviewer"
+  description: "Code quality review"
+  prompt: |
+    Analyze code at: [path from user or from question]
+    Scope: [quality|security|performance|all]
+    Report path: [path]/code-review-report.md
+```
+
+**Wait for the subagent to complete before proceeding.**
+
+The code-reviewer subagent will:
+
+1. Analyze code for complexity, duplication, and code smells
+2. Detect security vulnerabilities and hardcoded secrets
+3. Identify performance issues (N+1 queries, missing indexes, caching opportunities)
+4. Generate comprehensive report with findings categorized by severity
+5. Provide actionable recommendations with code examples
+
+## Examples
+
+**Example 1**: Review specific task
+
+```
+User: /owflow:reviews-code .owflow/tasks/development/2025-10-24-auth/
+```
+
+**Example 2**: Review with specific scope
+
+```
+User: /owflow:reviews-code src/api/ --scope=security
+```
+
+**Example 3**: Review entire project
+
+```
+User: /owflow:reviews-code src/
+```
+
+## What to Expect
+
+The code-reviewer will provide:
+
+- Summary of issues found (critical, warnings, info)
+- Detailed findings with file locations and line numbers
+- Code examples showing issues and fixes
+- Metrics on code quality, security, and performance
+- Prioritized recommendations
+- Go/no-go assessment for code review
+
+## Notes
+
+- This is analysis only - no code will be modified
+- Focus on actionable findings
+- Severity levels guide prioritization:
+  - **Critical**: Must fix before production
+  - **Warning**: Should fix before merge
+  - **Info**: Nice to have improvements

package/dist/commands/reviews-pragmatic.md

@@ -1,99 +1,99 @@
----
-name: owflow:reviews-pragmatic
-description: Run pragmatic code review to detect over-engineering and ensure code matches project scale
----
-
-**ACTION REQUIRED**: This command delegates to a different skill. The `<command-name>` tag refers to THIS command, not the target. Call the Task tool with subagent_type="code-quality-pragmatist" NOW. Pass the path to analyze in the prompt. Do not read files, explore code, or execute workflow steps yourself.
-
-You are running a pragmatic code review using the `code-quality-pragmatist` agent.
-
-## Your Task
-
-You are performing pragmatic analysis to identify over-engineering, unnecessary complexity, and developer experience issues.
-
-## Parse User Request
-
-**Determine the following from the user's request:**
-
-1. **Path to analyze**:
-   - If provided: Use the specified path
-   - If not provided: Use question to ask what to analyze (file, directory, or task path)
-
-## Your Instructions
-
-**Invoke the code-quality-pragmatist agent NOW using the Task tool:**
-
-```
-Task Tool:
-- subagent_type: code-quality-pragmatist
-- description: Pragmatic code review
-- prompt: |
-    You are the code-quality-pragmatist agent. Review the code at: [path]
-
-    Your task:
-    1. Assess overall complexity relative to project scale (check .owflow/docs/project/ for scale)
-    2. Detect over-engineering patterns (infrastructure overkill, excessive abstraction, enterprise patterns in simple code)
-    3. Assess developer experience (setup complexity, feedback loops, error messages, consistency)
-    4. Verify requirements alignment (if spec.md available, compare implementation to requirements)
-    5. Recommend specific simplifications with before/after examples
-    6. Prioritize top 3 changes with highest impact
-
-    Generate comprehensive pragmatic review report.
-    Save to: verification/pragmatic-review.md
-
-    Focus on: Simple solutions for simple problems. Code should match project needs, not theoretical best practices.
-```
-
-**Wait for the agent to complete before proceeding.**
-
-The code-quality-pragmatist agent will:
-
-1. Assess complexity relative to project scale (MVP vs Enterprise)
-2. Detect over-engineering (Redis in MVP, excessive layers, premature optimization)
-3. Identify developer experience friction points
-4. Compare implementation to requirements (if spec available)
-5. Recommend concrete simplifications with impact estimates
-6. Provide top 3 priority actions
-
-## Examples
-
-**Example 1**: Review specific feature
-
-```
-User: /owflow:reviews-pragmatic .owflow/tasks/development/2025-11-17-user-management/
-```
-
-**Example 2**: Review source directory
-
-```
-User: /owflow:reviews-pragmatic src/features/payments/
-```
-
-**Example 3**: Review specific file
-
-```
-User: /owflow:reviews-pragmatic src/services/cache-service.ts
-```
-
-## What to Expect
-
-The code-quality-pragmatist will provide:
-
-- Complexity assessment (Low/Medium/High) relative to project scale
-- Over-engineering patterns with severity (Critical/High/Medium/Low)
-- Developer experience issues and friction points
-- Requirements alignment assessment
-- Concrete simplification recommendations with before/after examples
-- Top 3 priority actions with estimated impact
-- Summary statistics (LOC reduction potential, dependencies removable)
-
-## Notes
-
-- This is analysis only - no code will be modified
-- Focus on pragmatism: appropriate complexity for actual needs
-- Identifies unnecessary infrastructure, abstractions, and patterns
-- Severity levels guide prioritization:
-  - **Critical**: Severe over-engineering blocking development
-  - **High**: Significant unnecessary complexity
-  - **Medium**: Moderate complexity issues
-  - **Low**: Minor improvements
+---
+name: owflow:reviews-pragmatic
+description: Run pragmatic code review to detect over-engineering and ensure code matches project scale
+---
+
+**ACTION REQUIRED**: This command delegates to a different skill. The `<command-name>` tag refers to THIS command, not the target. Call the Task tool with subagent_type="code-quality-pragmatist" NOW. Pass the path to analyze in the prompt. Do not read files, explore code, or execute workflow steps yourself.
+
+You are running a pragmatic code review using the `code-quality-pragmatist` agent.
+
+## Your Task
+
+You are performing pragmatic analysis to identify over-engineering, unnecessary complexity, and developer experience issues.
+
+## Parse User Request
+
+**Determine the following from the user's request:**
+
+1. **Path to analyze**:
+   - If provided: Use the specified path
+   - If not provided: Use question to ask what to analyze (file, directory, or task path)
+
+## Your Instructions
+
+**Invoke the code-quality-pragmatist agent NOW using the Task tool:**
+
+```
+Task Tool:
+- subagent_type: code-quality-pragmatist
+- description: Pragmatic code review
+- prompt: |
+    You are the code-quality-pragmatist agent. Review the code at: [path]
+
+    Your task:
+    1. Assess overall complexity relative to project scale (check .owflow/docs/project/ for scale)
+    2. Detect over-engineering patterns (infrastructure overkill, excessive abstraction, enterprise patterns in simple code)
+    3. Assess developer experience (setup complexity, feedback loops, error messages, consistency)
+    4. Verify requirements alignment (if spec.md available, compare implementation to requirements)
+    5. Recommend specific simplifications with before/after examples
+    6. Prioritize top 3 changes with highest impact
+
+    Generate comprehensive pragmatic review report.
+    Save to: verification/pragmatic-review.md
+
+    Focus on: Simple solutions for simple problems. Code should match project needs, not theoretical best practices.
+```
+
+**Wait for the agent to complete before proceeding.**
+
+The code-quality-pragmatist agent will:
+
+1. Assess complexity relative to project scale (MVP vs Enterprise)
+2. Detect over-engineering (Redis in MVP, excessive layers, premature optimization)
+3. Identify developer experience friction points
+4. Compare implementation to requirements (if spec available)
+5. Recommend concrete simplifications with impact estimates
+6. Provide top 3 priority actions
+
+## Examples
+
+**Example 1**: Review specific feature
+
+```
+User: /owflow:reviews-pragmatic .owflow/tasks/development/2025-11-17-user-management/
+```
+
+**Example 2**: Review source directory
+
+```
+User: /owflow:reviews-pragmatic src/features/payments/
+```
+
+**Example 3**: Review specific file
+
+```
+User: /owflow:reviews-pragmatic src/services/cache-service.ts
+```
+
+## What to Expect
+
+The code-quality-pragmatist will provide:
+
+- Complexity assessment (Low/Medium/High) relative to project scale
+- Over-engineering patterns with severity (Critical/High/Medium/Low)
+- Developer experience issues and friction points
+- Requirements alignment assessment
+- Concrete simplification recommendations with before/after examples
+- Top 3 priority actions with estimated impact
+- Summary statistics (LOC reduction potential, dependencies removable)
+
+## Notes
+
+- This is analysis only - no code will be modified
+- Focus on pragmatism: appropriate complexity for actual needs
+- Identifies unnecessary infrastructure, abstractions, and patterns
+- Severity levels guide prioritization:
+  - **Critical**: Severe over-engineering blocking development
+  - **High**: Significant unnecessary complexity
+  - **Medium**: Moderate complexity issues
+  - **Low**: Minor improvements

package/dist/commands/reviews-production-readiness.md

@@ -1,113 +1,113 @@
----
-name: owflow:reviews-production-readiness
-description: Verify production deployment readiness with comprehensive checks
----
-
-**ACTION REQUIRED**: This command delegates to a subagent. The `<command-name>` tag refers to THIS command, not the target. Invoke the production-readiness-checker subagent via the Task tool NOW. Pass path and target arguments. Do not read files, explore code, or execute workflow steps yourself.
-
-You are verifying production deployment readiness using the `production-readiness-checker` subagent.
-
-## Your Task
-
-You are performing comprehensive production readiness analysis covering configuration, monitoring, error handling, performance, security, and deployment considerations.
-
-## Parse User Request
-
-**Determine the following from the user's request:**
-
-1. **Path to analyze**:
-   - If provided: Use the specified path
-   - If not provided: Use question to ask what to check
-
-2. **Target environment**:
-   - If `--target=prod`: Full production checks (recommended)
-   - If `--target=staging`: Relaxed staging checks
-   - If not specified: Assume production (full rigor)
-
-## Your Instructions
-
-**Invoke the production-readiness-checker subagent NOW using the Task tool:**
-
-```
-Use Task tool:
-  subagent_type: "production-readiness-checker"
-  description: "Production readiness check"
-  prompt: |
-    Verify production readiness at: [path from user or from question]
-    Target: [production|staging]
-    Report path: [path]/production-readiness-report.md
-```
-
-**Wait for the subagent to complete before proceeding.**
-
-The production-readiness-checker subagent will:
-
-1. Verify configuration management (env vars, secrets, feature flags)
-2. Check monitoring & observability (logging, metrics, error tracking, health checks)
-3. Assess error handling & resilience (retries, circuit breakers, graceful shutdown)
-4. Evaluate performance & scalability (connection pooling, caching, rate limiting)
-5. Review security hardening (HTTPS, CORS, security headers, vulnerabilities)
-6. Analyze deployment considerations (migrations, zero-downtime, rollback plan)
-7. Generate go/no-go deployment recommendation
-
-## Examples
-
-**Example 1**: Check specific task for production
-
-```
-User: /owflow:reviews-production-readiness .owflow/tasks/development/2025-10-24-payment-api/
-```
-
-**Example 2**: Check feature for staging
-
-```
-User: /owflow:reviews-production-readiness src/features/notifications/ --target=staging
-```
-
-**Example 3**: Comprehensive project check
-
-```
-User: /owflow:reviews-production-readiness .
-```
-
-## What to Expect
-
-The production-readiness-checker will provide:
-
-- Overall readiness score and status (Ready / Concerns / Not Ready)
-- Clear GO/NO-GO deployment decision
-- Category scores (Configuration, Monitoring, Error Handling, Performance, Security, Deployment)
-- Deployment blockers that must be fixed
-- Concerns with mitigation plans
-- Recommendations for improvements
-- Risk assessment and rollback criteria
-- Post-deployment verification checklist
-
-## Deployment Decision Outcomes
-
-**Ready to Deploy**:
-
-- All critical checks passed
-- Low risk deployment
-- Optional improvements listed
-
-**Deploy with Caution**:
-
-- No blockers but concerns exist
-- Mitigation plan required
-- Close monitoring needed
-- Medium risk
-
-**Do Not Deploy**:
-
-- Critical issues present
-- High/critical risk
-- Must fix before deployment
-
-## Notes
-
-- This is verification only - no code will be modified
-- Production checks are more rigorous than staging
-- Focus on required items first (deployment blockers)
-- Strongly recommended items should be addressed or have mitigation plan
-- Nice to have items can be addressed post-deployment
+---
+name: owflow:reviews-production-readiness
+description: Verify production deployment readiness with comprehensive checks
+---
+
+**ACTION REQUIRED**: This command delegates to a subagent. The `<command-name>` tag refers to THIS command, not the target. Invoke the production-readiness-checker subagent via the Task tool NOW. Pass path and target arguments. Do not read files, explore code, or execute workflow steps yourself.
+
+You are verifying production deployment readiness using the `production-readiness-checker` subagent.
+
+## Your Task
+
+You are performing comprehensive production readiness analysis covering configuration, monitoring, error handling, performance, security, and deployment considerations.
+
+## Parse User Request
+
+**Determine the following from the user's request:**
+
+1. **Path to analyze**:
+   - If provided: Use the specified path
+   - If not provided: Use question to ask what to check
+
+2. **Target environment**:
+   - If `--target=prod`: Full production checks (recommended)
+   - If `--target=staging`: Relaxed staging checks
+   - If not specified: Assume production (full rigor)
+
+## Your Instructions
+
+**Invoke the production-readiness-checker subagent NOW using the Task tool:**
+
+```
+Use Task tool:
+  subagent_type: "production-readiness-checker"
+  description: "Production readiness check"
+  prompt: |
+    Verify production readiness at: [path from user or from question]
+    Target: [production|staging]
+    Report path: [path]/production-readiness-report.md
+```
+
+**Wait for the subagent to complete before proceeding.**
+
+The production-readiness-checker subagent will:
+
+1. Verify configuration management (env vars, secrets, feature flags)
+2. Check monitoring & observability (logging, metrics, error tracking, health checks)
+3. Assess error handling & resilience (retries, circuit breakers, graceful shutdown)
+4. Evaluate performance & scalability (connection pooling, caching, rate limiting)
+5. Review security hardening (HTTPS, CORS, security headers, vulnerabilities)
+6. Analyze deployment considerations (migrations, zero-downtime, rollback plan)
+7. Generate go/no-go deployment recommendation
+
+## Examples
+
+**Example 1**: Check specific task for production
+
+```
+User: /owflow:reviews-production-readiness .owflow/tasks/development/2025-10-24-payment-api/
+```
+
+**Example 2**: Check feature for staging
+
+```
+User: /owflow:reviews-production-readiness src/features/notifications/ --target=staging
+```
+
+**Example 3**: Comprehensive project check
+
+```
+User: /owflow:reviews-production-readiness .
+```
+
+## What to Expect
+
+The production-readiness-checker will provide:
+
+- Overall readiness score and status (Ready / Concerns / Not Ready)
+- Clear GO/NO-GO deployment decision
+- Category scores (Configuration, Monitoring, Error Handling, Performance, Security, Deployment)
+- Deployment blockers that must be fixed
+- Concerns with mitigation plans
+- Recommendations for improvements
+- Risk assessment and rollback criteria
+- Post-deployment verification checklist
+
+## Deployment Decision Outcomes
+
+**Ready to Deploy**:
+
+- All critical checks passed
+- Low risk deployment
+- Optional improvements listed
+
+**Deploy with Caution**:
+
+- No blockers but concerns exist
+- Mitigation plan required
+- Close monitoring needed
+- Medium risk
+
+**Do Not Deploy**:
+
+- Critical issues present
+- High/critical risk
+- Must fix before deployment
+
+## Notes
+
+- This is verification only - no code will be modified
+- Production checks are more rigorous than staging
+- Focus on required items first (deployment blockers)
+- Strongly recommended items should be addressed or have mitigation plan
+- Nice to have items can be addressed post-deployment