owflow 0.2.0 → 0.4.2

package/dist/agents/task-classifier.md

@@ -370,12 +370,12 @@ Use question with relevant options
 
 ## Integration Points
 
-**With /work Command**:
+**With /owflow:work Command**:
 
-1. `/work` parses arguments and task description
+1. `/owflow:work` parses arguments and task description
 2. Invokes this agent directly via Task tool
 3. Agent performs classification and returns result
-4. `/work` routes to appropriate orchestrator
+4. `/owflow:work` routes to appropriate orchestrator
 
 **Classification Routes**:
 

package/dist/commands/agents-md-generator.md

@@ -0,0 +1,36 @@
+---
+name: owflow:agents-md-generator
+description: Generate AGENTS.md onboarding document for AI coding agents
+argument-hint: "[directory or file path]"
+---
+
+CRITICAL INSTRUCTION: You MUST invoke the owflow:agents-md-generator skill immediately as your FIRST action.
+
+Use the Skill tool with these exact parameters:
+name: "agents-md-generator"
+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:agents-md-generator.
+Invoke the skill now and let it orchestrate the complete workflow.
+
+---
+
+## About This Workflow
+
+Generates an `AGENTS.md` onboarding document for AI coding agents working in a repository. Inspects the repo (package manifest, README, scripts, lint/test config, layout, commit history) and writes a concise, reference-heavy contributor guide.
+
+The skill handles:
+
+- Repo-level vs directory-level scope detection
+- Create path (fresh generation) and Update path (surgical edits)
+- Quality guards enforcing length, specificity, and structure
+- Parallel discovery via subagents for large repos
+
+See `skills/agents-md-generator/SKILL.md` for complete workflow documentation.

package/dist/commands/dev-analyze.md

@@ -0,0 +1,33 @@
+---
+name: owflow:dev-analyze
+description: Development — codebase analysis, clarifications, gap analysis & scope decisions
+argument-hint: "[task-path-or-identifier]"
+---
+
+CRITICAL INSTRUCTION: You MUST invoke the owflow:dev-analyze skill immediately as your FIRST action.
+
+Use the Skill tool with these exact parameters:
+name: "dev-analyze"
+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 phase by using /owflow:dev-analyze.
+Invoke the skill now and let it execute the phase, update orchestrator state,
+and present results with next-step suggestions.
+
+---
+
+## About This Workflow
+
+Part of the development workflow. See `skills/dev-analyze/SKILL.md` for complete phase documentation.
+
+Entry points:
+
+- `/owflow:development <description>` — start a new development task (assisted mode)
+- `/owflow:goal-development <description>` — run all phases in one loop (orchestrated mode)

package/dist/commands/dev-bugfix.md

@@ -0,0 +1,37 @@
+---
+name: owflow:dev-bugfix
+description: Quick bug fix with TDD red/green gates and complexity escalation — standard dev-task state, continuable by any dev-* subskill
+argument-hint: "[bug description | task-path-or-identifier]"
+---
+
+CRITICAL INSTRUCTION: You MUST invoke the owflow:dev-bugfix skill immediately as your FIRST action.
+
+Use the Skill tool with these exact parameters:
+name: "dev-bugfix"
+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:dev-bugfix.
+Invoke the skill now and let it orchestrate the complete workflow.
+
+---
+
+## About This Workflow
+
+Quick bug fix with TDD red/green gates and complexity escalation. An alternative entry point into the dev-* workflow: bootstraps (or resumes) a standard development task with `orchestrator-state.yml`.
+
+Pass a bug description for a fresh fix, or a task path/identifier (under `.owflow/tasks/development/`) to fix a newly emerging problem on an existing development task.
+The skill handles:
+
+- Task directory creation and state management
+- Phase execution with interactive gates
+- Subagent delegation for specialized work
+- Pause/resume capability
+
+See `skills/dev-bugfix/SKILL.md` for complete workflow documentation.

package/dist/commands/dev-finalize.md

