maestro-v2-migration
maestroCLI v2 Architecture Guide
Why This Exists
maestroCLI went through a significant architectural shift in v2. Sessions that touch v2 code without understanding these changes waste time rediscovering what was renamed, what was removed, and what the new patterns look like. This guide prevents that.
The v2 Changes (in dependency order)
1. Context --> Memory Rename
Everything called "context" in v1 is now "memory" in v2.
| v1 (deprecated) | v2 (current) |
|---|---|
ContextPort |
MemoryPort |
FsContextAdapter |
FsMemoryAdapter |
contextAdapter |
memoryAdapter |
context-write command |
memory-write command (but context-write still works as CLI alias) |
src/adapters/fs/context.ts |
src/adapters/fs/memory.ts |
More from reinamaccredy/maestro
conductor
Implementation execution for context-driven development. Trigger with ci, /conductor-implement, or /conductor-* commands. Use when executing tracks with specs/plans. For design phases, see designing skill. For session handoffs, see handoff skill.
10maestro-revert
Git-aware revert of track, phase, or individual task. Safely undoes implementation with plan state rollback.
9maestro-new-track
Create a new feature/bug track with spec and implementation plan. Interactive interview generates requirements spec, then phased TDD plan. Use when starting work on a new feature, bug fix, or chore.
8init
Generates AGENTS.md and CLAUDE.md files using the WHAT/WHY/HOW framework. Explores the codebase and produces minimal (<100 line) context files with progressive disclosure.
8maestro-setup
Scaffolds project context (product, tech stack, coding guidelines, product guidelines, workflow) and initializes track registry. Use for first-time project onboarding.
7tracking
>
7