owflow 0.2.0 → 0.3.0

package/dist/commands/goal-development.md

@@ -0,0 +1,32 @@
+---
+name: owflow:goal-development
+description: Full orchestrated development wrapper — runs ALL development phases in one session with question gates between subskills
+argument-hint: "[task description | task-path]"
+---
+
+CRITICAL INSTRUCTION: You MUST invoke the owflow:goal-development skill immediately as your FIRST action.
+
+Use the Skill tool with these exact parameters:
+name: "goal-development"
+prompt: "$ARGUMENTS"
+
+DO NOT:
+
+- Analyze the task before invoking the skill
+- Decide the task is "straightforward" and skip the skill
+- Substitute your own approach or workflow
+- Execute any part of the workflow yourself
+
+WHY: The user explicitly chose the orchestrated loop by using /owflow:goal-development.
+Invoke the skill now and let it sequence all dev-* subskills with gates between them.
+
+---
+
+## About This Workflow
+
+Autonomous mode for the development workflow: initializes the task, then invokes every required
+dev-* subskill in sequence (analyze → tdd-red → spec → plan → implement → verify → finalize),
+pausing at question gates. Shares orchestrator state with assisted mode.
+
+See `skills/goal-development/SKILL.md` for the loop rules and
+`skills/development/SKILL.md` for the dispatcher alternative.

package/dist/commands/html-renderer.md

@@ -1,11 +1,10 @@
 ---
-name: html-renderer
+name: owflow:html-renderer
 description: Render a markdown plan, idea, RFC, or design note into a self-contained, share-ready HTML file using the warm editorial visual system. Output is a single .html file with all CSS inlined, written next to the source markdown file.
 argument-hint: [path to markdown file]
-generated-from-skill: true
 ---
 
-CRITICAL INSTRUCTION: You MUST invoke the html-renderer skill immediately as your FIRST action.
+CRITICAL INSTRUCTION: You MUST invoke the owflow:html-renderer skill immediately as your FIRST action.
 
 Use the Skill tool with these exact parameters:
 name: "html-renderer"
@@ -18,7 +17,7 @@ DO NOT:
 - Substitute your own approach or workflow
 - Execute any part of the workflow yourself
 
-WHY: The user explicitly chose this workflow by using /html-renderer.
+WHY: The user explicitly chose this workflow by using /owflow:html-renderer.
 Invoke the skill now and let it orchestrate the complete workflow.
 
 ---

package/dist/commands/migration.md

@@ -1,11 +1,10 @@
 ---
-name: migration
+name: owflow:migration
 description: Orchestrates the complete migration workflow from current state analysis through implementation to compatibility verification. Handles technology migrations, platform changes, and architecture pattern transitions with adaptive risk assessment, incremental execution, and rollback planning. Use when migrating technologies, platforms, or architecture patterns.
 argument-hint: [task description]
-generated-from-skill: true
 ---
 
-CRITICAL INSTRUCTION: You MUST invoke the migration skill immediately as your FIRST action.
+CRITICAL INSTRUCTION: You MUST invoke the owflow:migration skill immediately as your FIRST action.
 
 Use the Skill tool with these exact parameters:
 name: "migration"
@@ -18,7 +17,7 @@ DO NOT:
 - Substitute your own approach or workflow
 - Execute any part of the workflow yourself
 
-WHY: The user explicitly chose this workflow by using /migration.
+WHY: The user explicitly chose this workflow by using /owflow:migration.
 Invoke the skill now and let it orchestrate the complete workflow.
 
 ---

package/dist/commands/performance.md

@@ -1,11 +1,10 @@
 ---
-name: performance
+name: owflow:performance
 description: Orchestrates performance optimization workflows using static code analysis to identify bottlenecks (N+1 queries, missing indexes, O(n^2) algorithms, blocking I/O, memory leaks). Accepts optional user-provided profiling data. Reuses standard specification, planning, implementation, and verification phases.
 argument-hint: [task description]
-generated-from-skill: true
 ---
 
-CRITICAL INSTRUCTION: You MUST invoke the performance skill immediately as your FIRST action.
+CRITICAL INSTRUCTION: You MUST invoke the owflow:performance skill immediately as your FIRST action.
 
 Use the Skill tool with these exact parameters:
 name: "performance"
@@ -18,7 +17,7 @@ DO NOT:
 - Substitute your own approach or workflow
 - Execute any part of the workflow yourself
 
-WHY: The user explicitly chose this workflow by using /performance.
+WHY: The user explicitly chose this workflow by using /owflow:performance.
 Invoke the skill now and let it orchestrate the complete workflow.
 
 ---

