owflow 0.5.0 → 0.7.0

package/dist/skills/standards-discover/references/external-analyzer-prompt.md

@@ -1,75 +1,75 @@
-# External Standards Analyzer — Subagent Prompt Template
-
-Analyze pull requests, CI/CD configurations, and pre-commit hooks to discover enforced standards.
-
-## Task
-
-Mine external sources for standards evidence, return findings as YAML.
-
-## Sources to Analyze
-
-### 1. Pull Requests (via gh CLI)
-
-**First check availability:**
-```bash
-which gh && gh auth status
-```
-
-If gh CLI available:
-- Get last `[pr_count]` merged PRs: `gh pr list --state merged --limit [pr_count] --json number,title`
-- For each PR, check review comments for repeated feedback patterns
-- Look for: "Please use...", "Always...", "Avoid...", "Per our convention...", "Style:", "Nit:"
-- Only report patterns that appear in **3+ different PRs** (significant feedback, not one-off)
-
-If gh CLI unavailable: skip PR analysis, note in output, not an error.
-
-### 2. CI/CD Workflows
-
-- **GitHub Actions**: `.github/workflows/*.yml`
-- **GitLab CI**: `.gitlab-ci.yml`
-- **Other**: `Jenkinsfile`, `.circleci/config.yml`, `.travis.yml`
-
-Extract: lint steps, test requirements, coverage thresholds, build quality gates, pre-deployment checks.
-
-### 3. Pre-commit Hooks
-
-- **Husky**: `.husky/` directory (pre-commit, pre-push scripts)
-- **pre-commit framework**: `.pre-commit-config.yaml`
-- **lint-staged**: `lint-staged` config in `package.json` or `.lintstagedrc`
-
-Extract: mandatory checks, formatting enforcement, commit message validation.
-
-## Confidence Ranges
-
-| Source | Confidence Range | Rationale |
-|--------|-----------------|-----------|
-| CI/CD enforced standards | 85-95% | Enforced by automation — very reliable |
-| Pre-commit hooks | 80-90% | Actively enforced on every commit |
-| PR review patterns (5+ PRs) | 70-80% | Strong team consensus |
-| PR review patterns (3-4 PRs) | 60-70% | Emerging pattern |
-
-## Output Format
-
-Return YAML:
-
-```yaml
-github_available: true  # or false
-findings:
-  - category: "[category/subcategory]"
-    standard_name: "[Short Name]"
-    description: "[What the standard requires]"
-    confidence: [60-95]
-    evidence:
-      - "[source]: [specific evidence]"
-    source: "[pr-reviews|ci-config|pre-commit]"
-    examples: []
-```
-
-## Rules
-
-- Handle gh CLI gracefully — return `github_available: false` and empty PR findings, not error
-- Only report PR patterns appearing in 3+ different PRs
-- For CI/CD: extract specific thresholds and rules, not just "runs tests"
-- Return empty findings list if no external sources available
-- Be specific: "80% coverage required" not "has coverage check"
-- Do NOT write any files to the project directory. Write your YAML results to: `[output_file]` (the orchestrator replaces this placeholder with an actual temp file path when invoking you).
+# External Standards Analyzer — Subagent Prompt Template
+
+Analyze pull requests, CI/CD configurations, and pre-commit hooks to discover enforced standards.
+
+## Task
+
+Mine external sources for standards evidence, return findings as YAML.
+
+## Sources to Analyze
+
+### 1. Pull Requests (via gh CLI)
+
+**First check availability:**
+```bash
+which gh && gh auth status
+```
+
+If gh CLI available:
+- Get last `[pr_count]` merged PRs: `gh pr list --state merged --limit [pr_count] --json number,title`
+- For each PR, check review comments for repeated feedback patterns
+- Look for: "Please use...", "Always...", "Avoid...", "Per our convention...", "Style:", "Nit:"
+- Only report patterns that appear in **3+ different PRs** (significant feedback, not one-off)
+
+If gh CLI unavailable: skip PR analysis, note in output, not an error.
+
+### 2. CI/CD Workflows
+
+- **GitHub Actions**: `.github/workflows/*.yml`
+- **GitLab CI**: `.gitlab-ci.yml`
+- **Other**: `Jenkinsfile`, `.circleci/config.yml`, `.travis.yml`
+
+Extract: lint steps, test requirements, coverage thresholds, build quality gates, pre-deployment checks.
+
+### 3. Pre-commit Hooks
+
+- **Husky**: `.husky/` directory (pre-commit, pre-push scripts)
+- **pre-commit framework**: `.pre-commit-config.yaml`
+- **lint-staged**: `lint-staged` config in `package.json` or `.lintstagedrc`
+
+Extract: mandatory checks, formatting enforcement, commit message validation.
+
+## Confidence Ranges
+
+| Source | Confidence Range | Rationale |
+|--------|-----------------|-----------|
+| CI/CD enforced standards | 85-95% | Enforced by automation — very reliable |
+| Pre-commit hooks | 80-90% | Actively enforced on every commit |
+| PR review patterns (5+ PRs) | 70-80% | Strong team consensus |
+| PR review patterns (3-4 PRs) | 60-70% | Emerging pattern |
+
+## Output Format
+
+Return YAML:
+
+```yaml
+github_available: true  # or false
+findings:
+  - category: "[category/subcategory]"
+    standard_name: "[Short Name]"
+    description: "[What the standard requires]"
+    confidence: [60-95]
+    evidence:
+      - "[source]: [specific evidence]"
+    source: "[pr-reviews|ci-config|pre-commit]"
+    examples: []
+```
+
+## Rules
+
+- Handle gh CLI gracefully — return `github_available: false` and empty PR findings, not error
+- Only report PR patterns appearing in 3+ different PRs
+- For CI/CD: extract specific thresholds and rules, not just "runs tests"
+- Return empty findings list if no external sources available
+- Be specific: "80% coverage required" not "has coverage check"
+- Do NOT write any files to the project directory. Write your YAML results to: `[output_file]` (the orchestrator replaces this placeholder with an actual temp file path when invoking you).

