Add orch and council-review skills

docs/architecture.md

@@ -157,5 +157,5 @@ Do not put these into `orch`:
 The intended skill split mirrors the CLI split.
 
 - `inbox` skill: used when an agent needs to fetch work, claim a thread, send progress, ask blocked questions, reply, or return results through `inbox`
-- `orchestrator` skill: used when the leader needs to create runs, decompose tasks, manage dependencies, dispatch ready work, inspect blocks, answer them, retry failures, or reassign work through `orch`
+- `orch` skill: used when the leader needs to create runs, decompose tasks, manage dependencies, dispatch ready work, inspect blocks, answer them, retry failures, or reassign work through `orch`
 - `council-review` skill: used when the user explicitly wants a structured three-reviewer brainstorm or review with grouped and tallied recommendations

docs/blog-project-example.md

@@ -35,7 +35,7 @@ Dependencies:
 
 ## Who Uses What
 
-- leader uses the `orchestrator` skill and `orch` CLI
+- leader uses the `orch` skill and `orch` CLI
 - workers use the `inbox` skill and `inbox` CLI
 - `orch` is the leader's main interface
 - `inbox` is the worker's main interface

docs/implementation-roadmap.md

@@ -23,8 +23,10 @@ As of now:
 - a human-readable inbox command test-plan set has been authored under `docs/tests/inbox/`
 - a human-readable `orch` test-plan set has now been authored under `docs/tests/orch/`, with a `ROADMAP.md`, shared conventions, workflow scenarios, per-command indexes, and concrete case documents aligned to the current CLI surface, including supplemental coverage for key flag validation, ordering/limit behavior, payload-only answers, cleanup errors, and council report default/error contracts
 - a reusable Codex skill package for `inbox` now exists under `skills/inbox/`, with a formal `SKILL.md`, `agents/openai.yaml`, and a bundled CLI binary asset
+- reusable Codex skill packages for `orch` and `council-review` now exist under `skills/orch/` and `skills/council-review/`, both using bundled copies of the `orch` CLI binary asset
 - an inbox skill forward-test plan directory now exists under `docs/tests/inbox-skill/`, with a shared execution template and multiple scenario cases
 - an execution-roadmap workflow now exists under `docs/roadmaps/active/` and `docs/roadmaps/archive/` for agent-level work traces and completion archives
+- a repo-local `scripts/package_skill_clis.sh` packaging flow now builds bundled skill CLI assets for `inbox`, `orch`, and `council-review`
 - `orch` now implements `run init/show`, `task add`, `dep add`, `ready`, `dispatch`, `reconcile`, `wait`, `blocked`, `answer`, `retry`, `reassign`, `cancel`, `cleanup`, and `status`
 - `orch` can create runs, gate tasks through dependencies, dispatch work through `inbox`, reconcile worker thread state back into task state, answer blocked tasks, retry or reassign work, cancel tasks or runs, clean attempt worktrees, and create per-attempt Git worktrees during strict dispatch
 - `orch dispatch` now supports `--repo-path`, `--workspace-root`, and `--strict-worktree`, auto-enables strict worktree mode for code-like tasks inferred from task metadata, resolves committed base revisions, records workspace metadata on attempts, and writes that metadata into inbox task payloads

docs/inbox-cli.md

@@ -476,7 +476,7 @@ The following block is a draft `SKILL.md` for the `inbox` skill.
 ```markdown
 ---
 name: inbox
-description: Use this skill when an agent needs durable communication through the local inbox CLI. It is for fetching work, claiming a thread, sending progress updates, raising blocked questions, waiting for replies, replying inside a thread, returning results, and watching inbox activity. Do not use it for task decomposition or scheduling decisions; use the orchestrator skill for that.
+description: Use this skill when an agent needs durable communication through the local inbox CLI. It is for fetching work, claiming a thread, sending progress updates, raising blocked questions, waiting for replies, replying inside a thread, returning results, and watching inbox activity. Do not use it for task decomposition or scheduling decisions; use the orch skill for that.
 ---
 
 # Inbox

docs/orch-cli.md

@@ -555,16 +555,16 @@ CREATE INDEX IF NOT EXISTS idx_events_run_event
 
 ## Embedded Skill Draft
 
-The following block is a draft `SKILL.md` for the leader-facing orchestration skill.
+The following block is a draft `SKILL.md` for the leader-facing `orch` skill.
 
 ````markdown
 ```markdown
 ---
