Harnesses
Harnesses are the differentiator. Instead of asking one agent to do a whole task in one context, a harness spawns focused sub-agents and adds adversarial verification so its output is trustworthy. They are Claude Code skills that live in .claude/skills/ of your scaffolded workspace.
Every harness is a template (tuned per workspace via args), read-only (it returns data; the caller writes), and demonstrated against the synthetic examples/sample-engagement/, so you can run every one with zero real data.
Shipped harnesses
Section titled “Shipped harnesses”These four ship an executable multi-agent workflow today and are the heart of the system.
Executable workflow skills: decision-audit, okf-traverse, scope-creep, and
weekly-synthesis.
/decision-audit
Section titled “/decision-audit”Lints the decision log against the workspace governance rules and returns only verified findings.
- Pattern: one verifier per rule + an adversarial verify pass.
- Run it inside Claude Code, in your scaffolded workspace:
/decision-audit
/scope-creep
Section titled “/scope-creep”Flags deliverables that drift from the scope baseline/ledger, with a refuter pass that downgrades false positives.
- Pattern: per-deliverable classify + severity-downgrade refuter.
- Run it:
/scope-creep
/weekly-synthesis — verified weekly summary
Section titled “/weekly-synthesis — verified weekly summary”A weekly summary and digest — decisions, scope moves, task deltas, risks — with a rubric-gated self-correction loop that revises until the rubric passes or the budget is spent.
- Pattern: synthesize + independent rubric grader + bounded revision.
- Run it:
/weekly-synthesis
/okf-traverse
Section titled “/okf-traverse”Answers a question by traversing the local OKF (Open Knowledge Framework) link graph: read index files to orient, fan out to relevant documents, follow cross-links for corroboration. Works offline — no brain required. Pull the graph first with aios pull-bundle.
- Pattern: orient + fan-out read + cross-link corroboration.
- Run it:
/okf-traverse
Workflow skills
Section titled “Workflow skills”These ship in the scaffold alongside the harnesses above, but drive a typed CLI rather than a multi-agent workflow.
/transcript-decisions
Section titled “/transcript-decisions”Turns meeting transcripts into grounded decisions and explicit task commitments. Pairs well with the Granola integration — export transcripts into 1-inbox/transcripts/ first.
The skill guides a typed CLI engine; it is not a workflow you invoke directly. Drafting is always an explicit operator action, and the result is staged for one human approval before either log changes:
aios transcripts draft --transcripts 1-inbox/transcripts/meeting-a.md,1-inbox/transcripts/meeting-b.mdaios transcripts listaios transcripts approve .aios/staging/transcript-decisions/<stage>.json/aios-sync
Section titled “/aios-sync”Review what’s staged to push, decide what to promote, then run aios push — the curated path from “I did work” to “the team can see it”.
/aios-syncCLI-driven loops
Section titled “CLI-driven loops”Two aios commands drive multi-agent loops from the terminal rather than as in-repo skills.
aios analyze
Section titled “aios analyze”Builds an Agentic Maturity (AM) report from your local agent-session logs (Claude, Codex, Cursor). It computes structural signals — delegation, verification, cost, and more — and places you on the AM Spine. Runs offline; raw session text never leaves your machine.
aios analyze # last 7 days, printedaios analyze --since 30d --report # longer window + deep reportaios analyze --push # send the daily aggregate (ratios + counts only) to the brainaios relay
Section titled “aios relay”Runs an automated Opus 4.8 ↔ Cursor plan/review loop over a task: Opus plans, Cursor executes, Opus reviews, repeating for N rounds (default 3).
aios relay "add rate-limit tests" # 3 rounds, /review-planaios relay "refactor parser" --rounds 2 # custom round countaios relay "tidy imports" --dry-run # plan/review without writingRoadmap
Section titled “Roadmap”More harnesses are deliberately deferred and make good contribution targets: a weekly-synthesis harness with a fidelity verifier, a ticket-hygiene harness, and a classifier-router that picks single-pass vs harness by input size. See the issue tracker for the current list.