@@ -0,0 +1,33 @@
+---
+name: owflow:dev-finalize
+description: Development — E2E testing, user documentation & finalization
+argument-hint: "[task-path-or-identifier]"
+---
+
+CRITICAL INSTRUCTION: You MUST invoke the owflow:dev-finalize skill immediately as your FIRST action.
+
+Use the Skill tool with these exact parameters:
+name: "dev-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 phase by using /owflow:dev-finalize.
+Invoke the skill now and let it execute the phase, update orchestrator state,
+and present results with next-step suggestions.
+
+---
+
+## About This Workflow
+
+Part of the development workflow. See `skills/dev-finalize/SKILL.md` for complete phase documentation.
+
+Entry points:
+
+- `/owflow:development <description>` — start a new development task (assisted mode)
+- `/owflow:goal-development <description>` — run all phases in one loop (orchestrated mode)

package/dist/commands/dev-implement.md

@@ -0,0 +1,34 @@
+---
+name: owflow:dev-implement
+description: Development — execute implementation plan & TDD Green Gate. --quick bootstraps a condensed task when no state file exists.
+argument-hint: "[task-path-or-identifier | \"description\"] [--quick]"
+---
+
+CRITICAL INSTRUCTION: You MUST invoke the owflow:dev-implement skill immediately as your FIRST action.
+
+Use the Skill tool with these exact parameters:
+name: "dev-implement"
+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 phase by using /owflow:dev-implement.
+Invoke the skill now and let it execute the phase, update orchestrator state,
+and present results with next-step suggestions.
+
+---
+
+## About This Workflow
+
+Part of the development workflow. See `skills/dev-implement/SKILL.md` for complete phase documentation.
+
+Entry points:
+
+- `/owflow:development <description>` — start a new development task (assisted mode)
+- `/owflow:goal-development <description>` — run all phases in one loop (orchestrated mode)
+- `/owflow:dev-implement --quick "<description>"` — condensed quick task: bootstraps a standard development task (state + condensed spec/plan) here, implements it directly with standards, then stops — continuable with `/owflow:dev-verify` or any dev-* subskill

package/dist/commands/dev-plan.md

@@ -0,0 +1,37 @@
+---
+name: owflow:dev-plan
+description: Development — break the specification into a grouped implementation plan. --quick bootstraps a condensed plan-only task when no state file exists.
+argument-hint: "[task-path-or-identifier | \"description\"] [--quick]"
+---
+
+CRITICAL INSTRUCTION: You MUST invoke the owflow:dev-plan skill immediately as your FIRST action.
+
+Use the Skill tool with these exact parameters:
+name: "dev-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 phase by using /owflow:dev-plan.
+Invoke the skill now and let it execute the phase, update orchestrator state,
+and present results with next-step suggestions.
+
+---
+
+## About This Workflow
+
+Part of the development workflow. See `skills/dev-plan/SKILL.md` for complete phase documentation.
+
+Entry points:
+
+- `/owflow:development <description>` — start a new development task (assisted mode)
+- `/owflow:goal-development <description>` — run all phases in one loop (orchestrated mode)
+
+Quick lane:
+
+- `/owflow:dev-plan --quick "<description>"` — condensed plan-only task: bootstraps a standard development task (state + condensed spec), writes the implementation plan directly on the fly (no planner subagent; diagram is optional and gated by a question), then stops — continuable with `/owflow:dev-implement` or any dev-* subskill

package/dist/commands/dev-spec.md