-name: orchestrator
+name: orch
 description: Use this skill when the leader needs to plan and schedule work through the orch CLI. It is for creating runs, adding tasks and dependencies, finding ready work, dispatching tasks to workers, allocating task worktrees, reconciling inbox state, waiting for worker events, reviewing blocked tasks, answering them, retrying failures, reassigning work, and cleaning up attempt worktrees. Do not use this skill for worker-side claim or progress updates; use inbox for that.
 ---
 
-# Orchestrator
+# Orch
 
 Use this skill when you are the leader and need to control the task graph through the `orch` CLI.
 

docs/roadmaps/archive/orch-council-skills.md

@@ -0,0 +1,74 @@
+# Title
+
+Add Orch And Council Review Skills With Bundled CLI Assets
+
+## Status
+
+- `completed`
+
+## Owner
+
+- Codex main agent
+
+## Started At
+
+- `2026-03-19`
+
+## Goal
+
+- Add project-local skill packages for `orch` and `council-review`.
+- Add a repeatable packaging flow that builds the `orch` CLI binary and installs it into both skills as bundled assets.
+
+## Scope
+
+- Create `skills/orch/` with `SKILL.md`, `agents/openai.yaml`, and bundled `assets/orch`.
+- Create `skills/council-review/` with `SKILL.md`, `agents/openai.yaml`, and bundled `assets/orch`.
+- Add a repo-local packaging script for building and copying the `orch` CLI binary into both skill asset directories.
+- Update implementation progress docs to reflect the new skill packages and packaging flow.
+
+## Checklist
+
+- [x] Review current skill structure, embedded skill drafts, and bundling expectations.
+- [x] Create `orch` skill package files.
+- [x] Create `council-review` skill package files.
+- [x] Add and validate the CLI packaging script.
+- [x] Build bundled `orch` binaries into both skills and smoke-check them.
+- [x] Update roadmap docs and archive this execution roadmap.
+
+## Files
+
+- `skills/orch/SKILL.md`
+- `skills/orch/agents/openai.yaml`
+- `skills/orch/assets/orch`
+- `skills/council-review/SKILL.md`
+- `skills/council-review/agents/openai.yaml`
+- `skills/council-review/assets/orch`
+- `scripts/package_skill_clis.sh`
+- `docs/architecture.md`
+- `docs/blog-project-example.md`
+- `docs/inbox-cli.md`
+- `docs/orch-cli.md`
+- `docs/implementation-roadmap.md`
+- `docs/roadmaps/archive/orch-council-skills.md`
+
+## Decisions
+
+- Use one underlying `orch` binary for both skills, because `council` is an `orch` subcommand rather than a separate executable.
+- Keep each skill self-contained by bundling its own copy of the `orch` binary asset.
+- Keep the packaging script able to refresh the existing `inbox` skill binary as well, so all bundled CLIs can be rebuilt through one entrypoint.
+- Standardize on the actual implemented skill name `orch` rather than the older draft term `orchestrator`.
+
+## Blockers
+
+- none
+
+## Next Step
+
+- none
+
+## Completion Summary
+
+- Added `skills/orch/` and `skills/council-review/`, each with `SKILL.md`, `agents/openai.yaml`, and a bundled `assets/orch` binary.
+- Added `scripts/package_skill_clis.sh` to rebuild bundled skill CLIs for `inbox`, `orch`, and `council-review`.
+- Built and smoke-checked the new `orch` skill assets with `./skills/orch/assets/orch --help` and `./skills/council-review/assets/orch council --help`.
+- Updated implementation and reference docs to use the actual `orch` skill name and to record the new skill packages and packaging flow.