Pipeline composition
Route work through focused stages instead of asking one context to do everything.
MAESTRIA / METHODOLOGY LAYER
A portable harness for AI coding agents. Route complex work through specialists, structured handoffs, and independent review.
Thinker
Worker
Verifier
Workflow
Inspector
01 / THE METHOD
Route work through focused stages instead of asking one context to do everything.
The builder produces; the reviewer sees it fresh.
Methodology stays consistent while each platform uses native primitives.
02 / SPECIALISTS
Routes tasks to specialists, manages commit protocol
The dispatcher that never implements. Routes every task to the right specialist, enforces 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 clear, human-readable prose.
03 / ADAPTERS
04 / DOCUMENTATION
Core
How It WorksThe dispatcher, seven specialists, and the staged pipeline.Pipeline & RolesThinker, worker, and verifier roles and the maker/checker split.Specialist ReferenceAll eight agents: scope, artifact, and constraint for each.When to UseDecide between direct execution, a specialist, or the full pipeline.Adapters
@maestria/opencodeOpenCode plugin with 8 agents and global rules.@maestria/kimi-codeKimi Code plugin with 8 declarative skills.@maestria/cursorCursor IDE and CLI plugin with specialist agents.@maestria/pi & @maestria/ompPi and Oh My Pi orchestration through subagents.@maestria/hermesHermes Agent methodology layer and mode system.