package/dist/commands/research.md

@@ -1,11 +1,10 @@
 ---
-name: research
+name: owflow:research
 description: Orchestrates comprehensive research workflows from question definition through findings documentation. Handles technical, requirements, literature, and mixed research types with adaptive methodology, multi-source gathering, pattern synthesis, and evidence-based reporting. Supports standalone research tasks and embedded research phase in other workflows.
 argument-hint: [task description]
-generated-from-skill: true
 ---
 
-CRITICAL INSTRUCTION: You MUST invoke the research skill immediately as your FIRST action.
+CRITICAL INSTRUCTION: You MUST invoke the owflow:research skill immediately as your FIRST action.
 
 Use the Skill tool with these exact parameters:
 name: "research"
@@ -18,7 +17,7 @@ DO NOT:
 - Substitute your own approach or workflow
 - Execute any part of the workflow yourself
 
-WHY: The user explicitly chose this workflow by using /research.
+WHY: The user explicitly chose this workflow by using /owflow:research.
 Invoke the skill now and let it orchestrate the complete workflow.
 
 ---

package/dist/commands/reviews-code.md

@@ -1,5 +1,5 @@
 ---
-name: reviews-code
+name: owflow:reviews-code
 description: Run automated code quality, security, and performance analysis on your code
 ---
 
@@ -54,19 +54,19 @@ The code-reviewer subagent will:
 **Example 1**: Review specific task
 
 ```
-User: /reviews-code .owflow/tasks/development/2025-10-24-auth/
+User: /owflow:reviews-code .owflow/tasks/development/2025-10-24-auth/
 ```
 
 **Example 2**: Review with specific scope
 
 ```
-User: /reviews-code src/api/ --scope=security
+User: /owflow:reviews-code src/api/ --scope=security
 ```
 
 **Example 3**: Review entire project
 
 ```
-User: /reviews-code src/
+User: /owflow:reviews-code src/
 ```
 
 ## What to Expect

package/dist/commands/reviews-pragmatic.md

@@ -1,5 +1,5 @@
 ---
-name: reviews-pragmatic
+name: owflow:reviews-pragmatic
 description: Run pragmatic code review to detect over-engineering and ensure code matches project scale
 ---
 
@@ -60,19 +60,19 @@ The code-quality-pragmatist agent will:
 **Example 1**: Review specific feature
 
 ```
-User: /reviews-pragmatic .owflow/tasks/development/2025-11-17-user-management/
+User: /owflow:reviews-pragmatic .owflow/tasks/development/2025-11-17-user-management/
 ```
 
 **Example 2**: Review source directory
 
 ```
-User: /reviews-pragmatic src/features/payments/
+User: /owflow:reviews-pragmatic src/features/payments/
 ```
 
 **Example 3**: Review specific file
 
 ```
-User: /reviews-pragmatic src/services/cache-service.ts
+User: /owflow:reviews-pragmatic src/services/cache-service.ts
 ```
 
 ## What to Expect

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

@@ -1,5 +1,5 @@
 ---
-name: reviews-production-readiness
+name: owflow:reviews-production-readiness
 description: Verify production deployment readiness with comprehensive checks
 ---
 
@@ -55,19 +55,19 @@ The production-readiness-checker subagent will:
 **Example 1**: Check specific task for production
 
 ```
-User: /reviews-production-readiness .owflow/tasks/development/2025-10-24-payment-api/
+User: /owflow:reviews-production-readiness .owflow/tasks/development/2025-10-24-payment-api/
 ```
 
 **Example 2**: Check feature for staging
 
 ```
-User: /reviews-production-readiness src/features/notifications/ --target=staging
+User: /owflow:reviews-production-readiness src/features/notifications/ --target=staging
 ```
 
 **Example 3**: Comprehensive project check
 
 ```
-User: /reviews-production-readiness .
+User: /owflow:reviews-production-readiness .
 ```
 
 ## What to Expect

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

@@ -1,5 +1,5 @@
 ---
-name: reviews-reality-check
+name: owflow:reviews-reality-check
 description: Comprehensive reality assessment of completed work to verify it actually works and is production-ready
 ---
 
