owflow 0.2.0 → 0.3.0

package/README.md

@@ -76,7 +76,7 @@ In `opencode.json`:
 Initialize your project to auto-detect coding standards and generate project documentation:
 
 ```bash
-/flow-init
+/owflow:flow-init
 ```
 
 This scans your codebase and creates `.owflow/` with standards, docs, and task folders. May take a few minutes on larger projects.
@@ -84,28 +84,28 @@ This scans your codebase and creates `.owflow/` with standards, docs, and task f
 If you have another project already using Owflow, you can reuse its standards as a starting point:
 
 ```bash
-/flow-init --standards-from=/path/to/other-project
+/owflow:flow-init --standards-from=/path/to/other-project
 ```
 
 ### First Workflow
 
 ```bash
-/development Add user profile page with avatar upload
+/owflow:development Add user profile page with avatar upload
 ```
 
 Or just discuss your task with Agent and then run:
 
 ```bash
-/development
+/owflow:development
 ```
 
-The plugin picks up context from your conversation - no arguments needed.
+The plugin picks up context from your conversation - no arguments needed. Prefer everything in one session? Use `/owflow:goal-development` (autonomous mode) instead - it runs the same pipeline without handoffs between phases (subskills run back-to-back in one session).
 
 ## How It Works
 
 1. You describe a task - either as an argument or just in conversation
 2. The plugin classifies it (feature, bug, enhancement, etc.) and proposes a workflow
-3. You confirm, and it guides you through phases: **requirements → spec → plan → implement → verify**
+3. You confirm, and it guides you through the pipeline of development subskills: **analysis → spec → plan → implement → verify → finalize**
 4. At each phase, it asks for your input and decisions
 5. You get tested, verified code with a detailed work log
 
@@ -117,12 +117,12 @@ Every workflow command works without arguments. The plugin reads your current co
 
 ```
 You: "The login page throws a 500 error when the session expires"
-You: /development
+You: /owflow:development
 → Auto-detects: bug fix, extracts description from conversation
 ```
 
 ```
-You: /standards-update
+You: /owflow:standards-update
 → Scans conversation for patterns like "we always use..." or "prefer X over Y"
 ```
 
@@ -130,35 +130,68 @@ You can always be explicit when you prefer - arguments and flags simply override
 
 ## Supported Workflows
 
-| Command        | Use When                                    |
-| -------------- | ------------------------------------------- |
-| `/development` | Features, bug fixes, enhancements           |
-| `/research`    | Research with synthesis and solution design |
-| `/performance` | Optimizing speed or resource usage          |
-| `/migration`   | Changing technologies or patterns           |
+| Command                | Use When                                    |
+| ---------------------- | ------------------------------------------- |
+| `/owflow:development`  | Features, bug fixes, enhancements           |
+| `/owflow:research`     | Research with synthesis and solution design |
+| `/owflow:performance`  | Optimizing speed or resource usage          |
+| `/owflow:migration`    | Changing technologies or patterns           |
 
-Task type (feature/bug/enhancement) is auto-detected from context. Override with `--type=feature|bug|enhancement` if needed. Or use `/work` as a single entry point that routes to the right workflow.
+Task type (feature/bug/enhancement) is auto-detected from context. Override with `--type=feature|bug|enhancement` if needed. Or use `/owflow:work` as a single entry point that routes to the right workflow.
 
 ### Quick Commands
 
 For smaller tasks that don't need a full workflow:
 
