owflow 0.4.2 → 0.5.0

package/dist/commands/performance.md

@@ -1,36 +0,0 @@
----
-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]
----
-
-CRITICAL INSTRUCTION: You MUST invoke the owflow:performance skill immediately as your FIRST action.
-
-Use the Skill tool with these exact parameters:
-name: "performance"
-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 this workflow by using /owflow:performance.
-Invoke the skill now and let it orchestrate the complete workflow.
-
----
-
-## About This Workflow
-
-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.
-
-The skill handles:
-
-- Task directory creation and state management
-- Phase execution with interactive gates
-- Subagent delegation for specialized work
-- Pause/resume capability
-
-See `skills/performance/SKILL.md` for complete workflow documentation.

package/dist/commands/research-brainstorm.md

@@ -1,33 +0,0 @@
----
-name: owflow:research-brainstorm
-description: Research skill — optional step. Brainstorms solution alternatives from multiple perspectives and records them for the later convergence step. Invoking this step means you chose to brainstorm.
-argument-hint: "[task-path-or-identifier]"
----
-
-CRITICAL INSTRUCTION: You MUST invoke the owflow:research-brainstorm skill immediately as your FIRST action.
-
-Use the Skill tool with these exact parameters:
-name: "research-brainstorm"
-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 this workflow step by using /owflow:research-brainstorm.
-Invoke the skill now and let it execute the step, update orchestrator state,
-and present results with next-step suggestions.
-
----
-
-## About This Workflow
-
-Part of the research workflow. See `skills/research-brainstorm/SKILL.md` for complete step documentation.
-
-Entry points:
-
-- `/owflow:research <description | task-path>` — start or resume a research task (assisted mode)
-- `/owflow:goal-research <description>` — run all steps in one loop (orchestrated mode)

package/dist/commands/research-converge.md

@@ -1,33 +0,0 @@
----
-name: owflow:research-converge
-description: Research skill — optional step after brainstorming. Walks through every decision area one at a time — all alternatives with full detail, one question per area — and records the chosen approach for each.
-argument-hint: "[task-path-or-identifier]"
----
-
-CRITICAL INSTRUCTION: You MUST invoke the owflow:research-converge skill immediately as your FIRST action.
-
-Use the Skill tool with these exact parameters:
-name: "research-converge"
-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 this workflow step by using /owflow:research-converge.
-Invoke the skill now and let it execute the step, update orchestrator state,
-and present results with next-step suggestions.
-
----
-
-## About This Workflow
-
-Part of the research workflow. See `skills/research-converge/SKILL.md` for complete step documentation.
-
-Entry points:
-
-- `/owflow:research <description | task-path>` — start or resume a research task (assisted mode)
-- `/owflow:goal-research <description>` — run all steps in one loop (orchestrated mode)

package/dist/commands/research-design.md

@@ -1,33 +0,0 @@
----
-name: owflow:research-design
-description: Research skill — optional step. Asks for your design preferences, creates the high-level architecture design together with its decision log, and refines the diagrams. Invoking this step means you chose to design.
-argument-hint: "[task-path-or-identifier]"
----
-
-CRITICAL INSTRUCTION: You MUST invoke the owflow:research-design skill immediately as your FIRST action.
-
-Use the Skill tool with these exact parameters:
-name: "research-design"
-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 this workflow step by using /owflow:research-design.
-Invoke the skill now and let it execute the step, update orchestrator state,
-and present results with next-step suggestions.
-
----
-
-## About This Workflow
-
-Part of the research workflow. See `skills/research-design/SKILL.md` for complete step documentation.
-
-Entry points:
-
-- `/owflow:research <description | task-path>` — start or resume a research task (assisted mode)
-- `/owflow:goal-research <description>` — run all steps in one loop (orchestrated mode)

package/dist/commands/research-finalize.md