@@ -0,0 +1,37 @@
+---
+name: owflow:dev-spec
+description: Development — requirements gathering, specification creation & audit. --quick bootstraps a condensed spec-only task when no state file exists.
+argument-hint: "[task-path-or-identifier | \"description\"] [--quick]"
+---
+
+CRITICAL INSTRUCTION: You MUST invoke the owflow:dev-spec skill immediately as your FIRST action.
+
+Use the Skill tool with these exact parameters:
+name: "dev-spec"
+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 phase by using /owflow:dev-spec.
+Invoke the skill now and let it execute the phase, update orchestrator state,
+and present results with next-step suggestions.
+
+---
+
+## About This Workflow
+
+Part of the development workflow. See `skills/dev-spec/SKILL.md` for complete phase documentation.
+
+Entry points:
+
+- `/owflow:development <description>` — start a new development task (assisted mode)
+- `/owflow:goal-development <description>` — run all phases in one loop (orchestrated mode)
+
+Quick lane:
+
+- `/owflow:dev-spec --quick "<description>"` — condensed spec-only task: bootstraps a standard development task (state + standards discovery + quick analysis), writes the condensed specification directly on the fly (no specification-creator subagent; diagrams are optional and gated by a question; audit is skipped — `/owflow:reviews-spec-audit` stays available later), then stops — continuable with `/owflow:dev-plan` or any dev-* subskill

package/dist/commands/dev-tdd-red.md

@@ -0,0 +1,33 @@
+---
+name: owflow:dev-tdd-red
+description: "Development — TDD Red Gate: write a failing test reproducing the defect"
+argument-hint: "[task-path-or-identifier]"
+---
+
+CRITICAL INSTRUCTION: You MUST invoke the owflow:dev-tdd-red skill immediately as your FIRST action.
+
+Use the Skill tool with these exact parameters:
+name: "dev-tdd-red"
+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 phase by using /owflow:dev-tdd-red.
+Invoke the skill now and let it execute the phase, update orchestrator state,
+and present results with next-step suggestions.
+
+---
+
+## About This Workflow
+
+Part of the development workflow. See `skills/dev-tdd-red/SKILL.md` for complete phase documentation.
+
+Entry points:
+
+- `/owflow:development <description>` — start a new development task (assisted mode)
+- `/owflow:goal-development <description>` — run all phases in one loop (orchestrated mode)

package/dist/commands/dev-verify.md

@@ -0,0 +1,33 @@
+---
+name: owflow:dev-verify
+description: Development — verification options, implementation verification & fix loop
+argument-hint: "[task-path-or-identifier]"
+---
+
+CRITICAL INSTRUCTION: You MUST invoke the owflow:dev-verify skill immediately as your FIRST action.
+
+Use the Skill tool with these exact parameters:
+name: "dev-verify"
+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 phase by using /owflow:dev-verify.
+Invoke the skill now and let it execute the phase, update orchestrator state,
+and present results with next-step suggestions.
+
+---
+
+## About This Workflow
+
+Part of the development workflow. See `skills/dev-verify/SKILL.md` for complete phase documentation.
+
+Entry points:
+
+- `/owflow:development <description>` — start a new development task (assisted mode)
+- `/owflow:goal-development <description>` — run all phases in one loop (orchestrated mode)

package/dist/commands/development.md

@@ -1,11 +1,10 @@
 ---
-name: development
-description: Unified orchestrator for all development tasks. ALWAYS execute when invoked — never skip for 'straightforward' tasks. Phases adapt based on detected task characteristics rather than predetermined types. Use for any development work that modifies code.
+name: owflow:development
+description: Development workflow dispatcher — initializes/resumes tasks, derives the next phase from state, and hands off to /owflow:dev-* subskills.
 argument-hint: [task description]
-generated-from-skill: true
 ---
 
-CRITICAL INSTRUCTION: You MUST invoke the development skill immediately as your FIRST action.
+CRITICAL INSTRUCTION: You MUST invoke the owflow:development skill immediately as your FIRST action.
 
 Use the Skill tool with these exact parameters:
 name: "development"
@@ -18,20 +17,20 @@ DO NOT:
 - Substitute your own approach or workflow
 - Execute any part of the workflow yourself
 
-WHY: The user explicitly chose this workflow by using /development.
+WHY: The user explicitly chose this workflow by using /owflow:development.
 Invoke the skill now and let it orchestrate the complete workflow.
 
 ---
 
 ## About This Workflow
 
-Unified orchestrator for all development tasks. ALWAYS execute when invoked — never skip for 'straightforward' tasks. Phases adapt based on detected task characteristics rather than predetermined types. Use for any development work that modifies code.
+Development workflow **dispatcher** (assisted mode). The skill handles:
 
