compound-workflow 1.7.3 → 1.9.0

package/src/.agents/skills/xstate-actor-orchestration/references/testing-strategy.md

@@ -1,35 +0,0 @@
-# Testing Strategy
-
-## Test layers
-
-1. Unit tests:
-- Actions, guards, pure transition logic.
-
-2. Actor tests:
-- Start actors, send events, assert snapshots and outputs.
-
-3. Integration tests:
-- Orchestrator plus real or fake worker actors.
-
-4. Model/path tests:
-- Generate critical paths from machine model.
-
-## Priority scenarios
-
-- Happy path completion.
-- Cancellation at each in-flight stage.
-- Retry exhaustion and terminal failure.
-- Recovery from persisted snapshot.
-- Out-of-order or duplicate events.
-
-## Assertions to include
-
-- Current state value.
-- Context data invariants.
-- Emitted events to collaborators.
-- Invoked actor lifecycle (started/stopped as expected).
-
-## Simulated time
-
-Use simulated clocks for deterministic timeout testing.
-Avoid wall-clock sleeps in tests.

package/src/.agents/skills/xstate-actor-orchestration/scripts/create-statechart-artifact.sh

@@ -1,71 +0,0 @@
-#!/usr/bin/env bash
-
-set -euo pipefail
-
-skill_dir="${1:-.}"
-machine_name_raw="${2:-}"
-timestamp="${3:-$(date '+%Y%m%d-%H%M%S')}"
-phase="${4:-DRAFT}"
-
-if [[ -z "$machine_name_raw" ]]; then
-  echo "Usage: $0 <skill-dir> <machine-name> [timestamp] [phase]" >&2
-  exit 1
-fi
-
-machine_name="$(echo "$machine_name_raw" | tr '[:upper:]' '[:lower:]' | sed -E 's/[^a-z0-9]+/-/g; s/^-+//; s/-+$//')"
-if [[ -z "$machine_name" ]]; then
-  echo "ERROR: machine-name must contain at least one alphanumeric character" >&2
-  exit 1
-fi
-
-artifact_dir="$skill_dir/assets/statecharts"
-mkdir -p "$artifact_dir"
-
-artifact_base="${machine_name}-${timestamp}"
-diagram_file="$artifact_dir/${artifact_base}.mmd"
-signoff_file="$artifact_dir/${artifact_base}.signoff.md"
-
-if [[ -e "$diagram_file" || -e "$signoff_file" ]]; then
-  echo "ERROR: Artifact already exists for ${artifact_base}" >&2
-  exit 1
-fi
-
-cat > "$diagram_file" <<EOF
-stateDiagram-v2
-  [*] --> "TODO: initial"
-  "TODO: initial" --> "TODO: next": "TODO: event"
-  "TODO: next" --> [*]
-EOF
-
-cat > "$signoff_file" <<EOF
-# Statechart Sign-Off
-
-- Machine: ${machine_name_raw}
-- Artifact: ${artifact_base}
-- Diagram: ./$(basename "$diagram_file")
-- Source machine file: TODO:
-
-## Change summary
-
-TODO:
-
-## Review discussion points
-
-1. Scope and event visibility:
-2. Parallel vs sequential structure:
-3. Wildcard routing behavior:
-4. Retry/cancel/recovery paths:
-5. Tags used by UI selectors:
-6. Emitted imperative events:
-
-## Sign-off
-
-- Status: ${phase}
-- Reviewer:
-- Date:
-- Notes:
-EOF
-
-echo "Created:"
-echo "- $diagram_file"
-echo "- $signoff_file"

package/src/.agents/skills/xstate-actor-orchestration/scripts/validate-skill.sh

