owflow 0.1.2 → 0.1.4

package/README.md

@@ -1,169 +1,169 @@
-![Owflow logo](logo.png)
-
-# Owflow
-
-**Structured, standards-aware development workflows for OpenCode**
-
-Describe what you want to build, and the plugin handles the rest - from specification through implementation to verification - while enforcing your project's coding standards at every step.
-
-Started as a simple OpenCode fork of [Maister Claude Code plugin](https://github.com/SkillPanel/maister), Owflow aims to deliver production ready workflows using the full [Opencode](https://opencode.ai/) plugin support.
-
-## What You Get
-
-- **Guided workflows** for features, bug fixes, enhancements, performance, migrations, research, and product design
-- **Auto-discovered standards** from your codebase - config files, source patterns, and documentation are analyzed and enforced throughout every workflow
-- **Test-driven implementation** with automated planning, incremental verification, and full test suite runs before completion
-- **Pause and resume** any workflow - state is preserved across sessions
-- **Production readiness checks** including code review, reality assessment, and pragmatic over-engineering detection
-
-## Getting Started
-
-### Prerequisites
-
-- [Opencode](https://opencode.ai/) CLI installed and configured
-- [Node.js](https://nodejs.org/) >= 25
-
-### Installation
-
-#### Install the plugin
-
-```bash
-npm install owflow
-```
-
-#### Add owflow to the `plugin` array in your `opencode.json` ([global or project-level](https://opencode.ai/docs/plugins/#load-order)):
-
-```json
-{
-  "plugin": ["owflow"]
-}
-```
-
-### Initial project setup
-
-Initialize your project to auto-detect coding standards and generate project documentation:
-
-```bash
-/flow-init
-```
-
-This scans your codebase and creates `.owflow/` with standards, docs, and task folders. May take a few minutes on larger projects.
-
-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
-```
-
-### First Workflow
-
-```bash
-/development Add user profile page with avatar upload
-```
-
-Or just discuss your task with LLM model and then run:
-
-```bash
-/development
-```
-
-The plugin picks up context from your conversation - no arguments needed.
-
-## 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**
-4. At each phase, it asks for your input and decisions
-5. You get tested, verified code with a detailed work log
-
-All artifacts are saved in `.owflow/tasks/` organized by type and date.
-
-### Context-Aware Commands
-
-Every workflow command works without arguments. The plugin reads your current conversation to extract the task description and auto-detect the task type:
-
-```
-You: "The login page throws a 500 error when the session expires"
-You: /development
-→ Auto-detects: bug fix, extracts description from conversation
-```
-
-```
-You: /standards-update
-→ Scans conversation for patterns like "we always use..." or "prefer X over Y"
-```
-
-You can always be explicit when you prefer - arguments and flags simply override the auto-detection.
-
-## 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           |
-| `/product-design` | Product and feature design                  |
-
-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.
-
-### Quick Commands
-
-For smaller tasks that don't need a full workflow:
-
-| Command         | Use When                                                    |
-| --------------- | ----------------------------------------------------------- |
-| `/quick-plan`   | You want a plan with standards awareness before coding      |
-| `/quick-dev`    | You know what to do - just implement with standards applied |
-| `/quick-bugfix` | Quick TDD-driven bug fix — write failing test, fix, verify  |
-
-## 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
-- **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`
-
-Standards live in `.owflow/docs/standards/` and are indexed in `.owflow/docs/INDEX.md`.
-
-**Important**: Do not use plan mode with workflows (see [Best Practices](#best-practices) below).
-
-## Beta Channel
-
-Want to try experimental features before they hit stable? Install from the beta channel:
-
-TBD
-
-## Best Practices
-
-**Don't use plan mode when starting a workflow.** Planning is a built-in part of every workflow — the orchestrator creates specs, plans, and other files as it goes. Claude Code's plan mode restricts file creation, which conflicts with this. Let the workflow handle planning on its own.
-
-**Start workflows in a fresh session.** This is especially useful when chaining workflows (e.g., research → development). Research and product-design 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 or product-design workflow and want to build on those results, pass the task folder directly:
-
-```bash
-/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/product-design/2026-03-10-dashboard-redesign Implement only phase 1
-```
-
-## 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
-```
-
-## Learn More
-
-- [Workflow Details](docs/workflows.md) - phases, examples, and task structure for each workflow type
-- [Full Command Reference](docs/commands.md) - all workflow, review, utility, and quick commands
+![Owflow logo](logo.png)
+
+# Owflow
+
+**Structured, standards-aware development workflows for OpenCode**
+
+Describe what you want to build, and the plugin handles the rest - from specification through implementation to verification - while enforcing your project's coding standards at every step.
+
+Started as a simple OpenCode fork of [Maister Claude Code plugin](https://github.com/SkillPanel/maister), Owflow aims to deliver production ready workflows using the full [Opencode](https://opencode.ai/) plugin support.
+
+## What You Get
+
+- **Guided workflows** for features, bug fixes, enhancements, performance, migrations, research, and product design
+- **Auto-discovered standards** from your codebase - config files, source patterns, and documentation are analyzed and enforced throughout every workflow
+- **Test-driven implementation** with automated planning, incremental verification, and full test suite runs before completion
+- **Pause and resume** any workflow - state is preserved across sessions
+- **Production readiness checks** including code review, reality assessment, and pragmatic over-engineering detection
+
+## Getting Started
+
+### Prerequisites
+
+- [Opencode](https://opencode.ai/) CLI installed and configured
+- [Node.js](https://nodejs.org/) >= 25
+
+### Installation
+
+#### Install the plugin
+
+```bash
+npm install owflow
+```
+
+#### Add owflow to the `plugin` array in your `opencode.json` ([global or project-level](https://opencode.ai/docs/plugins/#load-order)):
+
+```json
+{
+  "plugin": ["owflow"]
+}
+```
+
+### Initial project setup
+
+Initialize your project to auto-detect coding standards and generate project documentation:
+
+```bash
+/flow-init
+```
+
+This scans your codebase and creates `.owflow/` with standards, docs, and task folders. May take a few minutes on larger projects.
+
+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
+```
+
+### First Workflow
+
+```bash
+/development Add user profile page with avatar upload
+```
+
+Or just discuss your task with Agent and then run:
+
+```bash
+/development
+```
+
+The plugin picks up context from your conversation - no arguments needed.
+
+## 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**
+4. At each phase, it asks for your input and decisions
+5. You get tested, verified code with a detailed work log
+
+All artifacts are saved in `.owflow/tasks/` organized by type and date.
+
+### Context-Aware Commands
+
+Every workflow command works without arguments. The plugin reads your current conversation to extract the task description and auto-detect the task type:
+
+```
+You: "The login page throws a 500 error when the session expires"
+You: /development
+→ Auto-detects: bug fix, extracts description from conversation
+```
+
+```
+You: /standards-update
+→ Scans conversation for patterns like "we always use..." or "prefer X over Y"
+```
+
+You can always be explicit when you prefer - arguments and flags simply override the auto-detection.
+
+## 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           |
+| `/product-design` | Product and feature design                  |
+
+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.
+
+### Quick Commands
+
+For smaller tasks that don't need a full workflow:
+
+| Command         | Use When                                                    |
+| --------------- | ----------------------------------------------------------- |
+| `/quick-plan`   | You want a plan with standards awareness before coding      |
+| `/quick-dev`    | You know what to do - just implement with standards applied |
+| `/quick-bugfix` | Quick TDD-driven bug fix — write failing test, fix, verify  |
+
+## 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
+- **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`
+
+Standards live in `.owflow/docs/standards/` and are indexed in `.owflow/docs/INDEX.md`.
+
+**Important**: Do not use plan mode with workflows (see [Best Practices](#best-practices) below).
+
+## Beta Channel
+
+Want to try experimental features before they hit stable? Install from the beta channel:
+
+TBD
+
+## Best Practices
+
+**Don't use plan mode when starting a workflow.** Planning is a built-in part of every workflow — the orchestrator creates specs, plans, and other files as it goes. OpenCode's plan mode restricts file creation, which conflicts with this. Let the workflow handle planning on its own.
+
+**Start workflows in a fresh session.** This is especially useful when chaining workflows (e.g., research → development). Research and product-design 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 or product-design workflow and want to build on those results, pass the task folder directly:
+
+```bash
+/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/product-design/2026-03-10-dashboard-redesign Implement only phase 1
+```
+
+## 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
+```
+
+## Learn More
+
+- [Workflow Details](docs/workflows.md) - phases, examples, and task structure for each workflow type
+- [Full Command Reference](docs/commands.md) - all workflow, review, utility, and quick commands

package/dist/agents/e2e-test-verifier.md

@@ -299,7 +299,7 @@ Categorized by severity (Critical/Major/Minor/Cosmetic):
 Detect unavailable tools and provide setup instructions:
 
 - Install playwright-mcp
-- Configure MCP server in Claude Code
+- Configure MCP server in OpenCode
 - Restart and retry
 
 ### Application Not Running

package/dist/commands/quick-plan.md

@@ -5,7 +5,7 @@ description: Enter planning mode with AI SDLC standards awareness
 
 # Planning Mode with Standards Awareness
 
-Enter Claude Code's planning mode for a task, with automatic discovery of project standards from `.owflow/docs/`.
+Enter OpenCode's planning mode for a task, with automatic discovery of project standards from `.owflow/docs/`.
 
 ## Usage
 
@@ -37,7 +37,7 @@ Enter Claude Code's planning mode for a task, with automatic discovery of projec
 
 ### Step 2: Discover and Read Standards (BEFORE Plan Mode)
 
-**CRITICAL: This step MUST complete before calling EnterPlanMode.**
+**CRITICAL: This step MUST complete before calling Plan Agent.**
 
 1. **Check if `.owflow/docs/INDEX.md` exists**
    - **If not exists**: Note that no standards are available, skip to Step 3
@@ -56,7 +56,7 @@ Enter Claude Code's planning mode for a task, with automatic discovery of projec
 
 ### Step 3: Enter Planning Mode
 
-**Use the `EnterPlanMode` tool to trigger Claude Code's builtin planning mode.**
+**Use the `Plan agent` to trigger OpenCode's builtin planning mode.**
 
 **Standards context from Step 2 MUST actively inform all plan mode phases:**
 
@@ -70,11 +70,11 @@ The planning mode will:
 2. Launch Plan agents to design implementation approach (with standards constraints)
 3. Review and verify alignment with user intent
 4. Write final plan to plan file (with standards woven into steps)
-5. Call ExitPlanMode for user approval (gated on mandatory standards sections)
+5. Ask for user approval (gated on mandatory standards sections)
 
-### ExitPlanMode Gate: Mandatory Standards Sections
+### Approval question gate: Mandatory Standards Sections
 
-**BLOCKING: Do NOT call `ExitPlanMode` until the plan file contains these sections:**
+**BLOCKING: Do NOT call ask user for approval until the plan file contains these sections:**
 
 1. **"## Applicable Standards"** — list each standard file that was read, with key guidelines extracted from each. If no standards exist, state: "No AI SDLC standards found. Consider running `/flow-init`."
 
@@ -85,7 +85,7 @@ The planning mode will:
    - [ ] New components use TypeScript strict mode (from `standards/frontend/components.md`)
    ```
 
-If these sections are missing from the plan file, add them before calling ExitPlanMode.
+If these sections are missing from the plan file, add them before asking user for approval.
 
 ### Graceful Fallback
 
@@ -102,9 +102,9 @@ project documentation and coding standards for better consistency.
 
 1. **Parses** task description from user input
 2. **Discovers and READS** applicable standard files from `.owflow/docs/` (BEFORE plan mode)
-3. **Enters** Claude Code's builtin planning mode via `EnterPlanMode` with standards already loaded
+3. **Enters** OpenCode's builtin planning mode via delegating to `Plan Agent` with standards already loaded
 4. **Produces** a plan file with implementation approach, applicable standards, and compliance checklist
-5. **Gates** ExitPlanMode on mandatory standards sections in the plan file
+5. **Gates** Approval question on mandatory standards sections in the plan file
 
 ## Benefits Over Manual Planning
 

package/dist/index.js

@@ -7,7 +7,7 @@ import fs from "node:fs";
 import { fileURLToPath } from "url";
 import matter from "gray-matter";
 const __dirname = path.dirname(fileURLToPath(import.meta.url));
-const PLUGIN_ROOT = path.resolve(__dirname, "../..");
+const PLUGIN_ROOT = __dirname; // Points to dist/ where skills/commands/agents are copied
 /**
  * Resolves model aliases to the configured small_model value.
  * Maps common small/fast model aliases to OpenCode's small_model config.
@@ -69,7 +69,7 @@ const prepareAgent = ({ data, content }, smallModel) => {
         ...(data.hidden === "true" && { hidden: true }),
     };
 };
-export const OwflowPlugin = async ({ $, directory }) => {
+const OwflowPlugin = async ({ $, directory }) => {
     const agentBySession = new Map();
     return {
         /**
@@ -195,3 +195,4 @@ and determine the next phase. Use the question tool at Phase Gates.`);
         },
     };
 };
+export default OwflowPlugin;

package/dist/skills/docs-manager/SKILL.md

@@ -185,7 +185,7 @@ Use this to add new documentation to the project, either from plugin baseline or
    - Ask for the filename and purpose
    - Create a template file with appropriate frontmatter and structure
 4. Update INDEX.md to include the new documentation (see "Manage INDEX.md" operation)
-5. If this is a technical standard and corresponds to a Claude Code Skill, ensure consistency
+5. If this is a technical standard and corresponds to a Agent Skill, ensure consistency
 
 **Result:** New documentation is added to the project and indexed in INDEX.md.
 
@@ -211,7 +211,7 @@ Use this to help the user update or modify existing project documentation.
    - Check if INDEX.md needs updating (if the purpose/description changed significantly)
    - If updating tech-stack.md or architecture.md, suggest reviewing AGENTS.md for consistency
 6. For technical standards:
-   - If a corresponding Claude Code Skill exists, suggest reviewing it for consistency
+   - If a corresponding Agent Skill exists, suggest reviewing it for consistency
    - Standards should align with actual code patterns in the project
 
 **Result:** Documentation is updated to reflect current project state and team decisions.
@@ -273,7 +273,7 @@ Use this to ensure the project's AGENTS.md properly integrates with the document
 2. If it doesn't exist, ask the user if they want to create it
 3. Look for a documentation reference section in AGENTS.md
 4. If the section doesn't exist or is incomplete:
-   - Read `references/claude-md-template.md` for the template
+   - Read `references/agents-md-template.md` for the template
    - Add the template section to AGENTS.md
 5. Ensure the documentation section is placed prominently in AGENTS.md (near the top)
 6. Verify that the INDEX.md path is correct and the file exists
@@ -307,7 +307,7 @@ Use this to check that documentation is consistent, up-to-date, and properly int
    - Check if they contain placeholder text vs. actual project information
    - Warn if critical documentation is missing or empty
 5. **Check standards consistency:**
-   - If Claude Code Skills exist, check if corresponding standards documentation exists
+   - If Agent Skills exist, check if corresponding standards documentation exists
    - If standards exist without skills, suggest creating skills (if appropriate)
    - Report any inconsistencies
 6. **Generate validation report:**
@@ -330,42 +330,42 @@ Use this to check that documentation is consistent, up-to-date, and properly int
 
 ```
 User: "Set up documentation for this project"
-Claude: [Executes Initialize Documentation - creates structure, copies baseline docs, generates INDEX.md, updates AGENTS.md, gathers project info]
+Agent: [Executes Initialize Documentation - creates structure, copies baseline docs, generates INDEX.md, updates AGENTS.md, gathers project info]
 ```
 
 **Update project vision:**
 
 ```
 User: "I want to update our project vision to include AI-first approach"
-Claude: [Executes Update Documentation - reads current vision.md, helps user edit it, updates INDEX.md if needed]
+Agent: [Executes Update Documentation - reads current vision.md, helps user edit it, updates INDEX.md if needed]
 ```
 
 **Add custom documentation:**
 
 ```
 User: "Add documentation for our deployment process"
-Claude: [Executes Add Documentation File - creates custom project/deployment.md, updates INDEX.md]
+Agent: [Executes Add Documentation File - creates custom project/deployment.md, updates INDEX.md]
 ```
 
 **Reference plugin baseline:**
 
 ```
 User: "Show me the plugin's baseline error handling standard"
-Claude: [Executes Use Plugin Documentation as Reference - shows plugin baseline, compares with project version, no changes unless user requests]
+Agent: [Executes Use Plugin Documentation as Reference - shows plugin baseline, compares with project version, no changes unless user requests]
 ```
 
 **Validate documentation:**
 
 ```
 User: "Check if our documentation is complete and consistent"
-Claude: [Executes Validate Documentation Consistency - checks structure, INDEX.md, AGENTS.md integration, generates report]
+Agent: [Executes Validate Documentation Consistency - checks structure, INDEX.md, AGENTS.md integration, generates report]
 ```
 
 **Manage INDEX.md:**
 
 ```
 User: "Rebuild the documentation index"
-Claude: [Executes Manage INDEX.md - scans .owflow/docs/, regenerates comprehensive INDEX.md]
+Agent: [Executes Manage INDEX.md - scans .owflow/docs/, regenerates comprehensive INDEX.md]
 ```
 
 ---