-The skill handles:
+- Task initialization/resume and state management (`orchestrator-state.yml`)
+- Research context intake, dev-bugfix/quick-lane entry_points, and flag handling
+- Deriving the next pending phase from state
+- Handing off to the matching `/owflow:dev-*` subskill, then stopping
 
-- Task directory creation and state management
-- Phase execution with interactive gates
-- Subagent delegation for specialized work
-- Pause/resume capability
+Run `/owflow:goal-development` instead for autonomous mode (all subskills in one session with gates).
 
-See `skills/development/SKILL.md` for complete workflow documentation.
+See `skills/development/SKILL.md` for the routing table and `skills/dev-*/SKILL.md` for phase documentation.

package/dist/commands/diagrams-mermaid.md

@@ -1,11 +1,10 @@
 ---
-name: diagrams-mermaid
+name: owflow:diagrams-mermaid
 description: Generate Mermaid diagrams from natural language descriptions. Creates diagrams in markdown format with mermaid code fences. Supports flowcharts, sequence diagrams, class diagrams, state diagrams, ER diagrams, user journeys, Gantt charts, pie charts, and C4 diagrams.
 argument-hint: [diagram description]
-generated-from-skill: true
 ---
 
-CRITICAL INSTRUCTION: You MUST invoke the diagrams-mermaid skill immediately as your FIRST action.
+CRITICAL INSTRUCTION: You MUST invoke the owflow:diagrams-mermaid skill immediately as your FIRST action.
 
 Use the Skill tool with these exact parameters:
 name: "diagrams-mermaid"
@@ -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 /diagrams-mermaid.
+WHY: The user explicitly chose this workflow by using /owflow:diagrams-mermaid.
 Invoke the skill now and let it orchestrate the complete workflow.
 
 ---

package/dist/commands/flow-init.md

@@ -1,11 +1,10 @@
 ---
-name: flow-init
+name: owflow:flow-init
 description: Initialize AI SDLC framework with intelligent project analysis and documentation generation
 argument-hint: [--standards-from=PATH]
-generated-from-skill: true
 ---
 
-CRITICAL INSTRUCTION: You MUST invoke the flow-init skill immediately as your FIRST action.
+CRITICAL INSTRUCTION: You MUST invoke the owflow:flow-init skill immediately as your FIRST action.
 
 Use the Skill tool with these exact parameters:
 name: "flow-init"
@@ -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 /flow-init.
+WHY: The user explicitly chose this workflow by using /owflow:flow-init.
 Invoke the skill now and let it orchestrate the complete workflow.
 
 ---

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/goal-research.md

@@ -0,0 +1,33 @@
+---
+name: owflow:goal-research
+description: Full orchestrated research wrapper — runs ALL research steps in one session by invoking every research-* subskill in sequence with question gates between them (equivalent to the classic unified orchestrator for research). Use /owflow:research for the same lifecycle in assisted mode — tasks can mix both modes freely.
+argument-hint: "[task description | task-path] [--from=<slug>] [--type=<type>]"
+---
+
+CRITICAL INSTRUCTION: You MUST invoke the owflow:goal-research skill immediately as your FIRST action.
+
+Use the Skill tool with these exact parameters:
+name: "goal-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 the orchestrated loop by using /owflow:goal-research.
+Invoke the skill now and let it sequence all research subskills with gates between them.
+
+---
+
+## About This Workflow
+
+Autonomous mode for research tasks: initializes (or resumes) the task, then invokes every required
+research subskill in sequence (plan → gather → synthesize → optional chain as chosen at the gate → finalize),
+pausing at question gates. Shares orchestrator state with assisted mode — tasks can mix both
+modes freely (assisted mode is `/owflow:research`).
+
+See `skills/goal-research/SKILL.md` for the loop rules and
+`skills/research/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-brainstorm.md

@@ -0,0 +1,33 @@
+---
+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

@@ -0,0 +1,33 @@
+---
+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)