AGER Init Graph
Scaffold a multi-agent loop engineering OKF bundle (AGER v0.3).
Prerequisite
okf-graph-eng must be installed (SpillwaveSolutions/okf-plugin). Use it for final validate / impact.
When to use
- New multi-agent system design in OKF
- User asks for orchestrator/workers, judges, loop budgets, tool policies
- Converting a project to AGER layout
Steps
- Confirm target directory (default
.okf/oragent-graph/at repo root). - Run the deterministic generator from the plugin root:
python3 <plugin-root>/scripts/ager-init.py <bundle> --title "<graph title>"
The command refuses an existing destination, renders into a temporary directory, runs strict AGER validation, and installs the bundle atomically. 3. The generated structure is:
<bundle>/
├── index.md
├── log.md
├── agents/
├── runtime/ # LoopPolicy, ScratchPad, Checkpoint, edges
├── ops/ # Failure, Retry, Run, Trigger, limits
├── evaluation/ # Rubrics
├── memory/ # KnowledgeBind, Retrieval
├── tools/
├── models/
├── patterns/
└── schemas/
- Customize the illustrative research graph without deleting required contracts.
- Root
index.mdkeepsokf_version: "0.2"andager_version: "0.3.0". - Absolute links only:
[Lead](/agents/lead-researcher.md). - Validate:
- AGER structural checks (required fields per type)
okf validate/okf-graph.py validatefrom okf-plugin
- Report paths + any errors.
Rules
- Do not invent domain content beyond one illustrative research/example graph.
- Every file: YAML frontmatter with
type,title,description,timestamp(andager_versionon AGER types). - Prefer
record_output_to: { key, mode: append }on workers/judges. - Link FailurePolicy via
on_failure/failure_policyfield.
Canonical scaffold
The complete source tree lives at <plugin-root>/scaffold/. Do not recreate a
second template tree under this skill; tests keep the generated scaffold valid.
Done when
- Bundle exists with agents + runtime + ops
- LoopPolicy includes goal + deadline + price + max_turns + no_progress
- okf validate (if available) reports no broken links