-| Command         | Use When                                                    | Artifacts                               |
-| --------------- | ----------------------------------------------------------- | --------------------------------------- |
-| `/quick-plan`   | You want a plan with standards awareness before coding      | `task.yml`, `findings.md`               |
-| `/quick-dev`    | You know what to do - just implement with standards applied | `task.yml`, `summary.md`                |
-| `/quick-bugfix` | Quick TDD-driven bug fix — write failing test, fix, verify  | `task.yml`, `findings.md`, `summary.md` |
+| Command                          | Use When                                                    | Artifacts                                                                                                                               |
+| -------------------------------- | ----------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
+| `/owflow:dev-spec --quick`       | Standards-aware, resumable spec before any plan — spec only | `orchestrator-state.yml`, `analysis/quick-analysis.md`, `analysis/requirements.md`, `implementation/spec.md`                              |
+| `/owflow:dev-plan --quick`       | Standards-aware, resumable plan before coding — plan only   | `orchestrator-state.yml`, `analysis/quick-analysis.md`, `implementation/spec.md`, `implementation/implementation-plan.md`                |
+| `/owflow:dev-implement --quick`  | Task is clear, no architectural decisions needed            | `orchestrator-state.yml`, `analysis/quick-analysis.md`, `implementation/spec.md`, `implementation/implementation-plan.md`, `work-log.md` |
+| `/owflow:dev-bugfix`             | Quick TDD-driven bug fix — write failing test, fix, verify  | `orchestrator-state.yml`, `analysis/findings.md`, `summary.md`                                                                            |
 
-All quick commands create lightweight task directories under `.owflow/tasks/quick-{type}/` with a `task.yml` for traceability.
+Every quick lane creates a standard development task under `.owflow/tasks/development/` (full `orchestrator-state.yml` with the lane as `orchestrator.entry_point`) and stops at that lane's exit gate — continuable later by any dev-* subskill (`/owflow:dev-verify`, `/owflow:development <task-path>`, …).
+
+Quick development uses the standard pipeline instead: `/owflow:dev-implement --quick "<description>"` bootstraps a regular development task (`orchestrator-state.yml`, condensed spec + plan), implements it, and stops — continue later with `/owflow:dev-verify` or stop there if the results are enough. Plan-only tasks work the same way: `/owflow:dev-plan --quick "<description>"` bootstraps a regular development task and stops after the plan — continue with `/owflow:dev-implement` or stop there if the plan is enough. Spec-only tasks condense one step further: `/owflow:dev-spec --quick "<description>"` bootstraps a regular development task and stops after the condensed specification (written directly on the fly, no specification-creator subagent; audit skipped) — continue with `/owflow:dev-plan` or stop there if the spec is enough.
+
+**The `--quick` flag is optional.** You can start from a bare prompt with any quick-lane command — the skill bootstraps the task and then asks whether to run the condensed quick lane or escalate to the full pipeline. Pass `--quick` to skip that question and go straight to the quick lane. Invoked with no argument at all, the skill prompts you for a task description, task path, or identifier. Bug-shaped descriptions route to `/owflow:dev-bugfix` instead (you can insist on proceeding if you prefer).
+
+```bash
+# Quick lane, no questions asked
+/owflow:dev-spec --quick "Add server-side pagination to the users list"
+/owflow:dev-plan --quick "Add rate limiting to the public API"
+/owflow:dev-implement --quick "Add a logout button to the navbar"
+
+# Bare prompt — the skill asks: quick lane or full pipeline?
+/owflow:dev-spec "Design the CSV export for the invoices table"
+/owflow:dev-plan "Add rate limiting to the public API"
+/owflow:dev-implement "Add CSV export to the invoices table"
+
+# No argument — prompts for a description, task path, or identifier
+/owflow:dev-spec
+/owflow:dev-plan
+/owflow:dev-implement
+```
+
+### Fine-Grained Control: Development Subskills
+
+The full `/owflow:development` workflow consists of standalone subskills — `/owflow:dev-analyze`, `/owflow:dev-tdd-red`, `/owflow:dev-spec`, `/owflow:dev-plan`, `/owflow:dev-implement`, `/owflow:dev-verify`, `/owflow:dev-finalize` — which you can also invoke individually. Each accepts a task path, or just a task-directory identifier:
+
+```bash
+/owflow:dev-spec 2026-01-12-my-feature
+/owflow:dev-verify .owflow/tasks/development/2026-01-12-my-feature
+```
+
+If a subskill is invoked too early in the workflow (prerequisite phases not yet complete), it stops and tells you exactly which steps to run first, in order. If the workflow state doesn't exist yet, use `/owflow:development <description>` to start from scratch.
 
 ## Standards-Aware Development
 
 This is the key differentiator. Owflow doesn't just run workflows - it learns your project's conventions and enforces them:
 