@@ -1,33 +0,0 @@
----
-name: owflow:research-finalize
-description: Research skill — terminal step. Inventories all research outputs (the research report always, brainstorm and design artifacts when they exist), presents the workflow results, and gets your confirmation that the research is correct. Marks the task complete.
-argument-hint: "[task-path-or-identifier]"
----
-
-CRITICAL INSTRUCTION: You MUST invoke the owflow:research-finalize skill immediately as your FIRST action.
-
-Use the Skill tool with these exact parameters:
-name: "research-finalize"
-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 this workflow step by using /owflow:research-finalize.
-Invoke the skill now and let it execute the step, update orchestrator state,
-and present results with next-step suggestions.
-
----
-
-## About This Workflow
-
-Terminal step of the research workflow. Inventory of outputs, results box, confirmation; then assisted mode suggests development handoff. See `skills/research-finalize/SKILL.md` for complete step documentation.
-
-Entry points:
-
-- `/owflow:research <description | task-path>` — start or resume a research task (assisted mode)
-- `/owflow:goal-research <description>` — run all steps in one loop (orchestrated mode)

package/dist/commands/research-fork.md

@@ -1,40 +0,0 @@
----
-name: owflow:research-fork
-description: 'Utility command for the research workflow — fork an existing research task into a new one that diverges at a chosen completed step (the copied state is trimmed so the fork continues from that step onwards; the source stays untouched). Pass just the task path: the skill reads the source, then asks intent, fork point, and name with suggestions derived from that research.'
-argument-hint: "<task-path-or-identifier> [\"<what this fork should explore>\"] [--from=<slug>] [--name=\"...\"]"
----
-
-CRITICAL INSTRUCTION: You MUST invoke the owflow:research-fork skill immediately as your FIRST action.
-
-Use the Skill tool with these exact parameters:
-name: "research-fork"
-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 this workflow step by using /owflow:research-fork.
-Invoke the skill now and let it copy the task, update orchestrator state,
-and present the fork summary.
-
----
-
-## About This Workflow
-
-Utility skill of the research workflow — NOT a pipeline step. Copies a research task directory wholesale into a new task that diverges from the previous run at a chosen fork point (`--from=<slug>`); the copied state is trimmed to continue from the fork point onwards. See `skills/research-fork/SKILL.md` for complete documentation.
-
-Usage:
-
-- `/owflow:research-fork <task-path>` — bare path; the skill asks the remaining questions
-- `/owflow:research-fork <task-path> "explore the cost angle"` — the quoted text answers the intent question
-- `--from=<step-slug>` / `--name="<short name>"` — skip the matching question entirely
-
-Related entry points:
-
-- `/owflow:research <description | task-path>` — start or resume a research task (assisted mode)
-- `/owflow:goal-research <description>` — run all steps in one loop (orchestrated mode)
-- After forking: `/owflow:research <fork-path>` resumes the fork at the first step after the fork point.

package/dist/commands/research-gather.md

@@ -1,33 +0,0 @@
----
-name: owflow:research-gather
-description: Research skill — reads the plan's Gathering Strategy and launches the parallel information-gatherer agent fan in ONE message, then merges per-category findings. Ends the gathering step of the research workflow (findings-gathered) and continues with research-synthesize.
-argument-hint: "[task-path-or-identifier]"
----
-
-CRITICAL INSTRUCTION: You MUST invoke the owflow:research-gather skill immediately as your FIRST action.
-
-Use the Skill tool with these exact parameters:
-name: "research-gather"
-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 this workflow step by using /owflow:research-gather.
-Invoke the skill now and let it execute the step, update orchestrator state,
-and present results with next-step suggestions.
-
----
-
-## About This Workflow
-
-Part of the research workflow. See `skills/research-gather/SKILL.md` for complete step documentation.
-
-Entry points:
-
-- `/owflow:research <description | task-path>` — start or resume a research task (assisted mode)
-- `/owflow:goal-research <description>` — run all steps in one loop (orchestrated mode)

package/dist/commands/research-plan.md

