owflow 0.6.0 → 0.7.0

package/dist/commands/reviews-reality-check.md

@@ -1,110 +1,110 @@
----
-name: owflow:reviews-reality-check
-description: Comprehensive reality assessment of completed work to verify it actually works and is production-ready
----
-
-**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="reality-assessor" NOW. Pass the task path in the prompt. Do not read files, explore code, or execute workflow steps yourself.
-
-You are running a comprehensive reality check using the `reality-assessor` agent.
-
-## Your Task
-
-You are performing no-nonsense reality assessment to determine if completed work actually works and solves the business problem.
-
-## Parse User Request
-
-**Determine the following from the user's request:**
-
-1. **Task path**:
-   - If provided: Use the specified task directory path
-   - If not provided: Use question to ask for task path
-
-## Your Instructions
-
-**Invoke the reality-assessor agent NOW using the Task tool:**
-
-```
-Task Tool:
-- subagent_type: reality-assessor
-- description: Reality assessment
-- prompt: |
-    You are the reality-assessor agent. Assess the reality of completion for: [task-path]
-
-    Your task:
-    1. Load all available verification reports (implementation-verifier, pragmatic-review.md, code-review-report.md, spec-audit.md)
-    2. Assess claimed completion (check implementation-plan.md markers, test results, verification status)
-    3. Validate functional completeness:
-       - Run tests yourself (don't trust reports)
-       - Test end-to-end workflows (not just unit tests)
-       - Try error scenarios (invalid inputs, edge cases, realistic data)
-       - Test integration with dependent systems
-       - Test under realistic conditions
-    4. Identify reality gaps (functionality, quality, production readiness)
-    5. Check integration points (data flow, API contracts, auth, external systems)
-    6. Generate reality assessment report with clear deployment decision
-
-    Save report to: verification/reality-check.md
-
-    Focus on: Does this ACTUALLY work for intended purpose? Functional reality over technical perfection.
-
-    Provide clear deployment decision: ✅ Ready | ⚠️ Issues Found | ❌ Not Ready
-```
-
-**Wait for the agent to complete before proceeding.**
-
-The reality-assessor agent will:
-
-1. Review all available verification reports
-2. Validate claimed completions through independent testing
-3. Test end-to-end functionality (not just isolated tests)
-4. Identify gaps between claims and reality
-5. Check integration with rest of system
-6. Assess production readiness
-7. Provide pragmatic action plan (if gaps exist)
-8. Make clear GO/NO-GO deployment decision
-
-## Examples
-
-**Example 1**: Reality check before deployment
-
-```
-User: /owflow:reviews-reality-check .owflow/tasks/development/2025-11-17-payment-processing/
-```
-
-**Example 2**: Verify claimed completion
-
-```
-User: /owflow:reviews-reality-check .owflow/tasks/development/2025-11-17-login-timeout/
-```
-
-**Example 3**: Production readiness check
-
-```
-User: /owflow:reviews-reality-check .owflow/tasks/development/2025-11-17-user-dashboard/ --production
-```
-
-## What to Expect
-
-The reality-assessor will provide:
-
-- Reality vs claims gap analysis
-- Critical gaps preventing deployment (Critical severity)
-- Quality gaps affecting reliability (High/Medium severity)
-- Integration issues with system components
-- Functional completeness percentage assessment
-- Pragmatic action plan with specific steps
-- Clear deployment decision (✅ Ready | ⚠️ Issues | ❌ Not Ready)
-- Evidence-based assessment (test results, error messages, observed behavior)
-
-## Notes
-
-- This is validation only - no code will be modified
-- Runs actual tests and workflows, doesn't just read reports
-- Tests with realistic data and scenarios
-- Checks production configuration and deployment readiness
-- Focus on: Does it ACTUALLY work and solve the problem?
-- Severity levels guide deployment decision:
-  - **Critical**: Must fix before deployment (prevents GO decision)
-  - **High**: Should fix soon (allows conditional GO with monitoring)
-  - **Medium**: Can deploy with known issues
-  - **Low**: Minor issues, acceptable
+---
+name: owflow:reviews-reality-check
+description: Comprehensive reality assessment of completed work to verify it actually works and is production-ready
+---
+
+**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="reality-assessor" NOW. Pass the task path in the prompt. Do not read files, explore code, or execute workflow steps yourself.
+
+You are running a comprehensive reality check using the `reality-assessor` agent.
+
+## Your Task
+
+You are performing no-nonsense reality assessment to determine if completed work actually works and solves the business problem.
+
+## Parse User Request
+
+**Determine the following from the user's request:**
+
+1. **Task path**:
+   - If provided: Use the specified task directory path
+   - If not provided: Use question to ask for task path
+
+## Your Instructions
+
+**Invoke the reality-assessor agent NOW using the Task tool:**
+
+```
+Task Tool:
+- subagent_type: reality-assessor
+- description: Reality assessment
+- prompt: |
+    You are the reality-assessor agent. Assess the reality of completion for: [task-path]
+
+    Your task:
+    1. Load all available verification reports (implementation-verifier, pragmatic-review.md, code-review-report.md, spec-audit.md)
+    2. Assess claimed completion (check implementation-plan.md markers, test results, verification status)
+    3. Validate functional completeness:
+       - Run tests yourself (don't trust reports)
+       - Test end-to-end workflows (not just unit tests)
+       - Try error scenarios (invalid inputs, edge cases, realistic data)
+       - Test integration with dependent systems
+       - Test under realistic conditions
+    4. Identify reality gaps (functionality, quality, production readiness)
+    5. Check integration points (data flow, API contracts, auth, external systems)
+    6. Generate reality assessment report with clear deployment decision
+
+    Save report to: verification/reality-check.md
+
+    Focus on: Does this ACTUALLY work for intended purpose? Functional reality over technical perfection.
+
+    Provide clear deployment decision: ✅ Ready | ⚠️ Issues Found | ❌ Not Ready
+```
+
+**Wait for the agent to complete before proceeding.**
+
+The reality-assessor agent will:
+
+1. Review all available verification reports
+2. Validate claimed completions through independent testing
+3. Test end-to-end functionality (not just isolated tests)
+4. Identify gaps between claims and reality
+5. Check integration with rest of system
+6. Assess production readiness
+7. Provide pragmatic action plan (if gaps exist)
+8. Make clear GO/NO-GO deployment decision
+
+## Examples
+
+**Example 1**: Reality check before deployment
+
+```
+User: /owflow:reviews-reality-check .owflow/tasks/development/2025-11-17-payment-processing/
+```
+
+**Example 2**: Verify claimed completion
+
+```
+User: /owflow:reviews-reality-check .owflow/tasks/development/2025-11-17-login-timeout/
+```
+
+**Example 3**: Production readiness check
+
+```
+User: /owflow:reviews-reality-check .owflow/tasks/development/2025-11-17-user-dashboard/ --production
+```
+
+## What to Expect
+
+The reality-assessor will provide:
+
+- Reality vs claims gap analysis
+- Critical gaps preventing deployment (Critical severity)
+- Quality gaps affecting reliability (High/Medium severity)
+- Integration issues with system components
+- Functional completeness percentage assessment
+- Pragmatic action plan with specific steps
+- Clear deployment decision (✅ Ready | ⚠️ Issues | ❌ Not Ready)
+- Evidence-based assessment (test results, error messages, observed behavior)
+
+## Notes
+
+- This is validation only - no code will be modified
+- Runs actual tests and workflows, doesn't just read reports
+- Tests with realistic data and scenarios
+- Checks production configuration and deployment readiness
+- Focus on: Does it ACTUALLY work and solve the problem?
+- Severity levels guide deployment decision:
+  - **Critical**: Must fix before deployment (prevents GO decision)
+  - **High**: Should fix soon (allows conditional GO with monitoring)
+  - **Medium**: Can deploy with known issues
+  - **Low**: Minor issues, acceptable

