@crafts69guy/orchestra 0.0.0-stage → 0.3.0

package/skills/dispatch/references/claude.md

@@ -0,0 +1,9 @@
+# Dispatch on Claude Code
+
+- Agent names carry the plugin prefix: `orch:implementer`, `orch:scoper`,
+  `orch:reviewer`, `orch:shipper`. The bare name is not found.
+- Parallel spawn: several Agent tool calls in one assistant message.
+- Do not set `isolation: "worktree"`; the worktree comes from `orch wt new`.
+- Resume an agent with SendMessage to its id or name; it keeps its context.
+- Plugin hooks see `agent_type` as `orch:<role>` and enforce: implementers
+  cannot commit or push; only the shipper pushes or opens PRs.

package/skills/dispatch/references/codex.md

@@ -0,0 +1,12 @@
+# Dispatch on Codex
+
+- Agent names are bare: `implementer`, `scoper`, `reviewer`, `shipper`. They
+  are loaded from the plugin's `codex/agents/*.toml` by the `orch codex`
+  launcher (`-c agents.<name>.config_file=…`). An unknown name silently falls
+  back to the default agent, so confirm the role in its first reply.
+- Spawn each task with `spawn_agent` (`agent_type`, no forked turns), all
+  before waiting, then `wait_agent` on every id.
+- The sandbox must allow writing `<repo>/.git` (`--add-dir <repo>/.git`) or
+  `orch wt new` and commits fail. `orch codex` adds it.
+- Hooks only run when the user trusted them, so restate "do not commit or
+  push" in every brief.

package/skills/plan/SKILL.md

@@ -0,0 +1,56 @@
+---
+name: plan
+description: "orch workflow: write .scratch/<feature>/plan.md, a task list with file ownership and dependencies that the dispatch skill can run in parallel waves. Use when work has 2+ separable parts."
+---
+
+# Plan
+
+Write `.scratch/<feature>/plan.md` in the repo root. Keep `.scratch/` out of git
+(`.git/info/exclude`) unless the repo already tracks it.
+
+## Before writing
+
+1. Read the scoper brief if there is one; do not rescope.
+2. Decide every cross-cutting choice now (interfaces, names, libraries, error
+   handling). Workers run in parallel and cannot ask each other.
+
+## Format
+
+````markdown
+# <feature>
+
+Base branch: <F>   # the branch the tasks merge into
+
+## Decisions
+
+- <decision that every task must follow>
+
+## Tasks
+
+```yaml
+- id: T1
+  goal: <one sentence, observable outcome>
+  files: [<paths this task owns>]
+  depends_on: []
+  validate: <command that proves this task works>
+  decisions: [<task-specific choices>]
+```
+````
+
+## Rules
+
+- `files` is ownership. Two tasks with no dependency path between them must not
+  share a file. If they must, add a `depends_on` edge or merge the tasks.
+- Shared files that everyone touches (lockfiles, barrel exports, registries) go
+  to one task that the others depend on.
+- Each task is 1 implementer-sized unit: one edit-and-test loop, not a project.
+- `validate` runs inside the task's own worktree and must not need other
+  unmerged tasks.
+- Don't split one feature into many tiny tasks. Separate features stay separate
+  tasks, even when each one is small.
+
+## After writing
+
+Show the user the task table (id, goal, depends_on) in a few lines. If 2+ tasks
+are independent, continue with the `dispatch` skill; otherwise run implementers
+one at a time.