owflow 0.3.0 → 0.4.3

package/dist/commands/dev-plan.md

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

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

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

@@ -1,33 +0,0 @@
----
-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,36 +0,0 @@
----
-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]
----
-
-CRITICAL INSTRUCTION: You MUST invoke the owflow:development skill immediately as your FIRST action.
-
-Use the Skill tool with these exact parameters:
-name: "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 this workflow by using /owflow:development.
-Invoke the skill now and let it orchestrate the complete workflow.
-
----
-
-## About This Workflow
-
-Development workflow **dispatcher** (assisted mode). 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
-
-Run `/owflow:goal-development` instead for autonomous mode (all subskills in one session with gates).
-
-See `skills/development/SKILL.md` for the routing table and `skills/dev-*/SKILL.md` for phase documentation.

package/dist/commands/diagrams-mermaid.md

@@ -1,36 +0,0 @@
----
-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]
----
-
-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"
-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:diagrams-mermaid.
-Invoke the skill now and let it orchestrate the complete workflow.
-
----
-
-## About This Skill
-
-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.
-
-The skill handles:
-
-- Diagram type selection based on description
-- Mermaid syntax generation with proper formatting
-- Best practices and anti-patterns enforcement
-- Output in markdown format with mermaid code fences
-
-See `skills/diagrams-mermaid/SKILL.md` for complete documentation.

package/dist/commands/flow-init.md

@@ -1,36 +0,0 @@
----
-name: owflow:flow-init
-description: Initialize AI SDLC framework with intelligent project analysis and documentation generation
-argument-hint: [--standards-from=PATH]
----
-
-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"
-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:flow-init.
-Invoke the skill now and let it orchestrate the complete workflow.
-
----
-
-## About This Workflow
-
-Initialize AI SDLC framework with intelligent project analysis and documentation generation
-
-The skill handles:
-
-- Task directory creation and state management
-- Phase execution with interactive gates
-- Subagent delegation for specialized work
-- Pause/resume capability
-
-See `skills/flow-init/SKILL.md` for complete workflow documentation.

package/dist/commands/goal-development.md

@@ -1,32 +0,0 @@
----
-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/html-renderer.md

@@ -1,36 +0,0 @@
----
-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]
----
-
-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"
-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:html-renderer.
-Invoke the skill now and let it orchestrate the complete workflow.
-
----
-
-## About This Skill
-
-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.
-
-The skill handles:
-
-- Markdown parsing and semantic HTML generation
-- Design system application with warm editorial styling
-- Mermaid diagram rendering via CDN (when present)
-- Self-contained output with inlined CSS
-
-See `skills/html-renderer/SKILL.md` for complete documentation.

package/dist/commands/migration.md

@@ -1,36 +0,0 @@
----
-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]
----
-
-CRITICAL INSTRUCTION: You MUST invoke the owflow:migration skill immediately as your FIRST action.
-
-Use the Skill tool with these exact parameters:
-name: "migration"
-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:migration.
-Invoke the skill now and let it orchestrate the complete workflow.
-
----
-
-## About This Workflow
-
-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.
-
-The skill handles:
-
-- Task directory creation and state management
-- Phase execution with interactive gates
-- Subagent delegation for specialized work
-- Pause/resume capability
-
-See `skills/migration/SKILL.md` for complete workflow documentation.

package/dist/commands/performance.md

@@ -1,36 +0,0 @@
----
-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]
----
-
-CRITICAL INSTRUCTION: You MUST invoke the owflow:performance skill immediately as your FIRST action.
-
-Use the Skill tool with these exact parameters:
-name: "performance"
-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:performance.
-Invoke the skill now and let it orchestrate the complete workflow.
-
----
-
-## About This Workflow
-
-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.
-
-The skill handles:
-
-- Task directory creation and state management
-- Phase execution with interactive gates
-- Subagent delegation for specialized work
-- Pause/resume capability
-
-See `skills/performance/SKILL.md` for complete workflow documentation.

package/dist/commands/research.md

@@ -1,36 +0,0 @@
----
-name: owflow:research
-description: Orchestrates comprehensive research workflows from question definition through findings documentation. Handles technical, requirements, literature, and mixed research types with adaptive methodology, multi-source gathering, pattern synthesis, and evidence-based reporting. Supports standalone research tasks and embedded research phase in other workflows.
-argument-hint: [task description]
----
-
-CRITICAL INSTRUCTION: You MUST invoke the owflow:research skill immediately as your FIRST action.
-
-Use the Skill tool with these exact parameters:
-name: "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 this workflow by using /owflow:research.
-Invoke the skill now and let it orchestrate the complete workflow.
-
----
-
-## About This Workflow
-
-Orchestrates comprehensive research workflows from question definition through findings documentation. Handles technical, requirements, literature, and mixed research types with adaptive methodology, multi-source gathering, pattern synthesis, and evidence-based reporting. Supports standalone research tasks and embedded research phase in other workflows.
-
-The skill handles:
-
-- Task directory creation and state management
-- Phase execution with interactive gates
-- Subagent delegation for specialized work
-- Pause/resume capability
-
-See `skills/research/SKILL.md` for complete workflow documentation.

package/dist/commands/rule-reviewer.md

@@ -1,38 +0,0 @@
----
-name: owflow:rule-reviewer
-description: Score an AI rules file on 5 axes and produce concrete actionable fixes
----
-
-CRITICAL INSTRUCTION: You MUST invoke the owflow:rule-reviewer skill immediately as your FIRST action.
-
-Use the Skill tool with these exact parameters:
-name: "rule-reviewer"
-prompt: "$ARGUMENTS"
-
-DO NOT:
-- Analyze the file 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:rule-reviewer.
-Invoke the skill now and let it orchestrate the complete workflow.
-
----
-
-## About This Workflow
-
-Score an AI rules file (AGENTS.md, CLAUDE.md, .cursor/rules/*.mdc, .windsurfrules,
-.github/copilot-instructions.md, or any rule-for-AI markdown) on 5 axes and return
-concrete actionable fixes. The skill is read-only by default — it produces a scorecard.
-The only edit it may apply is a section reorder, and only with explicit user approval.
-
-## Examples
-
-```
-/owflow:rule-reviewer AGENTS.md
-/owflow:rule-reviewer .cursor/rules/api.mdc
-/owflow:rule-reviewer src/api/AGENTS.md
-```
-
-See `skills/rule-reviewer/SKILL.md` for complete workflow documentation.

package/dist/commands/standards-discover.md

@@ -1,36 +0,0 @@
----
-name: owflow:standards-discover
-description: Discover coding standards from project configuration files, code patterns, documentation, and external sources (PRs, CI/CD)
-argument-hint: [task description]
----
-
-CRITICAL INSTRUCTION: You MUST invoke the owflow:standards-discover skill immediately as your FIRST action.
-
-Use the Skill tool with these exact parameters:
-name: "standards-discover"
-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:standards-discover.
-Invoke the skill now and let it orchestrate the complete workflow.
-
----
-
-## About This Workflow
-
-Discover coding standards from project configuration files, code patterns, documentation, and external sources (PRs, CI/CD)
-
-The skill handles:
-
-- Task directory creation and state management
-- Phase execution with interactive gates
-- Subagent delegation for specialized work
-- Pause/resume capability
-
-See `skills/standards-discover/SKILL.md` for complete workflow documentation.

package/dist/commands/standards-update.md

@@ -1,36 +0,0 @@
----
-name: owflow:standards-update
-description: Update or create project standards from conversation context or explicit description
-argument-hint: "[description of standard/convention] [--from=PATH]"
----
-
-CRITICAL INSTRUCTION: You MUST invoke the owflow:standards-update skill immediately as your FIRST action.
-
-Use the Skill tool with these exact parameters:
-name: "standards-update"
-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:standards-update.
-Invoke the skill now and let it orchestrate the complete workflow.
-
----
-
-## About This Workflow
-
-Update or create project standards from conversation context or explicit description
-
-The skill handles:
-
-- Task directory creation and state management
-- Phase execution with interactive gates
-- Subagent delegation for specialized work
-- Pause/resume capability
-
-See `skills/standards-update/SKILL.md` for complete workflow documentation.

package/dist/constants.js

@@ -1,4 +0,0 @@
-import path from "node:path";
-import { fileURLToPath } from "node:url";
-const __dirname = path.dirname(fileURLToPath(import.meta.url));
-export const PLUGIN_ROOT = __dirname; // Points to dist/ where skills/commands/agents are copied