package/dist/skills/standards-update/SKILL.md

@@ -1,207 +1,207 @@
----
-name: owflow:standards-update
-description: Update or create project standards from conversation context or explicit description
-argument-hint: "[description of standard/convention] [--from=PATH]"
-user-invocable: true
----
-
-# Update Project Standards
-
-Update or create standards in `.owflow/docs/standards/` based on conversation context or a provided description. Automatically detects the best-matching category and file. Supports both baseline categories (global, frontend, backend, testing) and custom user-defined categories.
-
-## Usage
-
-```bash
-/owflow:standards-update                                    # Detect from conversation
-/owflow:standards-update "always use React.memo for lists"  # From description
-/owflow:standards-update --from=/path/to/other-project      # Sync from another project
-```
-
----
-
-## Mode: Sync from External Project (`--from=PATH`)
-
-When `--from=PATH` is provided, the skill switches to **sync mode** — importing standards from another project's `.owflow/docs/standards/` into the current project. This bypasses Phases 1-3 and uses a dedicated flow.
-
-### SYNC STEP 1: Validate Source
-
-1. Resolve the path (absolute or relative to cwd)
-2. Check `PATH/.owflow/docs/standards/` exists. If not, inform the user and stop.
-3. Check `.owflow/docs/standards/` exists in the current project. If not, offer to run `/owflow:flow-init` first.
-
-### SYNC STEP 2: Analyze Differences
-
-1. Scan source project's `standards/*/` — list all categories and files
-2. Scan current project's `standards/*/` — list all categories and files
-3. For each source file, compare against the local counterpart:
-   - **Missing locally**: Category or file doesn't exist in the current project
-   - **Differs**: Both exist but content differs (read and compare)
-   - **Identical**: No action needed
-4. Present a summary to the user via question (multi-select):
-   - Group by status: "New standards to add" and "Standards that differ"
-   - Each item shows: `[category]/[file]` with brief description of what it contains
-   - Options: individual files to sync, plus "Select all new" / "Select all different" convenience options
-   - User selects which standards to import
-
-### SYNC STEP 3: Apply Selected Standards
-
-For each selected standard:
-
-- **Missing locally**: Copy the file from source. Create category directory if needed.
-- **Differs**: Show a brief diff summary and use question per file:
-  - "Replace with source version" — overwrite local file
-  - "Merge (append new sections)" — read both files, append `###` sections from source that don't exist locally
-  - "Skip" — leave local file unchanged
-
-### SYNC STEP 4: Update INDEX.md
-
-Invoke `docs-operator` subagent via Task tool (subagent_type: `docs-operator`):
-
-> "Regenerate INDEX.md to include all newly added/updated standards. Verify AGENTS.md integration."
-
-Wait for docs-operator to complete, then immediately proceed to SYNC STEP 5.
-
-### SYNC STEP 5: Exit Gate
-
-Present results and close (Exit Gate contract, [Gate Contract](../orchestrator-framework/references/gate-contract.md)):
-
-```markdown
-## ✅ STANDARDS SYNC COMPLETE
-
-**Added** — [added count]
-**Updated** — [updated count]
-**Skipped** — [skipped count]
-**Total** — [total]
-
-**Artifacts**
-- `.owflow/docs/standards/<category>/<file>.md` [per synced standard]
-- `.owflow/docs/INDEX.md`
-```
-
-Use `question` — "Are these results correct?" with options:
-
-- **Accept** — sync is complete; print next steps below.
-- **Adjust** — re-run selected imports with different merge choices, then re-present the results box.
-- **Discuss** — walk through merged/differing standards in more depth; then re-ask.
-- **Stop here** — end.
-
-Next steps (after Accept): review the imported standards, then commit.
-
----
-
-## Mode: Conversation / Description (default)
-
-When `--from` is NOT provided, the skill uses the standard detect-and-update flow below.
-
----
-
-## PHASE 1: Detect Standard
-
-**Step 1: Gather input**
-
-- **If argument provided**: Use the description as primary input. Also scan last 15-20 messages for additional context, examples, or related conventions.
-- **If no argument**: Scan last 15-20 messages for convention discussions. Look for patterns like "we should always...", "our convention is...", "prefer X over Y", "never use...", code examples showing patterns.
-
-**Step 2: Discover existing categories and files**
-
-Scan `.owflow/docs/standards/*/` to find all existing categories and standard files. This determines what's available — not limited to baseline categories.
-
-**Step 3: Match to category and file**
-
-Based on the topic detected, suggest the best-matching existing category and file. Consider:
-
-- File names and their content (read existing files if topic is close)
-- Whether the convention fits an existing file or needs a new one
-
-**Step 4: Present suggestion**
-
-- **If confident match** → question: "This convention about [topic] fits [category/file]. Update it?" (Yes / Choose different / Cancel)
-- **If ambiguous** → question listing possible categories/files + "Create new category" + "Create new file in [category]"
-- **If nothing detected** (no argument, no conversation context) → ask user to describe the convention they want to document
-
----
-
-## PHASE 2: Determine Action
-
-Check if the target file exists:
-
-- **Exists** → update mode
-- **Doesn't exist** → create mode (if new category, create the directory too)
-
-No user prompt needed — just inform: "Updating existing standard: [name]" or "Creating new standard: [category/name]"
-
----
-
-## PHASE 3: Gather Standard Content
-
-### If updating
-
-1. Read current content
-2. Show summary of existing practices
-3. Ask what to add/change
-4. Extract: new practices, modifications, removals, code examples
-
-### If creating
-
-1. Inform user of target path
-2. Ask for practices, conventions, code examples, do's/don'ts
-3. Optionally show plugin baseline if similar standard exists in docs-manager's bundled docs
-
----
-
-## PHASE 4: Apply via docs-manager
-
-> Each standard uses a `###` heading with 1-10 lines description (excluding code snippets). Multiple standards per topic file. Split large topics into sub-topic files.
-
-**Invoke `docs-operator` subagent** via Task tool (subagent_type: `docs-operator`) with context:
-
-For **updates**:
-
-> "Update documentation file: standards/[category]/[name].md. Current content: [content]. Add/change: [new conventions]. Integrate new practices, maintain markdown formatting, organize logically, preserve existing unless conflicts. Update INDEX.md entry with practice-specific description (enumerate actual practices, not generic category)."
-
-For **creates**:
-
-> "Create documentation file: standards/[category]/[name].md. Category: [category]. Content: [conventions]. Create with proper markdown, organized sections, code examples. Add to INDEX.md with practice-specific description. Verify AGENTS.md integration."
-
-Wait for docs-operator to complete, then immediately proceed to Phase 5.
-
----
-
-## PHASE 5: Validate & Exit Gate
-
-1. Verify standard file exists and has content
-2. Verify INDEX.md references the standard with practice-specific description (not generic)
-3. Verify AGENTS.md integration
-4. Present results (Exit Gate contract, [Gate Contract](../orchestrator-framework/references/gate-contract.md)):
-
-**Results box**:
-
-```markdown
-## ✅ STANDARDS UPDATE COMPLETE
-
-**Action** — [created / updated] `standards/<category>/<name>.md`
-**Practices** — [count added/changed]
-**INDEX/AGENTS** — [integration status]
-
-**Artifacts**
-- `.owflow/docs/standards/<category>/<name>.md`
-- `.owflow/docs/INDEX.md`
-```
-
-**Results-acceptance question** — use `question` — "Are these results correct?" with options:
-
-- **Accept** — standard is good; print next steps below.
-- **Adjust** — revise the standard (wording, more practices, better examples), via docs-operator, then re-present the results box.
-- **Discuss** — walk through what was written and why in more depth; then re-ask.
-- **Stop here** — end.
-
-**Next steps (after Accept)**:
-
-- Review the applied standard file
-- Commit the changes and share with the team
-
----
-
-## Prerequisites
-
-If `.owflow/docs/` doesn't exist, offer to run `/owflow:flow-init` first.
+---
+name: owflow:standards-update
+description: Update or create project standards from conversation context or explicit description
+argument-hint: "[description of standard/convention] [--from=PATH]"
+user-invocable: true
+---
+
+# Update Project Standards
+
+Update or create standards in `.owflow/docs/standards/` based on conversation context or a provided description. Automatically detects the best-matching category and file. Supports both baseline categories (global, frontend, backend, testing) and custom user-defined categories.
+
+## Usage
+
+```bash
+/owflow:standards-update                                    # Detect from conversation
+/owflow:standards-update "always use React.memo for lists"  # From description
+/owflow:standards-update --from=/path/to/other-project      # Sync from another project
+```
+
+---
+
+## Mode: Sync from External Project (`--from=PATH`)
+
+When `--from=PATH` is provided, the skill switches to **sync mode** — importing standards from another project's `.owflow/docs/standards/` into the current project. This bypasses Phases 1-3 and uses a dedicated flow.
+
+### SYNC STEP 1: Validate Source
+
+1. Resolve the path (absolute or relative to cwd)
+2. Check `PATH/.owflow/docs/standards/` exists. If not, inform the user and stop.
+3. Check `.owflow/docs/standards/` exists in the current project. If not, offer to run `/owflow:flow-init` first.
+
+### SYNC STEP 2: Analyze Differences
+
+1. Scan source project's `standards/*/` — list all categories and files
+2. Scan current project's `standards/*/` — list all categories and files
+3. For each source file, compare against the local counterpart:
+   - **Missing locally**: Category or file doesn't exist in the current project
+   - **Differs**: Both exist but content differs (read and compare)
+   - **Identical**: No action needed
+4. Present a summary to the user via question (multi-select):
+   - Group by status: "New standards to add" and "Standards that differ"
+   - Each item shows: `[category]/[file]` with brief description of what it contains
+   - Options: individual files to sync, plus "Select all new" / "Select all different" convenience options
+   - User selects which standards to import
+
+### SYNC STEP 3: Apply Selected Standards
+
+For each selected standard:
+
+- **Missing locally**: Copy the file from source. Create category directory if needed.
+- **Differs**: Show a brief diff summary and use question per file:
+  - "Replace with source version" — overwrite local file
+  - "Merge (append new sections)" — read both files, append `###` sections from source that don't exist locally
+  - "Skip" — leave local file unchanged
+
+### SYNC STEP 4: Update INDEX.md
+
+Invoke `docs-operator` subagent via Task tool (subagent_type: `docs-operator`):
+
+> "Regenerate INDEX.md to include all newly added/updated standards. Verify AGENTS.md integration."
+
+Wait for docs-operator to complete, then immediately proceed to SYNC STEP 5.
+
+### SYNC STEP 5: Exit Gate
+
+Present results and close (Exit Gate contract, [Gate Contract](../orchestrator-framework/references/gate-contract.md)):
+
+```markdown
+## ✅ STANDARDS SYNC COMPLETE
+
+**Added** — [added count]
+**Updated** — [updated count]
+**Skipped** — [skipped count]
+**Total** — [total]
+
+**Artifacts**
+- `.owflow/docs/standards/<category>/<file>.md` [per synced standard]
+- `.owflow/docs/INDEX.md`
+```
+
+Use `question` — "Are these results correct?" with options:
+
+- **Accept** — sync is complete; print next steps below.
+- **Adjust** — re-run selected imports with different merge choices, then re-present the results box.
+- **Discuss** — walk through merged/differing standards in more depth; then re-ask.
+- **Stop here** — end.
+
+Next steps (after Accept): review the imported standards, then commit.
+
+---
+
+## Mode: Conversation / Description (default)
+
+When `--from` is NOT provided, the skill uses the standard detect-and-update flow below.
+
+---
+
+## PHASE 1: Detect Standard
+
+**Step 1: Gather input**
+
+- **If argument provided**: Use the description as primary input. Also scan last 15-20 messages for additional context, examples, or related conventions.
+- **If no argument**: Scan last 15-20 messages for convention discussions. Look for patterns like "we should always...", "our convention is...", "prefer X over Y", "never use...", code examples showing patterns.
+
+**Step 2: Discover existing categories and files**
+
+Scan `.owflow/docs/standards/*/` to find all existing categories and standard files. This determines what's available — not limited to baseline categories.
+
+**Step 3: Match to category and file**
+
+Based on the topic detected, suggest the best-matching existing category and file. Consider:
+
+- File names and their content (read existing files if topic is close)
+- Whether the convention fits an existing file or needs a new one
+
+**Step 4: Present suggestion**
+
+- **If confident match** → question: "This convention about [topic] fits [category/file]. Update it?" (Yes / Choose different / Cancel)
+- **If ambiguous** → question listing possible categories/files + "Create new category" + "Create new file in [category]"
+- **If nothing detected** (no argument, no conversation context) → ask user to describe the convention they want to document
+
+---
+
+## PHASE 2: Determine Action
+
+Check if the target file exists:
+
+- **Exists** → update mode
+- **Doesn't exist** → create mode (if new category, create the directory too)
+
+No user prompt needed — just inform: "Updating existing standard: [name]" or "Creating new standard: [category/name]"
+
+---
+
+## PHASE 3: Gather Standard Content
+
+### If updating
+
+1. Read current content
+2. Show summary of existing practices
+3. Ask what to add/change
+4. Extract: new practices, modifications, removals, code examples
+
+### If creating
+
+1. Inform user of target path
+2. Ask for practices, conventions, code examples, do's/don'ts
+3. Optionally show plugin baseline if similar standard exists in docs-manager's bundled docs
+
+---
+
+## PHASE 4: Apply via docs-manager
+
+> Each standard uses a `###` heading with 1-10 lines description (excluding code snippets). Multiple standards per topic file. Split large topics into sub-topic files.
+
+**Invoke `docs-operator` subagent** via Task tool (subagent_type: `docs-operator`) with context:
+
+For **updates**:
+
+> "Update documentation file: standards/[category]/[name].md. Current content: [content]. Add/change: [new conventions]. Integrate new practices, maintain markdown formatting, organize logically, preserve existing unless conflicts. Update INDEX.md entry with practice-specific description (enumerate actual practices, not generic category)."
+
+For **creates**:
+
+> "Create documentation file: standards/[category]/[name].md. Category: [category]. Content: [conventions]. Create with proper markdown, organized sections, code examples. Add to INDEX.md with practice-specific description. Verify AGENTS.md integration."
+
+Wait for docs-operator to complete, then immediately proceed to Phase 5.
+
+---
+
+## PHASE 5: Validate & Exit Gate
+
+1. Verify standard file exists and has content
+2. Verify INDEX.md references the standard with practice-specific description (not generic)
+3. Verify AGENTS.md integration
+4. Present results (Exit Gate contract, [Gate Contract](../orchestrator-framework/references/gate-contract.md)):
+
+**Results box**:
+
+```markdown
+## ✅ STANDARDS UPDATE COMPLETE
+
+**Action** — [created / updated] `standards/<category>/<name>.md`
+**Practices** — [count added/changed]
+**INDEX/AGENTS** — [integration status]
+
+**Artifacts**
+- `.owflow/docs/standards/<category>/<name>.md`
+- `.owflow/docs/INDEX.md`
+```
+
+**Results-acceptance question** — use `question` — "Are these results correct?" with options:
+
+- **Accept** — standard is good; print next steps below.
+- **Adjust** — revise the standard (wording, more practices, better examples), via docs-operator, then re-present the results box.
+- **Discuss** — walk through what was written and why in more depth; then re-ask.
+- **Stop here** — end.
+
+**Next steps (after Accept)**:
+
+- Review the applied standard file
+- Commit the changes and share with the team
+
+---
+
+## Prerequisites
+
+If `.owflow/docs/` doesn't exist, offer to run `/owflow:flow-init` first.

package/dist/templates/orchestrator-state-base.yml

@@ -1,17 +1,17 @@
-orchestrator:
-  started_phase: null
-  completed_phases: []
-  failed_phases: []
-  auto_fix_attempts: {}
-  options: {}
-  created: "YYYY-MM-DDTHH:MM:SSZ"
-  updated: "YYYY-MM-DDTHH:MM:SSZ"
-  task_path: null
-  task_ids: {}
-
-task:
-  title: null
-  description: null
-  status: pending
-  tags: []
-  priority: null
+orchestrator:
+  started_phase: null
+  completed_phases: []
+  failed_phases: []
+  auto_fix_attempts: {}
+  options: {}
+  created: "YYYY-MM-DDTHH:MM:SSZ"
+  updated: "YYYY-MM-DDTHH:MM:SSZ"
+  task_path: null
+  task_ids: {}
+
+task:
+  title: null
+  description: null
+  status: pending
+  tags: []
+  priority: null