@@ -68,19 +68,19 @@ The reality-assessor agent will:
 **Example 1**: Reality check before deployment
 
 ```
-User: /reviews-reality-check .owflow/tasks/development/2025-11-17-payment-processing/
+User: /owflow:reviews-reality-check .owflow/tasks/development/2025-11-17-payment-processing/
 ```
 
 **Example 2**: Verify claimed completion
 
 ```
-User: /reviews-reality-check .owflow/tasks/development/2025-11-17-login-timeout/
+User: /owflow:reviews-reality-check .owflow/tasks/development/2025-11-17-login-timeout/
 ```
 
 **Example 3**: Production readiness check
 
 ```
-User: /reviews-reality-check .owflow/tasks/development/2025-11-17-user-dashboard/ --production
+User: /owflow:reviews-reality-check .owflow/tasks/development/2025-11-17-user-dashboard/ --production
 ```
 
 ## What to Expect

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

@@ -1,5 +1,5 @@
 ---
-name: reviews-spec-audit
+name: owflow:reviews-spec-audit
 description: Independent specification audit to verify completeness and clarity before implementation
 ---
 
@@ -73,19 +73,19 @@ The spec-auditor agent will:
 **Example 1**: Pre-implementation spec audit
 
 ```
-User: /reviews-spec-audit .owflow/tasks/development/2025-11-17-user-auth/implementation/spec.md
+User: /owflow:reviews-spec-audit .owflow/tasks/development/2025-11-17-user-auth/implementation/spec.md
 ```
 
 **Example 2**: Post-implementation audit
 
 ```
-User: /reviews-spec-audit .owflow/tasks/development/2025-11-17-user-auth/ --post-implementation
+User: /owflow:reviews-spec-audit .owflow/tasks/development/2025-11-17-user-auth/ --post-implementation
 ```
 
 **Example 3**: Audit with clarification focus
 
 ```
-User: /reviews-spec-audit spec.md --focus=ambiguity
+User: /owflow:reviews-spec-audit spec.md --focus=ambiguity
 ```
 
 ## What to Expect

package/dist/commands/rule-reviewer.md

