owflow 0.2.0 → 0.4.2

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,75 @@ 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.
+
+### Research Utility
+
+| Command                       | Use When                                                                        |
+| ----------------------------- | -------------------------------------------------------------------------------- |
+| `/owflow:research-quick "<description>"` | Condensed research: brief → plan → gather → synthesis in one pass     |
+| `/owflow:research-fork <task-path> ["<what this fork should explore>"]` | Branch a research task and re-run from the fork point with different choices |
 
 ### 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`                                                                            |
+
+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
+```
 
-All quick commands create lightweight task directories under `.owflow/tasks/quick-{type}/` with a `task.yml` for traceability.
+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,24 +216,39 @@ 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
+```
+
+**Fork a research task to diverge from it.** If you want to re-run part of a completed research with different choices while keeping the original intact, fork it. Passing the task path is enough — the skill reads that research, then asks what the fork should explore, where it should diverge, and what to call it, with suggestions drawn from the research itself:
+
+```bash
+/owflow:research-fork .owflow/tasks/research/2026-01-12-oauth-research
 ```
 
+Answer the three questions (or supply the answers up front — each one then gets skipped):
+
+```bash
+/owflow:research-fork .owflow/tasks/research/2026-01-12-oauth-research "compare scoping alternatives" \
+  --from=synthesis-complete --name="compare-scoping-alternatives"
+```
+
+The copy is verbatim (all artifacts, including those from after the fork point) and only the fork's `completed_phases` is trimmed at the fork point, so the fork resumes at the step after it. The source task is never modified.
+
 ## Known Issues
 
 **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**: