owflow 0.6.0 → 0.7.0

package/dist/commands/work.md

@@ -1,280 +1,280 @@
----
-name: owflow:work
-description: Unified entry point — auto-classifies tasks and routes to appropriate workflow. ALWAYS execute when invoked via slash command.
----
-
-**NOTE**: This is a multi-step workflow that invokes the task-classifier subagent and orchestrator skills at specific steps. The `<command-name>` tag refers to THIS command only — you MUST still use the Skill tool to invoke those other skills when instructed below. Follow ALL steps in order.
-
-# Unified Work Entry Point
-
-Auto-classifies tasks and routes to the appropriate workflow orchestrator. Supports resuming existing tasks or starting new ones.
-
-## Usage
-
-```bash
-/owflow:work [task description | task folder path | issue identifier]
-```
-
-### Input Types
-
-| Input Type       | Example                                                           |
-| ---------------- | ----------------------------------------------------------------- |
-| Task folder path | `.owflow/tasks/development/2025-10-23-login-timeout`              |
-| Folder name only | `2025-10-26-user-auth` (searches all task types)                  |
-| Task description | `"Fix login timeout error on mobile"`                             |
-| GitHub issue     | `#456`, `GH-456`, `https://github.com/owner/repo/issues/456`      |
-| Jira ticket      | `PROJ-456`, `https://company.atlassian.net/browse/PROJ-456`       |
-| Azure DevOps     | `AB#123`, `https://dev.azure.com/org/project/_workitems/edit/123` |
-| No argument      | Prompts for input                                                 |
-
-## Examples
-
-```bash
-# Resume existing task
-/owflow:work ".owflow/tasks/development/2025-10-23-login-timeout"
-/owflow:work "2025-10-26-user-auth"
-
-# New task (auto-classifies)
-/owflow:work "Fix login timeout error on mobile devices"
-/owflow:work "Add user authentication with email/password"
-/owflow:work "Improve dashboard loading performance"
-
-# From issue tracker
-/owflow:work "#456"
-/owflow:work "PROJ-123"
-/owflow:work "AB#789"
-```
-
-## How It Works
-
-1. **Detect existing task** - If input is a task folder path, route to resume
-2. **Classify new task** - Invoke task-classifier subagent to determine workflow type
-3. **Route to workflow** - Use Skill tool to invoke appropriate orchestrator skill
-
-## Workflow Type Routing
-
-| Classification | Routes To (Skill)     |
-| -------------- | --------------------- |
-| development    | `owflow:development`  |
-| performance    | `owflow:performance`  |
-| migration      | `owflow:migration`    |
-| research       | `owflow:research`     |
-
----
-
-## Workflow
-
-### Step 1: Parse Input and Detect Task Folder
-
-**Check if input is an existing task folder:**
-
-1. Try path as-is (absolute path)
-2. Try prepending `.owflow/` (relative path)
-3. Search `.owflow/tasks/*/` for folder name match
-
-**If folder exists AND contains `orchestrator-state.yml`:**
-
-- Go to **Step 2: Resume Existing Task**
-
-**If NOT a task folder:**
-
-- Go to **Step 3: Classify & Route New Task**
-
-**If no argument provided:**
-
-- Prompt user: "What would you like to work on?" with input examples
-- Then check if input is task folder or description
-
-### Step 2: Resume Existing Task
-
-**When existing task detected:**
-
-1. Read `orchestrator-state.yml` from task folder
-2. Determine workflow type from folder path:
-
-| Folder         | Workflow Type |
-| -------------- | ------------- |
-| `development/` | development   |
-| `performance/` | performance   |
-| `migrations/`  | migration     |
-| `research/`    | research      |
-
-3. Extract status from state file:
-   - `completed`: null = in-progress, timestamp = finished
-   - `completed_phases`: derive active phase as first phase not in this list
-   - `failed_phases`: array of failed attempts
-
-4. Present status to user with question:
-
-**For In-Progress Tasks:**
-
-```
-Options:
-1. Resume from next incomplete phase
-2. Restart from specific phase
-3. Cancel
-```
-
-**For Completed Tasks:**
-
-```
-Options:
-1. View task details
-2. Create follow-up development task
-3. Re-run verification phase
-4. Cancel
-```
-
-**For Failed Tasks:**
-
-```
-Options:
-1. Resume with fresh attempts (--reset-attempts --clear-failures)
-2. Retry failed phase
-3. Restart from specific phase
-4. Cancel
-```
-
-5. **Route using Skill tool:**
-
-```
-Use Skill tool:
-  skill: "[orchestrator-name]"
-  args: "--resume [task_path] [flags]"
-```
-
-Examples:
-
-- Resume development: `skill: "owflow:development"` with `args: "--resume .owflow/tasks/development/2025-10-23-fix"`
-- Restart from step: `skill: "owflow:development"` with `args: "--resume .owflow/tasks/development/2025-10-26-auth --from=verification-done"` (development, research, performance, and migration tasks use descriptive step slugs in `completed_phases`)
-- Fresh attempts: `skill: "owflow:development"` with `args: "--resume .owflow/tasks/development/2025-10-23-fix --reset-attempts"`
-
-### Step 3: Classify & Route New Task
-
-**For new task descriptions:**
-
-1. **Invoke task-classifier subagent** to determine workflow type:
-
-```
-Use Task tool:
-  subagent_type: "task-classifier"
-  description: "Classify task type"
-  prompt: "Classify this task into a workflow type: [task description].
-           Return structured YAML classification result."
-
-The subagent will:
-- Detect issue identifiers (GitHub, Jira)
-- Fetch issue details if available
-- Analyze codebase context
-- Match keywords and calculate confidence
-- Confirm with user if needed
-- Return classification in YAML format
-```
-
-2. **Parse classification result:**
-
-```yaml
-classification:
-  task_type: [development|performance|migration|research]
-  confidence: [percentage]
-  reasoning: [explanation]
-```
-
-3. **Route to appropriate workflow using Skill tool:**
-
-```
-Display:
-  Task classified as: [task_type] ([confidence]% confidence)
-  Routing to [task_type] workflow...
-
-Use Skill tool:
-  skill: "[orchestrator-name]"
-  args: "[description]"
-```
-
-**Routing examples:**
-
-- development (92%): `skill: "owflow:development"` with `args: "Fix login timeout error"`
-- development (88%): `skill: "owflow:development"` with `args: "Add filtering to user table"`
-- performance (95%): `skill: "owflow:performance"` with `args: "Optimize slow dashboard queries"`
-
----
-
-## Error Handling
-
-### Classification Fails
-
-If task-classifier returns error:
-
-```
-Display:
-"Unable to automatically classify this task. Please select manually:"
-
-Use question with options:
-1. Development - Fix bugs, improve features, or add new capabilities
-2. Performance - Optimize speed/efficiency
-3. Migration - Move to new tech/pattern
-4. Research - Investigate and document findings
-
-Then route to selected workflow using Skill tool.
-```
-
-### User Cancels
-
-```
-Display:
-"Task cancelled. You can:
-- Run /owflow:work again when ready
-- Use specific workflow commands directly:
-  /owflow:development, /owflow:performance, etc."
-```
-
----
-
-## Resume Skill Reference
-
-| Workflow Type | Skill         | Args                                                |
-| ------------- | ------------- | --------------------------------------------------- |
-| development   | `development` | `--resume [path] [--from=<slug>] [--reset-attempts]` |
-| performance   | `performance` | `--resume [path] [--from=<slug>]`                   |
-| migration     | `migration`   | `--resume [path] [--from=<slug>]`                   |
-| research      | `research`    | `--resume [path] [--from=<slug>]`                   |
-
----
-
-## Integration Notes
-
-### With Task Classifier
-
-The `/owflow:work` command delegates classification to the task-classifier subagent via Task tool, which:
-
-- Fetches issue details from GitHub/Jira/Azure DevOps (via MCP, CLI tools, or WebFetch)
-- Analyzes codebase context for better classification
-- Uses confidence-based user confirmation
-- Returns structured classification result
-
-### With Orchestrators
-
-After classification/detection, this command routes to the appropriate orchestrator via Skill tool:
-
-- Each orchestrator handles its specific workflow (spec, plan, implement, verify, etc.)
-- State is persisted in `orchestrator-state.yml` for pause/resume
-- Auto-recovery handles common failures
-
-### With Project Documentation
-
-Uses project documentation for context:
-
-- `.owflow/docs/INDEX.md` - Project overview and standards
-- `.owflow/tasks/` - Existing task directories
-
----
-
-## Key Behaviors
-
-1. **Single entry point** - One command for all workflow types
-2. **Auto-classification** - Intelligent routing based on task description
-3. **Resume support** - Detects and resumes existing tasks
-4. **Issue integration** - Fetches details from GitHub/Jira/Azure DevOps
-5. **Direct skill invocation** - Uses Skill tool for immediate orchestrator loading
-6. **Graceful fallback** - Manual selection if classification fails
+---
+name: owflow:work
+description: Unified entry point — auto-classifies tasks and routes to appropriate workflow. ALWAYS execute when invoked via slash command.
+---
+
+**NOTE**: This is a multi-step workflow that invokes the task-classifier subagent and orchestrator skills at specific steps. The `<command-name>` tag refers to THIS command only — you MUST still use the Skill tool to invoke those other skills when instructed below. Follow ALL steps in order.
+
+# Unified Work Entry Point
+
+Auto-classifies tasks and routes to the appropriate workflow orchestrator. Supports resuming existing tasks or starting new ones.
+
+## Usage
+
+```bash
+/owflow:work [task description | task folder path | issue identifier]
+```
+
+### Input Types
+
+| Input Type       | Example                                                           |
+| ---------------- | ----------------------------------------------------------------- |
+| Task folder path | `.owflow/tasks/development/2025-10-23-login-timeout`              |
+| Folder name only | `2025-10-26-user-auth` (searches all task types)                  |
+| Task description | `"Fix login timeout error on mobile"`                             |
+| GitHub issue     | `#456`, `GH-456`, `https://github.com/owner/repo/issues/456`      |
+| Jira ticket      | `PROJ-456`, `https://company.atlassian.net/browse/PROJ-456`       |
+| Azure DevOps     | `AB#123`, `https://dev.azure.com/org/project/_workitems/edit/123` |
+| No argument      | Prompts for input                                                 |
+
+## Examples
+
+```bash
+# Resume existing task
+/owflow:work ".owflow/tasks/development/2025-10-23-login-timeout"
+/owflow:work "2025-10-26-user-auth"
+
+# New task (auto-classifies)
+/owflow:work "Fix login timeout error on mobile devices"
+/owflow:work "Add user authentication with email/password"
+/owflow:work "Improve dashboard loading performance"
+
+# From issue tracker
+/owflow:work "#456"
+/owflow:work "PROJ-123"
+/owflow:work "AB#789"
+```
+
+## How It Works
+
+1. **Detect existing task** - If input is a task folder path, route to resume
+2. **Classify new task** - Invoke task-classifier subagent to determine workflow type
+3. **Route to workflow** - Use Skill tool to invoke appropriate orchestrator skill
+
+## Workflow Type Routing
+
+| Classification | Routes To (Skill)     |
+| -------------- | --------------------- |
+| development    | `owflow:development`  |
+| performance    | `owflow:performance`  |
+| migration      | `owflow:migration`    |
+| research       | `owflow:research`     |
+
+---
+
+## Workflow
+
+### Step 1: Parse Input and Detect Task Folder
+
+**Check if input is an existing task folder:**
+
+1. Try path as-is (absolute path)
+2. Try prepending `.owflow/` (relative path)
+3. Search `.owflow/tasks/*/` for folder name match
+
+**If folder exists AND contains `orchestrator-state.yml`:**
+
+- Go to **Step 2: Resume Existing Task**
+
+**If NOT a task folder:**
+
+- Go to **Step 3: Classify & Route New Task**
+
+**If no argument provided:**
+
+- Prompt user: "What would you like to work on?" with input examples
+- Then check if input is task folder or description
+
+### Step 2: Resume Existing Task
+
+**When existing task detected:**
+
+1. Read `orchestrator-state.yml` from task folder
+2. Determine workflow type from folder path:
+
+| Folder         | Workflow Type |
+| -------------- | ------------- |
+| `development/` | development   |
+| `performance/` | performance   |
+| `migrations/`  | migration     |
+| `research/`    | research      |
+
+3. Extract status from state file:
+   - `completed`: null = in-progress, timestamp = finished
+   - `completed_phases`: derive active phase as first phase not in this list
+   - `failed_phases`: array of failed attempts
+
+4. Present status to user with question:
+
+**For In-Progress Tasks:**
+
+```
+Options:
+1. Resume from next incomplete phase
+2. Restart from specific phase
+3. Cancel
+```
+
+**For Completed Tasks:**
+
+```
+Options:
+1. View task details
+2. Create follow-up development task
+3. Re-run verification phase
+4. Cancel
+```
+
+**For Failed Tasks:**
+
+```
+Options:
+1. Resume with fresh attempts (--reset-attempts --clear-failures)
+2. Retry failed phase
+3. Restart from specific phase
+4. Cancel
+```
+
+5. **Route using Skill tool:**
+
+```
+Use Skill tool:
+  skill: "[orchestrator-name]"
+  args: "--resume [task_path] [flags]"
+```
+
+Examples:
+
+- Resume development: `skill: "owflow:development"` with `args: "--resume .owflow/tasks/development/2025-10-23-fix"`
+- Restart from step: `skill: "owflow:development"` with `args: "--resume .owflow/tasks/development/2025-10-26-auth --from=verification-done"` (development, research, performance, and migration tasks use descriptive step slugs in `completed_phases`)
+- Fresh attempts: `skill: "owflow:development"` with `args: "--resume .owflow/tasks/development/2025-10-23-fix --reset-attempts"`
+
+### Step 3: Classify & Route New Task
+
+**For new task descriptions:**
+
+1. **Invoke task-classifier subagent** to determine workflow type:
+
+```
+Use Task tool:
+  subagent_type: "task-classifier"
+  description: "Classify task type"
+  prompt: "Classify this task into a workflow type: [task description].
+           Return structured YAML classification result."
+
+The subagent will:
+- Detect issue identifiers (GitHub, Jira)
+- Fetch issue details if available
+- Analyze codebase context
+- Match keywords and calculate confidence
+- Confirm with user if needed
+- Return classification in YAML format
+```
+
+2. **Parse classification result:**
+
+```yaml
+classification:
+  task_type: [development|performance|migration|research]
+  confidence: [percentage]
+  reasoning: [explanation]
+```
+
+3. **Route to appropriate workflow using Skill tool:**
+
+```
+Display:
+  Task classified as: [task_type] ([confidence]% confidence)
+  Routing to [task_type] workflow...
+
+Use Skill tool:
+  skill: "[orchestrator-name]"
+  args: "[description]"
+```
+
+**Routing examples:**
+
+- development (92%): `skill: "owflow:development"` with `args: "Fix login timeout error"`
+- development (88%): `skill: "owflow:development"` with `args: "Add filtering to user table"`
+- performance (95%): `skill: "owflow:performance"` with `args: "Optimize slow dashboard queries"`
+
+---
+
+## Error Handling
+
+### Classification Fails
+
+If task-classifier returns error:
+
+```
+Display:
+"Unable to automatically classify this task. Please select manually:"
+
+Use question with options:
+1. Development - Fix bugs, improve features, or add new capabilities
+2. Performance - Optimize speed/efficiency
+3. Migration - Move to new tech/pattern
+4. Research - Investigate and document findings
+
+Then route to selected workflow using Skill tool.
+```
+
+### User Cancels
+
+```
+Display:
+"Task cancelled. You can:
+- Run /owflow:work again when ready
+- Use specific workflow commands directly:
+  /owflow:development, /owflow:performance, etc."
+```
+
+---
+
+## Resume Skill Reference
+
+| Workflow Type | Skill         | Args                                                |
+| ------------- | ------------- | --------------------------------------------------- |
+| development   | `development` | `--resume [path] [--from=<slug>] [--reset-attempts]` |
+| performance   | `performance` | `--resume [path] [--from=<slug>]`                   |
+| migration     | `migration`   | `--resume [path] [--from=<slug>]`                   |
+| research      | `research`    | `--resume [path] [--from=<slug>]`                   |
+
+---
+
+## Integration Notes
+
+### With Task Classifier
+
+The `/owflow:work` command delegates classification to the task-classifier subagent via Task tool, which:
+
+- Fetches issue details from GitHub/Jira/Azure DevOps (via MCP, CLI tools, or WebFetch)
+- Analyzes codebase context for better classification
+- Uses confidence-based user confirmation
+- Returns structured classification result
+
+### With Orchestrators
+
+After classification/detection, this command routes to the appropriate orchestrator via Skill tool:
+
+- Each orchestrator handles its specific workflow (spec, plan, implement, verify, etc.)
+- State is persisted in `orchestrator-state.yml` for pause/resume
+- Auto-recovery handles common failures
+
+### With Project Documentation
+
+Uses project documentation for context:
+
+- `.owflow/docs/INDEX.md` - Project overview and standards
+- `.owflow/tasks/` - Existing task directories
+
+---
+
+## Key Behaviors
+
+1. **Single entry point** - One command for all workflow types
+2. **Auto-classification** - Intelligent routing based on task description
+3. **Resume support** - Detects and resumes existing tasks
+4. **Issue integration** - Fetches details from GitHub/Jira/Azure DevOps
+5. **Direct skill invocation** - Uses Skill tool for immediate orchestrator loading
+6. **Graceful fallback** - Manual selection if classification fails

package/dist/configuration/agents-config.d.ts

@@ -0,0 +1,2 @@
+import type { OpenCodeConfig } from '../types/opencode-types.js';
+export declare const configureAgents: (config: OpenCodeConfig) => void;

package/dist/configuration/agents-config.js

@@ -1,55 +1,19 @@
-import { loadMarkdownDir } from "../utils/file-util.js";
-import matter from "gray-matter";
-/**
- * Resolves model aliases to the configured small_model value.
- * Maps common small/fast model aliases to OpenCode's small_model config.
- *
- * @param {string} modelValue - The model value from agent frontmatter
- * @param {string} smallModel - The small_model from OpenCode config
- * @returns {string|undefined} - Resolved model value or undefined
- */
-const resolveModelAlias = (modelValue, smallModel) => {
-    // Aliases that should map to small_model
-    const SMALL_MODEL_ALIASES = [
-        "haiku", // Claude Code alias
-        "gpt-4o-mini", // OpenAI small model
-        "small", // Generic alias
-        "fast", // Generic alias
-    ];
-    // If no model specified or it's 'inherit', return undefined (let OpenCode decide)
-    if (!modelValue || modelValue === "inherit") {
-        return undefined;
-    }
-    // If it's a small model alias and we have a configured small_model, use it
-    if (SMALL_MODEL_ALIASES.includes(modelValue.toLowerCase())) {
-        if (smallModel) {
-            return smallModel;
-        }
-        // If no small_model configured, return undefined (inherit)
-        console.warn(`[owflow] Agent uses '${modelValue}' but no small_model configured in opencode.json - falling back to inherit`);
-        return undefined;
-    }
-    // Otherwise, pass through the original value
-    return modelValue;
-};
-const prepareAgent = ({ data, content }, smallModel) => {
+import { loadMarkdownDir } from '../utils/file-util.js';
+import matter from 'gray-matter';
+const prepareAgent = ({ data, content }) => {
     return {
         prompt: content,
         ...(data.description && { description: data.description }),
-        // Resolve model aliases (haiku, gpt-4o-mini, etc.) to small_model
-        ...(() => {
-            const resolvedModel = resolveModelAlias(data.model, smallModel);
-            return resolvedModel ? { model: resolvedModel } : {};
-        })(),
+        ...(data.model && { model: data.model }),
         ...(data.mode && { mode: data.mode }),
         // Add skills array if present
         ...(data.skills && Array.isArray(data.skills) && { skills: data.skills }),
-        ...(data.hidden === "true" && { hidden: true }),
+        ...(data.hidden === 'true' && { hidden: true }),
     };
 };
-export const configureAgents = (config, smallModel) => {
+export const configureAgents = (config) => {
     config.agent = config.agent || {};
-    for (const markdown of loadMarkdownDir("agents")) {
+    for (const markdown of loadMarkdownDir('agents')) {
         const name = markdown.data.name;
         if (!name)
             continue;
@@ -57,7 +21,7 @@ export const configureAgents = (config, smallModel) => {
         if (config.agent[name])
             continue;
         try {
-            config.agent[name] = prepareAgent(markdown, smallModel);
+            config.agent[name] = prepareAgent(markdown);
         }
         catch (error) {
             console.warn(`[owflow] Failed to register agent '${name}': ${error.message}`);

package/dist/configuration/commands-config.d.ts

@@ -0,0 +1,23 @@
+import type { OpenCodeConfig } from '../types/opencode-types.js';
+interface SkillFrontmatter extends Record<string, any> {
+    name: string;
+    description: string;
+    'user-invocable': boolean;
+}
+/**
+ * Renders the command body for one skill from its frontmatter.
+ * Pure: one frontmatter object in, one string out.
+ */
+export declare const renderCommandTemplate: (data: SkillFrontmatter) => string;
+/**
+ * Reads the frontmatter of every `skills/<slug>/SKILL.md`, one level deep.
+ * I/O and parsing only — the invocable gate and the key contract live in the
+ * registration loop. Failures are never swallowed: our own source data must not
+ * register silently incomplete.
+ */
+export declare const readSkillFrontmatter: () => readonly {
+    slug: string;
+    data: SkillFrontmatter;
+}[];
+export declare const configureCommands: (config: OpenCodeConfig) => void;
+export {};