package/dist/commands/reviews-spec-audit.md

@@ -1,114 +1,114 @@
----
-name: owflow:reviews-spec-audit
-description: Independent specification audit to verify completeness and clarity before implementation
----
-
-**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="spec-auditor" NOW. Pass the spec path in the prompt. Do not read files, explore code, or execute workflow steps yourself.
-
-You are running an independent specification audit using the `spec-auditor` agent.
-
-## Your Task
-
-You are performing senior auditor review of specifications to verify completeness, clarity, and implementability.
-
-## Parse User Request
-
-**Determine the following from the user's request:**
-
-1. **Specification path**:
-   - If provided: Use the specified spec file path
-   - If not provided: Use question to ask for spec.md path
-
-2. **Audit type**:
-   - **Pre-implementation**: Audit spec before building (default)
-   - **Post-implementation**: Audit spec vs actual implementation (if implementation exists)
-
-## Your Instructions
-
-**Invoke the spec-auditor agent NOW using the Task tool:**
-
-```
-Task Tool:
-- subagent_type: spec-auditor
-- description: Specification audit
-- prompt: |
-    You are the spec-auditor agent. Audit the specification at: [spec-path]
-
-    Your task:
-    1. Read and comprehend the specification thoroughly
-    2. [If pre-implementation]: Identify ambiguities, missing details, unclear sections
-    3. [If post-implementation]: Examine actual implementation independently
-    4. [If post-implementation]: Compare specification vs implementation
-    5. Categorize gaps (Missing/Incomplete/Incorrect/Extra/Ambiguous)
-    6. Assign severity to each finding (Critical/High/Medium/Low)
-    7. Request clarification for ambiguous specifications
-    8. Generate comprehensive audit report
-
-    [If post-implementation]:
-    - Use az CLI to verify Azure resources if applicable
-    - Use gh CLI to verify GitHub integration if applicable
-    - Examine codebase, database schemas, API endpoints, configurations
-    - Trust nothing, verify everything independently
-
-    Save report to: verification/spec-audit.md
-
-    Focus on: Evidence-based assessment. Every finding must have file:line references or clear evidence.
-```
-
-**Wait for the agent to complete before proceeding.**
-
-The spec-auditor agent will:
-
-1. Thoroughly read and understand specification
-2. Identify ambiguities, unclear sections, missing details
-3. (If post-impl) Independently examine actual implementation
-4. (If post-impl) Compare specification vs implementation using external tools
-5. Categorize gaps with evidence
-6. Assign severity with justification
-7. Ask clarifying questions for ambiguities
-8. Provide recommendations for compliance
-
-## Examples
-
-**Example 1**: Pre-implementation spec audit
-
-```
-User: /owflow:reviews-spec-audit .owflow/tasks/development/2025-11-17-user-auth/implementation/spec.md
-```
-
-**Example 2**: Post-implementation audit
-
-```
-User: /owflow:reviews-spec-audit .owflow/tasks/development/2025-11-17-user-auth/ --post-implementation
-```
-
-**Example 3**: Audit with clarification focus
-
-```
-User: /owflow:reviews-spec-audit spec.md --focus=ambiguity
-```
-
-## What to Expect
-
-The spec-auditor will provide:
-
-- Specification completeness assessment
-- Ambiguities and unclear sections identified
-- (If post-impl) Gaps between spec and implementation (Missing/Incomplete/Incorrect/Extra)
-- All findings with evidence (file:line references or absence proof)
-- Severity assessment (Critical/High/Medium/Low)
-- Clarification questions for stakeholders
-- Compliance status (✅ Compliant | ⚠️ Mostly Compliant | ❌ Non-Compliant)
-- Specific recommendations for each finding
-
-## Notes
-
-- This is analysis only - no code or specs will be modified
-- Senior auditor perspective: healthy skepticism, verify independently
-- Uses external tools (az CLI, gh CLI) for deployment verification
-- Focus on functional reality, not theoretical compliance
-- Severity levels guide prioritization:
-  - **Critical**: Breaks core functionality, blocks deployment
-  - **High**: Important feature missing/incorrect
-  - **Medium**: Nice-to-have missing, workarounds exist
-  - **Low**: Minor discrepancy, low user impact
+---
+name: owflow:reviews-spec-audit
+description: Independent specification audit to verify completeness and clarity before implementation
+---
+
+**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="spec-auditor" NOW. Pass the spec path in the prompt. Do not read files, explore code, or execute workflow steps yourself.
+
+You are running an independent specification audit using the `spec-auditor` agent.
+
+## Your Task
+
+You are performing senior auditor review of specifications to verify completeness, clarity, and implementability.
+
+## Parse User Request
+
+**Determine the following from the user's request:**
+
+1. **Specification path**:
+   - If provided: Use the specified spec file path
+   - If not provided: Use question to ask for spec.md path
+
+2. **Audit type**:
+   - **Pre-implementation**: Audit spec before building (default)
+   - **Post-implementation**: Audit spec vs actual implementation (if implementation exists)
+
+## Your Instructions
+
+**Invoke the spec-auditor agent NOW using the Task tool:**
+
+```
+Task Tool:
+- subagent_type: spec-auditor
+- description: Specification audit
+- prompt: |
+    You are the spec-auditor agent. Audit the specification at: [spec-path]
+
+    Your task:
+    1. Read and comprehend the specification thoroughly
+    2. [If pre-implementation]: Identify ambiguities, missing details, unclear sections
+    3. [If post-implementation]: Examine actual implementation independently
+    4. [If post-implementation]: Compare specification vs implementation
+    5. Categorize gaps (Missing/Incomplete/Incorrect/Extra/Ambiguous)
+    6. Assign severity to each finding (Critical/High/Medium/Low)
+    7. Request clarification for ambiguous specifications
+    8. Generate comprehensive audit report
+
+    [If post-implementation]:
+    - Use az CLI to verify Azure resources if applicable
+    - Use gh CLI to verify GitHub integration if applicable
+    - Examine codebase, database schemas, API endpoints, configurations
+    - Trust nothing, verify everything independently
+
+    Save report to: verification/spec-audit.md
+
+    Focus on: Evidence-based assessment. Every finding must have file:line references or clear evidence.
+```
+
+**Wait for the agent to complete before proceeding.**
+
+The spec-auditor agent will:
+
+1. Thoroughly read and understand specification
+2. Identify ambiguities, unclear sections, missing details
+3. (If post-impl) Independently examine actual implementation
+4. (If post-impl) Compare specification vs implementation using external tools
+5. Categorize gaps with evidence
+6. Assign severity with justification
+7. Ask clarifying questions for ambiguities
+8. Provide recommendations for compliance
+
+## Examples
+
+**Example 1**: Pre-implementation spec audit
+
+```
+User: /owflow:reviews-spec-audit .owflow/tasks/development/2025-11-17-user-auth/implementation/spec.md
+```
+
+**Example 2**: Post-implementation audit
+
+```
+User: /owflow:reviews-spec-audit .owflow/tasks/development/2025-11-17-user-auth/ --post-implementation
+```
+
+**Example 3**: Audit with clarification focus
+
+```
+User: /owflow:reviews-spec-audit spec.md --focus=ambiguity
+```
+
+## What to Expect
+
+The spec-auditor will provide:
+
+- Specification completeness assessment
+- Ambiguities and unclear sections identified
+- (If post-impl) Gaps between spec and implementation (Missing/Incomplete/Incorrect/Extra)
+- All findings with evidence (file:line references or absence proof)
+- Severity assessment (Critical/High/Medium/Low)
+- Clarification questions for stakeholders
+- Compliance status (✅ Compliant | ⚠️ Mostly Compliant | ❌ Non-Compliant)
+- Specific recommendations for each finding
+
+## Notes
+
+- This is analysis only - no code or specs will be modified
+- Senior auditor perspective: healthy skepticism, verify independently
+- Uses external tools (az CLI, gh CLI) for deployment verification
+- Focus on functional reality, not theoretical compliance
+- Severity levels guide prioritization:
+  - **Critical**: Breaks core functionality, blocks deployment
+  - **High**: Important feature missing/incorrect
+  - **Medium**: Nice-to-have missing, workarounds exist
+  - **Low**: Minor discrepancy, low user impact