Pipeline composition
Route work through focused stages so no single context does everything.
OPEN-SOURCE AGENT METHODOLOGY
A portable harness for AI coding agents. Route complex work through specialists, structured handoffs, and independent review.
npx maestria install opencodenpm · pnpm · yarn · bun · deno
- any runtime works
npx maestria install opencode
@maestria/opencode installed - 8 agents wired
maestria status
# one task through the harness - thinker, worker, verifier
01 / THE METHOD
Route work through focused stages so no single context does everything.
The builder produces; the reviewer sees it fresh.
The methodology stays consistent while each platform uses its native primitives.
02 / SPECIALISTS
Routes tasks to specialists, manages commit protocol
The dispatcher selects the smallest safe route for each turn: it executes known low-risk work directly, delegates specialist work with concise briefs, integrates results, enforces the maker/checker split, and manages the commit protocol.
Codebase reconnaissance, deep code understanding
Maps unknown territory so downstream specialists can work with full context. Explores code paths, traces dependencies, and produces structured reconnaissance reports.
Architecture decisions, trade-off analysis, ADRs
Makes architecture decisions systematically. Clarifies the problem, presents options with trade-offs, and documents decisions as Architecture Decision Records.
Focused implementation, single-task execution
Handles exactly one atomic task per invocation. Reads context, edits minimally, verifies with tests, and reports what changed and why.
Systematic bug tracing, root cause analysis
Traces bugs systematically from error to source, source to git history, and history to blast radius. Finds root cause and all similar problems in the codebase.
Implementation plans with phased milestones
Creates implementation plans with goals, phased milestones, atomic tasks, verification criteria, and rollback points for complex features.
Code review with quality gates
Runs one general review for quality, correctness, security, and maintainability, adding specialist lenses only for matching security, performance, architecture, or UX risk. Preserves blind review, lens exclusivity, observation over reasoning, and [fix]/[dismiss]/[escalate] triage. Enforces the maker/checker split.
Documentation following structured patterns
Writes documentation following structured patterns. Covers purpose, usage, and details with progressive disclosure and plain language.
03 / ADAPTERS