-- **`flow-init`** scans config files, source code, and documentation to auto-detect your coding standards
+- **`/owflow:flow-init`** scans config files, source code, and documentation to auto-detect your coding standards
 - **Continuous checking** - standards are consulted before specification, during planning, and while coding (not just at the start)
-- **`/standards-discover`** refreshes standards from your evolving codebase
-- **`/standards-update`** lets you add or refine standards manually, or sync from another project with `--from=PATH`
+- **`/owflow:standards-discover`** refreshes standards from your evolving codebase
+- **`/owflow:standards-update`** lets you add or refine standards manually, or sync from another project with `--from=PATH`
 
 Standards live in `.owflow/docs/standards/` and are indexed in `.owflow/docs/INDEX.md`.
 
@@ -176,16 +209,16 @@ TBD
 
 **Start workflows in a fresh session.** This is especially useful when chaining workflows (e.g., research → development). Research artifacts already contain all the context needed, so a clean session avoids noise from prior conversation.
 
-**Chain workflows by passing a task folder.** If you've completed a research workflow and want to build on those results, pass the task folder directly:
+**Chain workflows by passing a task folder.** If you've completed a research workflow and want to build on those results, pass the task folder directly — by path, or just by its directory identifier if the name is unique:
 
 ```bash
-/development .owflow/tasks/research/2026-01-12-oauth-research
+/owflow:development .owflow/tasks/research/2026-01-12-oauth-research
 ```
 
 You can also append additional instructions to narrow scope or guide the workflow:
 
 ```bash
-/development .owflow/tasks/research/2026-01-12-oauth-research Implement only phase 1
+/owflow:development .owflow/tasks/research/2026-01-12-oauth-research Implement only phase 1
 ```
 
 ## Known Issues
@@ -193,7 +226,7 @@ You can also append additional instructions to narrow scope or guide the workflo
 **Orchestrator may stall after long phases.** After context compaction (which typically happens after lengthy phases like implementation), the main agent may stop progressing automatically. If you notice it's idle, just type something like "continue" or "proceed" — it will pick up where it left off. You can also re-invoke the workflow in resume mode to reload the orchestrator state:
 
 ```bash
-/development .owflow/tasks/development/2026-03-24-my-feature
+/owflow:development .owflow/tasks/development/2026-03-24-my-feature
 ```
 
 ## Learn More

package/dist/agents/code-reviewer.md

@@ -228,7 +228,7 @@ issue_counts:
 
 ## Integration
 
-**Invoked by**: implementation-verifier (Phase 3), standalone via `/reviews-code` command
+**Invoked by**: implementation-verifier (Phase 3), standalone via `/owflow:reviews-code` command
 
 **Prerequisites**:
 

package/dist/agents/production-readiness-checker.md

@@ -268,7 +268,7 @@ issue_counts:
 
 ## Integration
 
-**Invoked by**: implementation-verifier (Phase 3), performance orchestrator (Phase 4), standalone via `/reviews-production-readiness` command
+**Invoked by**: implementation-verifier (Phase 3), performance orchestrator (Phase 4), standalone via `/owflow:reviews-production-readiness` command
 
 **Prerequisites**:
 

package/dist/agents/project-analyzer.md

@@ -2,7 +2,6 @@
 name: project-analyzer
 description: Analyzes project codebase to detect tech stack, architecture, and conventions for documentation generation. Use for existing/legacy projects to auto-generate meaningful documentation.
 color: blue
-model: haiku
 mode: subagent
 hidden: true
 ---

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.
 
 ---