@@ -1,138 +0,0 @@
-#!/usr/bin/env bash
-
-set -euo pipefail
-
-skill_dir="${1:-.}"
-skill_md="$skill_dir/SKILL.md"
-openai_yaml="$skill_dir/agents/openai.yaml"
-statecharts_dir="$skill_dir/assets/statecharts"
-statechart_script="$skill_dir/scripts/create-statechart-artifact.sh"
-
-fail=0
-
-ok() {
-  echo "OK: $1"
-}
-
-err() {
-  echo "ERROR: $1" >&2
-  fail=1
-}
-
-if [[ ! -f "$skill_md" ]]; then
-  err "Missing SKILL.md at $skill_md"
-fi
-
-if [[ ! -f "$openai_yaml" ]]; then
-  err "Missing agents/openai.yaml at $openai_yaml"
-fi
-
-if [[ ! -d "$statecharts_dir" ]]; then
-  err "Missing statechart asset directory at $statecharts_dir"
-else
-  ok "Statechart asset directory exists"
-fi
-
-if [[ ! -f "$statechart_script" ]]; then
-  err "Missing statechart artifact script at $statechart_script"
-elif [[ ! -x "$statechart_script" ]]; then
-  err "Statechart artifact script is not executable: $statechart_script"
-else
-  ok "Statechart artifact script exists and is executable"
-fi
-
-if [[ -f "$skill_md" ]]; then
-  first_line="$(head -n 1 "$skill_md" || true)"
-  if [[ "$first_line" != "---" ]]; then
-    err "SKILL.md must start with frontmatter delimiter '---'"
-  fi
-
-  fm_end_line="$(awk 'NR > 1 && $0 == "---" { print NR; exit }' "$skill_md")"
-  if [[ -z "${fm_end_line:-}" ]]; then
-    err "SKILL.md is missing closing frontmatter delimiter '---'"
-  else
-    ok "Frontmatter delimiters found"
-
-    frontmatter="$(sed -n "2,$((fm_end_line - 1))p" "$skill_md")"
-
-    if ! grep -qE '^name:[[:space:]]*[^[:space:]].*$' <<<"$frontmatter"; then
-      err "Frontmatter must include non-empty 'name'"
-    fi
-
-    if ! grep -qE '^description:[[:space:]]*[^[:space:]].*$' <<<"$frontmatter"; then
-      err "Frontmatter must include non-empty 'description'"
-    fi
-
-    extra_keys="$(sed '/^[[:space:]]*$/d' <<<"$frontmatter" | sed 's/:.*$//' | grep -Ev '^(name|description)$' || true)"
-    if [[ -n "$extra_keys" ]]; then
-      err "Frontmatter contains unsupported key(s): $(tr '\n' ',' <<<"$extra_keys" | sed 's/,$//')"
-    else
-      ok "Frontmatter keys are limited to name and description"
-    fi
-
-    skill_name="$(sed -n 's/^name:[[:space:]]*//p' <<<"$frontmatter" | head -n 1)"
-    if [[ ! "$skill_name" =~ ^[a-z0-9-]{1,64}$ ]]; then
-      err "name must match ^[a-z0-9-]{1,64}$ (found '$skill_name')"
-    else
-      ok "Skill name format is valid"
-    fi
-
-    skill_dir_basename="$(basename "$skill_dir")"
-    if [[ "$skill_name" != "$skill_dir_basename" ]]; then
-      err "Folder name '$skill_dir_basename' must match frontmatter name '$skill_name'"
-    else
-      ok "Folder name matches frontmatter name"
-    fi
-  fi
-fi
-
-if [[ -f "$openai_yaml" ]]; then
-  if ! grep -qE '^[[:space:]]*default_prompt:[[:space:]]*".*"$' "$openai_yaml"; then
-    err "agents/openai.yaml must include quoted default_prompt"
-  else
-    ok "default_prompt exists"
-  fi
-
-  if [[ -n "${skill_name:-}" ]] && ! grep -q '\$'"${skill_name}" "$openai_yaml"; then
-    err "default_prompt must mention \$${skill_name}"
-  elif [[ -n "${skill_name:-}" ]]; then
-    ok "default_prompt mentions $skill_name"
-  fi
-fi
-
-if command -v rg >/dev/null 2>&1; then
-  set +e
-  rg -n '\[TODO|TODO:' \
-    "$skill_dir/SKILL.md" \
-    "$skill_dir/agents/openai.yaml" \
-    "$skill_dir/references" >/dev/null
-  todo_rc=$?
-  set -e
-  if [[ "$todo_rc" -eq 0 ]]; then
-    err "Unresolved TODO placeholders found in skill files"
-  elif [[ "$todo_rc" -eq 1 ]]; then
-    ok "No TODO markers found"
-  else
-    err "Failed to run TODO marker check with ripgrep"
-  fi
-
-  if [[ -f "$skill_md" ]]; then
-    while IFS= read -r rel_path; do
-      clean_path="${rel_path#references/}"
-      full_path="$skill_dir/references/$clean_path"
-      if [[ ! -f "$full_path" ]]; then
-        err "Missing reference file linked from SKILL.md: $rel_path"
-      fi
-    done < <(rg -o '\]\((references/[^)]+)\)' "$skill_md" | sed -E 's/.*\((references\/[^)]+)\).*/\1/' | sort -u)
-    ok "Reference links resolved"
-  fi
-else
-  err "ripgrep (rg) is required for TODO and reference-link checks"
-fi
-
-if [[ "$fail" -ne 0 ]]; then
-  echo "Validation failed." >&2
-  exit 1
-fi
-
-echo "Validation passed."

package/src/generated/opencode.managed.json