@@ -1,37 +0,0 @@
----
-name: owflow:research-plan
-description: Research skill — creates the research brief, delegates methodology selection and planning to the research-planner agent, and writes the research plan with a parsable Gathering Strategy. First work phase of the research workflow; continues with research-gather.
-argument-hint: "[task-path-or-identifier | \"description\"]"
----
-
-CRITICAL INSTRUCTION: You MUST invoke the owflow:research-plan skill immediately as your FIRST action.
-
-Use the Skill tool with these exact parameters:
-name: "research-plan"
-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 this workflow step by using /owflow:research-plan.
-Invoke the skill now and let it execute the step, update orchestrator state,
-and present results with next-step suggestions.
-
----
-
-## About This Workflow
-
-Part of the research workflow. See `skills/research-plan/SKILL.md` for complete step documentation.
-
-Entry points:
-
-- `/owflow:research <description | task-path>` — start or resume a research task (assisted mode)
-- `/owflow:goal-research <description>` — run all steps in one loop (orchestrated mode)
-
-Quick lane:
-
-- `/owflow:research-quick "<description>"` — condensed research task: bootstraps a standard research task and then fuses brief, plan, gather, and synthesis into one pass — continuable with any research subskill

package/dist/commands/research-quick.md

@@ -1,37 +0,0 @@
----
-name: owflow:research-quick
-description: Research skill — the quick lane. Bootstraps a standard research task and fuses brief, plan + sources, gather, and synthesis into one condensed pass — the only place where the planner delegation, the gatherer fan, and the synthesizer delegation are condensable. Produces the same standard artifacts and state as the full lane; continuable by any research subskill at full fidelity.
-argument-hint: "[task-path-or-identifier | \"description\"]"
----
-
-CRITICAL INSTRUCTION: You MUST invoke the owflow:research-quick skill immediately as your FIRST action.
-
-Use the Skill tool with these exact parameters:
-name: "research-quick"
-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 this workflow step by using /owflow:research-quick.
-Invoke the skill now and let it execute the step, update orchestrator state,
-and present results with next-step suggestions.
-
----
-
-## About This Workflow
-
-Part of the research workflow. See `skills/research-quick/SKILL.md` for complete step documentation.
-
-Entry points:
-
-- `/owflow:research <description | task-path>` — start or resume a research task (assisted mode)
-- `/owflow:goal-research <description>` — run all steps in one loop (orchestrated mode)
-
-Quick lane:
-
-- `/owflow:research-quick "<description>"` — condensed research task: bootstraps a standard research task and then fuses brief, plan, gather, and synthesis into one pass — continuable with any research subskill

package/dist/commands/research-synthesize.md

@@ -1,33 +0,0 @@
----
-name: owflow:research-synthesize
-description: Research skill — delegates synthesis and evidence-based reporting to the research-synthesizer agent, producing the synthesis document and the comprehensive research report with per-finding confidence. Closes the research foundation (synthesis-complete) at the boundary with the optional chain (user choice).
-argument-hint: "[task-path-or-identifier]"
----
-
-CRITICAL INSTRUCTION: You MUST invoke the owflow:research-synthesize skill immediately as your FIRST action.
-
-Use the Skill tool with these exact parameters:
-name: "research-synthesize"
-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 this workflow step by using /owflow:research-synthesize.
-Invoke the skill now and let it execute the step, update orchestrator state,
-and present results with next-step suggestions.
-
----
-
-## About This Workflow
-
-Part of the research workflow. See `skills/research-synthesize/SKILL.md` for complete step documentation.
-
-Entry points:
-
-- `/owflow:research <description | task-path>` — start or resume a research task (assisted mode)
-- `/owflow:goal-research <description>` — run all steps in one loop (orchestrated mode)

package/dist/commands/research.md

