Add orch and council-review skills

skills/council-review/SKILL.md

@@ -0,0 +1,56 @@
+---
+name: council-review
+description: Structured three-reviewer brainstorming and review through a bundled orch CLI. Use when an agent needs a high-level council workflow on top of orch to launch reviewer roles, wait for their outputs, tally grouped recommendations, and report consensus, majority, and minority findings.
+---
+
+# Council Review
+
+Use the bundled `./assets/orch` CLI to run the high-level `orch council ...` workflow.
+
+## Quick Start
+
+- Invoke `./assets/orch` relative to this skill directory.
+- Pass `--db` explicitly for every command.
+- Prefer `--json` whenever another agent or script will read the output.
+- Treat this skill as a high-level workflow on top of `orch`, not as a separate infrastructure layer.
+
+## Reviewer Roles
+
+- `architecture-reviewer`
+- `implementation-reviewer`
+- `risk-reviewer`
+
+## Rules
+
+- Use this skill when the user explicitly wants a multi-reviewer brainstorm or review.
+- Treat the workflow as analysis-first unless the user explicitly asks for patch proposals or code-change recommendations.
+- Use `orch council` as the execution surface for start, wait, tally, and report.
+- Default to the fixed reviewer roles architecture, implementation, and risk.
+- Collect all three reviewer outputs before tallying.
+- Use `normal` similarity unless the user asks for stricter grouping.
+- If the user asks for unanimous-only output, rely on `--only-unanimous` and expect default report output to show only `consensus`.
+- Otherwise present `consensus` first, then `majority`, and include `minority` when requested.
+- Support text, repository, mixed, or task-target context when available.
+
+## Typical Commands
+
+```bash
+./assets/orch --db ./coord.db --json council start --run council_blog_001 --target-file brief.md --target-type mixed --mode brainstorm --output both
+./assets/orch --db ./coord.db --json council wait --run council_blog_001 --timeout-seconds 900
+./assets/orch --db ./coord.db --json council tally --run council_blog_001 --similarity normal
+./assets/orch --db ./coord.db --json council report --run council_blog_001 --show consensus,majority
+```
+
+## Command Map
+
+- `council start`: create the council run and dispatch the three reviewer tasks
+- `council wait`: block until all reviewers finish or timeout is reached
+- `council tally`: parse reviewer outputs, group similar findings, and count support
+- `council report`: render the final grouped council output and persist report metadata
+
+## Notes
+
+- This skill depends on the underlying `orch` orchestration model and persists its run state, grouped findings, and report metadata there.
+- Use `council wait` before `council tally`, and `council tally` before `council report`.
+- `council report` defaults to `consensus,majority`, except unanimous-only runs where the default is `consensus`.
+- If the bundled binary cannot execute on the current host, stop and report the compatibility issue instead of guessing a replacement path or workflow.

skills/council-review/agents/openai.yaml

@@ -0,0 +1,7 @@
+interface:
+  display_name: "Council Review CLI"
+  short_description: "Three-reviewer workflow on top of orch"
+  default_prompt: "Use $council-review to run the high-level orch council workflow through the bundled orch CLI and a SQLite orchestration database."
+
+policy:
+  allow_implicit_invocation: true

skills/orch/SKILL.md

@@ -0,0 +1,66 @@
+---
+name: orch
+description: Leader-side orchestration through a bundled orch CLI. Use when an agent needs to create runs, add tasks and dependencies, find ready work, dispatch tasks, reconcile worker progress, wait for run events, inspect blocked tasks, answer them, retry or reassign failures, or clean up attempt worktrees through a SQLite-backed orchestration database instead of hand-driving inbox threads.
+---
+
+# Orch
+
+Use the bundled `./assets/orch` CLI to control leader-side orchestration through `orch`.
+
+## Quick Start
+
+- Invoke `./assets/orch` relative to this skill directory.
+- Pass `--db` explicitly for every command.
+- Prefer `--json` whenever another agent or script will read the output.
+- Use this skill for leader-side scheduling and control-plane actions, not worker-side lease or progress updates.
+
+## Rules
+
+- Prefer `orch` over hand-written `inbox send` for normal leader operations.
+- Reconcile inbox state before making new dispatch decisions.
+- If nothing is actionable, use `wait` instead of manual sleep loops.
+- For code tasks, dispatch from a committed base and allocate a fresh worktree per attempt.
+- Use `blocked` and `answer` to resolve worker questions through the active attempt thread.
+- Use `retry` or `reassign` only after checking the latest task and attempt state.
+- Use `inbox` directly only for inspection or manual repair, not routine scheduling.
+
+## Typical Commands
+
+```bash
+./assets/orch --db ./coord.db --json run init --run blog_mvp_001 --goal "Build blog MVP" --summary "Public blog plus admin CRUD"
+./assets/orch --db ./coord.db --json task add --run blog_mvp_001 --task T1 --title "Project skeleton" --summary "Initialize app structure and database wiring" --default-to foundation-worker
+./assets/orch --db ./coord.db --json dep add --run blog_mvp_001 --task T2 --depends-on T1
+./assets/orch --db ./coord.db --json ready --run blog_mvp_001
+./assets/orch --db ./coord.db --json dispatch --run blog_mvp_001 --task T1 --to foundation-worker --base-ref main --workspace-root .orch/worktrees --strict-worktree --body-file tasks/t1.md
+./assets/orch --db ./coord.db --json reconcile --run blog_mvp_001
+./assets/orch --db ./coord.db --json wait --run blog_mvp_001 --for task_blocked,task_done,task_failed --after-event 0 --timeout-seconds 900
+./assets/orch --db ./coord.db --json blocked --run blog_mvp_001
+./assets/orch --db ./coord.db --json answer --run blog_mvp_001 --task T2 --body "MVP supports draft and published only."
+./assets/orch --db ./coord.db --json retry --run blog_mvp_001 --task T7a --to backend-worker --body "Retry after fixing the contract mismatch."
+./assets/orch --db ./coord.db --json cleanup --run blog_mvp_001 --all-completed
+```
+
+## Command Map
+
+- `run init`: create a new orchestration run
+- `run show`: inspect run metadata and aggregate task counts
+- `task add`: add a task to a run
+- `dep add`: record a task dependency
+- `ready`: list tasks that are ready for dispatch
+- `dispatch`: create an attempt and inbox thread for a ready task
+- `reconcile`: fold worker thread state back into orch task state
+- `wait`: block until matching run events arrive
+- `blocked`: list blocked tasks and their latest questions
+- `answer`: send a leader answer into the active blocked attempt
+- `retry`: create a fresh attempt for a failed task
+- `reassign`: cancel the current attempt and dispatch a new one to another worker
+- `cancel`: cancel a task or entire run
+- `cleanup`: remove completed or abandoned worktrees
+- `status`: inspect the full run summary and task list
+
+## Notes
+
+- `dispatch` supports `--repo-path`, `--workspace-root`, `--strict-worktree`, and `--base-ref` for worktree-backed code execution.
+- `answer` supports `--payload-json` for structured decisions, not just freeform text.
+- `status` is the full run view; `run show` is the lighter aggregate view.
+- If the bundled binary cannot execute on the current host, stop and report the compatibility issue instead of guessing a replacement path or workflow.

skills/orch/agents/openai.yaml

@@ -0,0 +1,7 @@
+interface:
+  display_name: "Orch CLI"
+  short_description: "Leader-side orchestration CLI"
+  default_prompt: "Use $orch to manage orchestration runs through the bundled orch CLI and a SQLite orchestration database."
+
+policy:
+  allow_implicit_invocation: true