recipe-maintainers/agent-orchestrator
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
main
agent-orchestrator/examples/PLAN-demo1.md
autonomic-bot 289ef07df4 feat: agent-orchestrator v0.1.0 — generic multi-agent harness 
Extracted and generalized from a project-specific agent launch engine. No project
specifics remain in code: paths, the loop kickoff preamble, handoff conventions, and the
on-complete hook are all config/template driven; session_prefix + log_dir are required.

- agents.py: driver + watchdog (data-driven backends via prompt_delivery arg|ping|exec;
  required session_prefix/log_dir; project-rooted path resolution; configurable kickoff
  template, handoff patterns, on_complete task; tmux-safe; selftest + init verbs)
- agent-log.py: config-driven claude transcript renderer
- agents.example.toml: self-contained 2-agent example (dependency-free demo backend)
- prompts/: generic builder/adversary/kickoff templates
- smoke.sh: isolated up+down sandbox proof that cleans up after itself
- flake.nix/.lock: devShell (python311 + tmux + git)
- README.md: schema + verbs + AI-PO usage + nix

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-13 18:39:00 +00:00

395 B
Raw Permalink Blame History

Example phase: demo1

A placeholder phase plan for the example project. In a real project this file is the single source of truth for the phase: its mission and its Definition of Done. The Builder reads it, builds, and claims each gate; the Adversary verifies from a cold start and records PASS/FAIL.

Definition of Done

  • (example) the thing builds and the Adversary records a fresh PASS.