@@ -1,55 +0,0 @@
----
-name: owflow:research
-description: Research workflow dispatcher. Initializes/resumes research tasks, derives the next step from state, and hands off to the matching /owflow:research-* subskill. Handles comprehensive research and analysis — technical, requirements, literature, and mixed research types with adaptive methodology, multi-source gathering, pattern synthesis, and evidence-based artifact outputs (findings documentation). Supports standalone research tasks and embedded research phases feeding development workflows.
-argument-hint: "[task description | task-path] [--from=<slug>] [--type=<type>]"
----
-
-CRITICAL INSTRUCTION: You MUST invoke the owflow:research skill immediately as your FIRST action.
-
-Use the Skill tool with these exact parameters:
-name: "research"
-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 this workflow by using /owflow:research.
-Invoke the skill now and let it dispatch the matching research step.
-
----
-
-## About This Workflow
-
-Research workflow **dispatcher** (assisted mode). The skill handles:
-
-- Task initialization/resume and state management (`orchestrator-state.yml`)
-- Research context intake and `--type` flag handling
-- Deriving the next pending step from state (descriptive slugs, NOT phase numbers)
-- Handing off to the matching `/owflow:research-*` subskill, then stopping
-
-Run `/owflow:goal-research` instead for autonomous mode (all subskills in one session with gates).
-
-Quick lane: starts only via `/owflow:research-quick "<description>"` — a condensed research task that fuses brief, plan, gather, and synthesis into one pass, continuable by any research subskill.
-
-Forking: `/owflow:research-fork <task-path> ["<what this fork should explore>"] [--from=<slug>]` copies a research task to a new task diverging at a chosen completed step (directory copied verbatim, `completed_phases` trimmed) — original task untouched. A bare task path is enough: the skill asks for the intent, fork point, and name with suggestions taken from that research.
-
-Entry points:
-
-- `/owflow:research <description>` — start or resume a research task (assisted mode)
-- `/owflow:goal-research <description>` — run all steps in one loop (orchestrated mode)
-
-Steps (each works on the shared task directory):
-
-- `/owflow:research-plan <description | task-path>` — brief, methodology & plan
-- `/owflow:research-gather <task-path>` — parallel findings fan
-- `/owflow:research-synthesize <task-path>` — synthesis & research report
-- `/owflow:research-brainstorm <task-path>` — solution alternatives (optional, user's choice)
-- `/owflow:research-converge <task-path>` — per-area decisions (after brainstorming)
-- `/owflow:research-design <task-path>` — high-level design (optional, user's choice)
-- `/owflow:research-finalize <task-path>` — completion & handoff
-
-See `skills/research/SKILL.md` for the routing table and `skills/research-*/SKILL.md` for step documentation.

package/dist/commands/rule-reviewer.md

@@ -1,38 +0,0 @@
----
-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,36 +0,0 @@
----
-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]
----
-
-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"
-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 this workflow by using /owflow:standards-discover.
-Invoke the skill now and let it orchestrate the complete workflow.
-
----
-
-## About This Workflow
-
-Discover coding standards from project configuration files, code patterns, documentation, and external sources (PRs, CI/CD)
-
-The skill handles:
-
-- Task directory creation and state management
-- Phase execution with interactive gates
-- Subagent delegation for specialized work
-- Pause/resume capability
-
-See `skills/standards-discover/SKILL.md` for complete workflow documentation.

package/dist/commands/standards-update.md

@@ -1,36 +0,0 @@
----
-name: owflow:standards-update
-description: Update or create project standards from conversation context or explicit description
-argument-hint: "[description of standard/convention] [--from=PATH]"
----
-
-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"
-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 this workflow by using /owflow:standards-update.
-Invoke the skill now and let it orchestrate the complete workflow.
-
----
-
-## About This Workflow
-
-Update or create project standards from conversation context or explicit description
-
-The skill handles:
-
-- Task directory creation and state management
-- Phase execution with interactive gates
-- Subagent delegation for specialized work
-- Pause/resume capability
-
-See `skills/standards-update/SKILL.md` for complete workflow documentation.