Skip to content

Quick Start

Once @maestria/codex is installed, start a fresh Codex CLI session so the plugin marketplace state is loaded.

Use the orchestrator skill when a task is unfamiliar, cross-file, or risky:

$maestria:orchestrator I need to add rate limiting to the API. Plan and implement it.

The orchestrator chooses between direct work and specialist skills based on task risk and available runtime capabilities. It is methodology guidance, not a replacement for Codex’s own approvals or sandbox.

Use one specialist when you need one kind of help:

$maestria:adventurer Trace the authentication flow and report the relevant files.

Available roles are:

Skill Use it for
$maestria:adventurer Reconnaissance and codebase mapping
$maestria:architect Architecture trade-offs and ADR decisions
$maestria:builder Focused implementation and verification
$maestria:diagnose Root-cause analysis and regression tracing
$maestria:planner Phased plans, dependencies, and rollback points
$maestria:reviewer Independent review after implementation
$maestria:writer Documentation and structured prose

The workflow modes are Codex skills rather than slash commands:

Skill Route
$maestria:fein Full pipeline: reconnaissance, design, implementation, and review
$maestria:sonar Research-only route that stops before implementation
$maestria:blitz Fast capability-aware route for small or well-understood work

For example:

$maestria:fein Add rate limiting to the API.

After the builder completes, invoke the reviewer in a separate turn:

$maestria:reviewer Review the current diff for correctness, security, and missing tests.

The reviewer skill is advisory. Codex may still expose write-capable tools while that skill is active; use Codex’s own sandbox and approval controls when a hard boundary is required.