@@ -0,0 +1,38 @@
+---
+name: owflow:rule-reviewer
+description: Score an AI rules file on 5 axes and produce concrete actionable fixes
+---
+
+CRITICAL INSTRUCTION: You MUST invoke the owflow:rule-reviewer skill immediately as your FIRST action.
+
+Use the Skill tool with these exact parameters:
+name: "rule-reviewer"
+prompt: "$ARGUMENTS"
+
+DO NOT:
+- Analyze the file before invoking the skill
+- Decide the task is "straightforward" and skip the skill
+- Substitute your own approach or workflow
+- Execute any part of the workflow yourself
+
+WHY: The user explicitly chose this workflow by using /owflow:rule-reviewer.
+Invoke the skill now and let it orchestrate the complete workflow.
+
+---
+
+## About This Workflow
+
+Score an AI rules file (AGENTS.md, CLAUDE.md, .cursor/rules/*.mdc, .windsurfrules,
+.github/copilot-instructions.md, or any rule-for-AI markdown) on 5 axes and return
+concrete actionable fixes. The skill is read-only by default — it produces a scorecard.
+The only edit it may apply is a section reorder, and only with explicit user approval.
+
+## Examples
+
+```
+/owflow:rule-reviewer AGENTS.md
+/owflow:rule-reviewer .cursor/rules/api.mdc
+/owflow:rule-reviewer src/api/AGENTS.md
+```
+
+See `skills/rule-reviewer/SKILL.md` for complete workflow documentation.

package/dist/commands/standards-discover.md

@@ -1,11 +1,10 @@
 ---
-name: standards-discover
+name: owflow:standards-discover
 description: Discover coding standards from project configuration files, code patterns, documentation, and external sources (PRs, CI/CD)
 argument-hint: [task description]
-generated-from-skill: true
 ---
 
-CRITICAL INSTRUCTION: You MUST invoke the standards-discover skill immediately as your FIRST action.
+CRITICAL INSTRUCTION: You MUST invoke the owflow:standards-discover skill immediately as your FIRST action.
 
 Use the Skill tool with these exact parameters:
 name: "standards-discover"
@@ -18,7 +17,7 @@ DO NOT:
 - Substitute your own approach or workflow
 - Execute any part of the workflow yourself
 
-WHY: The user explicitly chose this workflow by using /standards-discover.
+WHY: The user explicitly chose this workflow by using /owflow:standards-discover.
 Invoke the skill now and let it orchestrate the complete workflow.
 
 ---

package/dist/commands/standards-update.md

@@ -1,11 +1,10 @@
 ---
-name: standards-update
+name: owflow:standards-update
 description: Update or create project standards from conversation context or explicit description
 argument-hint: "[description of standard/convention] [--from=PATH]"
-generated-from-skill: true
 ---
 
-CRITICAL INSTRUCTION: You MUST invoke the standards-update skill immediately as your FIRST action.
+CRITICAL INSTRUCTION: You MUST invoke the owflow:standards-update skill immediately as your FIRST action.
 
 Use the Skill tool with these exact parameters:
 name: "standards-update"
@@ -18,7 +17,7 @@ DO NOT:
 - Substitute your own approach or workflow
 - Execute any part of the workflow yourself
 
-WHY: The user explicitly chose this workflow by using /standards-update.
+WHY: The user explicitly chose this workflow by using /owflow:standards-update.
 Invoke the skill now and let it orchestrate the complete workflow.
 
 ---

package/dist/commands/work.md

@@ -1,5 +1,5 @@
 ---
-name: work
+name: owflow:work
 description: Unified entry point — auto-classifies tasks and routes to appropriate workflow. ALWAYS execute when invoked via slash command.
 ---
 
@@ -12,7 +12,7 @@ Auto-classifies tasks and routes to the appropriate workflow orchestrator. Suppo
 ## Usage
 
 ```bash
-/work [task description | task folder path | issue identifier]
+/owflow:work [task description | task folder path | issue identifier]
 ```
 
 ### Input Types
@@ -31,18 +31,18 @@ Auto-classifies tasks and routes to the appropriate workflow orchestrator. Suppo
 
 ```bash
 # Resume existing task
-/work ".owflow/tasks/development/2025-10-23-login-timeout"
-/work "2025-10-26-user-auth"
+/owflow:work ".owflow/tasks/development/2025-10-23-login-timeout"
+/owflow:work "2025-10-26-user-auth"
 
 # New task (auto-classifies)
-/work "Fix login timeout error on mobile devices"
-/work "Add user authentication with email/password"
-/work "Improve dashboard loading performance"
+/owflow:work "Fix login timeout error on mobile devices"
+/owflow:work "Add user authentication with email/password"
+/owflow:work "Improve dashboard loading performance"
 
 # From issue tracker
-/work "#456"
-/work "PROJ-123"
-/work "AB#789"
+/owflow:work "#456"
+/owflow:work "PROJ-123"
+/owflow:work "AB#789"
 ```
 
 ## How It Works
@@ -145,9 +145,9 @@ Use Skill tool:
 
 Examples:
 
-- Resume development: `skill: "development"` with `args: "--resume .owflow/tasks/development/2025-10-23-fix"`
-- Restart from phase: `skill: "development"` with `args: "--resume .owflow/tasks/development/2025-10-26-auth --from=verify"`
-- Fresh attempts: `skill: "migration"` with `args: "--resume .owflow/tasks/migrations/2025-10-20-redux --reset-attempts"`
+- Resume development: `skill: "owflow:development"` with `args: "--resume .owflow/tasks/development/2025-10-23-fix"`
+- Restart from step: `skill: "owflow:development"` with `args: "--resume .owflow/tasks/development/2025-10-26-auth --from=verification-done"` (dev tasks use descriptive step slugs in `completed_phases`; other workflows use `phase-N`)
+- Fresh attempts: `skill: "owflow:migration"` with `args: "--resume .owflow/tasks/migrations/2025-10-20-redux --reset-attempts"`
 
 ### Step 3: Classify & Route New Task
 
@@ -194,9 +194,9 @@ Use Skill tool:
 
 **Routing examples:**
 
-- development (92%): `skill: "development"` with `args: "Fix login timeout error"`
-- development (88%): `skill: "development"` with `args: "Add filtering to user table"`
-- performance (95%): `skill: "performance"` with `args: "Optimize slow dashboard queries"`
+- development (92%): `skill: "owflow:development"` with `args: "Fix login timeout error"`
+- development (88%): `skill: "owflow:development"` with `args: "Add filtering to user table"`
+- performance (95%): `skill: "owflow:performance"` with `args: "Optimize slow dashboard queries"`
 
 ---
 
@@ -224,9 +224,9 @@ Then route to selected workflow using Skill tool.
 ```
 Display:
 "Task cancelled. You can:
-- Run /work again when ready
+- Run /owflow:work again when ready
 - Use specific workflow commands directly:
-  /development, /performance, etc."
+  /owflow:development, /owflow:performance, etc."
 ```
 
 ---
@@ -246,7 +246,7 @@ Display:
 
 ### With Task Classifier
 
-The `/work` command delegates classification to the task-classifier subagent via Task tool, which:
+The `/owflow:work` command delegates classification to the task-classifier subagent via Task tool, which:
 
 - Fetches issue details from GitHub/Jira/Azure DevOps (via MCP, CLI tools, or WebFetch)
 - Analyzes codebase context for better classification