@@ -1,115 +0,0 @@
-{
-  "$schema": "https://opencode.ai/config.json",
-  "skillsPath": "node_modules/compound-workflow/src/.agents/skills",
-  "commandRoot": "node_modules/compound-workflow/src/.agents/commands",
-  "agentRoot": "node_modules/compound-workflow/src/.agents/agents",
-  "commands": [
-    {
-      "id": "assess",
-      "description": "Review recent metrics entries to identify failures/trends and propose concrete improvements to commands/skills/agents",
-      "rel": "assess.md"
-    },
-    {
-      "id": "install",
-      "description": "Install compound-workflow in this project (native mode): writes opencode.json, merges AGENTS.md, and creates docs/todo dirs.",
-      "rel": "install.md"
-    },
-    {
-      "id": "metrics",
-      "description": "Log a metrics entry for the current workflow run so process performance can be reviewed daily/weekly/monthly",
-      "rel": "metrics.md"
-    },
-    {
-      "id": "test-browser",
-      "description": "Run browser tests on pages affected by current PR or branch",
-      "rel": "test-browser.md"
-    },
-    {
-      "id": "workflow:brainstorm",
-      "description": "Explore requirements and approaches through collaborative dialogue before planning implementation",
-      "rel": "workflow-brainstorm.md"
-    },
-    {
-      "id": "workflow:compound",
-      "description": "Document a durable learning (solved problem or implementation insight) into docs/solutions/ to compound institutional knowledge",
-      "rel": "workflow-compound.md"
-    },
-    {
-      "id": "workflow:plan",
-      "description": "Transform feature descriptions into well-structured project plans using an explicit fidelity and confidence model",
-      "rel": "workflow-plan.md"
-    },
-    {
-      "id": "workflow:review",
-      "description": "Review a PR/branch/diff with structured findings. Does not implement fixes unless explicitly requested.",
-      "rel": "workflow-review.md"
-    },
-    {
-      "id": "workflow:tech-review",
-      "description": "Run technical review on a plan (technical correctness before build). Optional plan path or latest in docs/plans/.",
-      "rel": "workflow-tech-review.md"
-    },
-    {
-      "id": "workflow:triage",
-      "description": "Manual triage command to prioritize todo files into an executable ready queue (priority, dependencies, recommended action)",
-      "rel": "workflow-triage.md"
-    },
-    {
-      "id": "workflow:work",
-      "description": "Execute a plan file systematically (implementation + verification) without auto-shipping",
-      "rel": "workflow-work.md"
-    }
-  ],
-  "agents": [
-    {
-      "id": "agent-native-reviewer",
-      "description": "Reviews code to ensure agent-native parity — any action a user can take, an agent can also take. Use after adding UI features, agent tools, or system prompts.",
-      "rel": "review/agent-native-reviewer.md"
-    },
-    {
-      "id": "best-practices-researcher",
-      "description": "Researches and synthesizes external best practices, documentation, and examples for any technology or framework. Use when you need industry standards, community conventions, or implementation guidance.",
-      "rel": "research/best-practices-researcher.md"
-    },
-    {
-      "id": "bug-reproduction-validator",
-      "description": "Systematically reproduces and validates bug reports to confirm whether reported behavior is an actual bug. Use when you receive a bug report or issue that needs verification.",
-      "rel": "workflow/bug-reproduction-validator.md"
-    },
-    {
-      "id": "framework-docs-researcher",
-      "description": "Gathers authoritative documentation for frameworks, libraries, and dependencies. Use when you need official docs, version constraints, breaking changes, or implementation patterns.",
-      "rel": "research/framework-docs-researcher.md"
-    },
-    {
-      "id": "git-history-analyzer",
-      "description": "Performs archaeological analysis of git history to trace code evolution, identify contributors, and understand why code patterns exist. Use when you need historical context for code changes.",
-      "rel": "research/git-history-analyzer.md"
-    },
-    {
-      "id": "learnings-researcher",
-      "description": "Searches docs/solutions/ for relevant past solutions by frontmatter metadata. Use before implementing features or fixing problems to surface institutional knowledge and prevent repeated mistakes.",
-      "rel": "research/learnings-researcher.md"
-    },
-    {
-      "id": "lint",
-      "description": "Run repo-configured linting and code quality checks. Use when you need to lint/format or verify code quality.",
-      "rel": "workflow/lint.md"
-    },
-    {
-      "id": "planning-technical-reviewer",
-      "description": "Independent technical reviewer for brainstorm/plan outputs before execution.",
-      "rel": "review/planning-technical-reviewer.md"
-    },
-    {
-      "id": "repo-research-analyst",
-      "description": "Conducts thorough research on repository structure, documentation, conventions, and implementation patterns. Use when onboarding to a new codebase or understanding project conventions.",
-      "rel": "research/repo-research-analyst.md"
-    },
-    {
-      "id": "spec-flow-analyzer",
-      "description": "Analyzes specifications and feature descriptions for user flow completeness and gap identification. Use when a spec, plan, or feature description needs flow analysis, edge case discovery, or requirements validation.",
-      "rel": "workflow/spec-flow-analyzer.md"
-    }
-  ]
-}