pantheon-opencode 1.6.0-beta.7 → 1.6.0-beta.8

package/src/skills/agent-coordination/SKILL.md

@@ -1,25 +1,95 @@
 ---
 name: agent-coordination
-description: "Coordinate two or more specialists for substantial multi-phase work. Skip for questions, bounded fixes, and one-agent tasks."
+description: "Multi-agent orchestration with model routing, category delegation, and sprint management. Use for coordinating Pantheon agents."
 context: fork
 globs: []
 alwaysApply: false
 ---
 
-# Agent coordination
+# Agent Coordination
 
-Load only when the work genuinely needs multiple specialists or dependent phases. For the default routing, retry, and safety rules, follow Zeus and `pantheon://routing`.
+Master guide to orchestrating the multi-agent system. Includes category routing, model selection, and sprint management for rapid, TDD-driven feature development.
 
-## Lean coordination
+---
+
+## Agent Hierarchy
+
+See `AGENTS.md` for the full agent table.
+
+---
+
+## Category Routing
+
+Route tasks to optimized agents based on category instead of specifying agents manually:
+
+| Category | Agent | Use For |
+|----------|-------|---------|
+| **Deep** | Athena, Hephaestus | Complex planning, AI pipelines |
+| **Quick** | Talos, Apollo | Fast fixes, codebase search |
+| **Ultrabrain** | Zeus | Multi-agent orchestration, model routing |
+
+---
+
+## Sprint Workflow
+
+```
+1. User describes feature
+2. @athena creates PLAN with phases and agents
+3. User approves PLAN (GATE 1)
+4. Zeus dispatches agents to phases (parallel when possible)
+5. Each agent: TDD cycle → writes IMPL artifact
+6. @themis reviews all phases (GATE 2)
+7. User reviews Themis findings
+8. If approved → user commits (GATE 3)
+9. @mnemosyne updates memory bank
+```
+
+---
+
+## Parallel Execution Declaration
 
-1. State the desired outcome and split only work with distinct ownership or dependencies. Ask @athena to plan only when scope, architecture, or acceptance criteria are materially unclear.
-2. Assign each bounded task to the most specific configured specialist. Include relevant context, expected result, and focused verification; do not make @apollo rediscover context the implementer can inspect directly.
-3. Dispatch independent tasks together only when native background delegation is enabled. Otherwise use normal `task()` calls. Do not create waves for a single task or poll without a returned task ID.
-4. Collect summaries once, resolve dependencies, and report evidence, remaining risk, and blockers. Add @themis, artifacts, or user approval only where the task's risk or requested workflow requires them.
+```
+🔀 PARALLEL EXECUTION — Phase 2
+Running simultaneously:
+- @hermes   → backend tests   → .tmp/IMPL-phase2-hermes.md
+- @aphrodite → frontend       → .tmp/IMPL-phase2-aphrodite.md
+- @demeter  → migrations      → .tmp/IMPL-phase2-demeter.md
+Themis reviews all three after completion.
+```
+
+---
+
+## Artifact Protocol
+
+All phase outputs go to `.pantheon/memory-bank/.tmp/`. See `skill: artifact-management` for the complete protocol (who generates what, templates, lifecycle).
+
+---
+
+## Safety Gates
+
+| Gate | When | Why |
+|------|------|-----|
+| **GATE 1** | After PLAN | User confirms scope |
+| **GATE 2** | After Themis review | User sees changes |
+| **GATE 3** | Before git commit | User controls history |
+
+---
+
+## Model Selection
+
+Model routing is handled by Prometheus and the platform configuration. Zeus delegates model selection to the tier system (`fast` / `default` / `coding` / `premium`).
+
+- **Deep tasks** → High-quality models (Claude, GPT-4)
+- **Quick tasks** → Fast/cheap models (Haiku, 4o-mini)
+- **Visual tasks** → Multimodal models (GPT-4V, Claude Vision)
+- **Cost optimization** → Route to cheapest model that meets quality bar
+
+---
 
-## Boundaries
+## Anti-Patterns
 
-- Zeus coordinates; implementation agents inspect, edit, and verify their assigned scope.
-- Preserve auth/security, data/schema, destructive-action, production, and permission gates.
-- Do not commit, push, merge, deploy, or broaden scope without explicit authorization.
-- Model selection comes from the active configured preset; do not invent a model tier or price.
+- ❌ Zeus doing implementation work (orchestrates, doesn't code)
+- ❌ Skipping TDD cycle (RED → GREEN → REFACTOR)
+- ❌ Auto-committing without user approval
+- ❌ Parallel phases with dependencies (order matters)
+- ❌ Ignoring Themis CRITICAL findings

package/src/skills/auto-continue/SKILL.md

@@ -52,8 +52,6 @@ Full-auto may continue only within a task and scope the user explicitly authoriz
 
 ---
 
----
-
 ## Implementation Pattern
 
 ```
@@ -165,25 +163,26 @@ Should I now run the migration tests? [waiting]
 
 ## Session Heartbeat & Checkpoints
 
-Use checkpoints only when `context_save` and `context_get` are explicitly present
-in the active session's tool list. Standalone OpenCode V2 agent profiles do not
-currently grant these tools; in that case, do not attempt a checkpoint or guess
-a session ID. Carry forward the phase and remaining tasks in the normal task
-handoff instead.
+Session state is **not** file-based. It lives in **pantheon-persistence** under the
+`checkpoint:<slug>` namespace and is cleaned up automatically by a 4h TTL.
+
+Use checkpoints only when `context_save` and `context_get` are explicitly
+present in the active session's tool list. If unavailable, do not attempt a
+checkpoint or guess a session ID; carry the handoff in the normal response.
 
-When the tools are available, write state with `context_save(slug=slug, key=key, content=JSON.stringify(state), session_id=...)` and read it back with
-`context_get(slug=slug, key="latest", session_id=...)`. Capture `session_id` from the first `context_save`
-of the session and reuse it for the rest of the session, so the `latest` pointer survives
-compaction. `state` must be an object — never pass a bare string as `content`: its
+When available, call `context_save` with `content=JSON.stringify(state)` and an
+explicit `session_id`. A successful save needs no immediate `context_get`; read
+only when resuming or when the save result is uncertain. Reuse the same session
+ID so the `latest` pointer survives compaction. `state` must be an object — never pass a bare string as `content`: its
 `goal`/`phase`/`delegations`/`heartbeat` values are objects and `tail` is an array.
 `goal` is optional; when unset, omit the key rather than passing a string placeholder.
 
 ### Heartbeat Check
-- When checkpoint tools are available, an old heartbeat (>300s) is a stall signal; log it before resuming.
-- Write a heartbeat after anti-stall recovery only when the current session exposes the checkpoint tools.
+- Check heartbeat only when checkpoint tools are available and the workflow needs a durable resume.
+- Write a heartbeat after anti-stall recovery only when the current session exposes checkpoint tools.
 
 ### Checkpoint Rules
-1. Save checkpoints for long-running/multi-phase work, context-loss risk, or substantive parallel work — not a one-off command or bounded fix, and only when the tools are available
+1. Save checkpoints only for long-running/multi-phase work, context-loss risk, or substantive parallel work — not a one-off command or bounded fix
 2. Include current phase and remaining tasks when a checkpoint is warranted
 3. On resume, read the latest checkpoint only with a known session ID; otherwise request the missing handoff context.