tracking
Prerequisites
- Load maestro-core first - maestro-core for routing table and fallback policies
- Routing and fallback policies are defined in AGENTS.md.
Tracking - Persistent Memory for AI Agents
Graph-based issue tracker that survives conversation compaction. Provides persistent memory for multi-session work with complex dependencies.
Entry Points
| Trigger | Reference | Action |
|---|---|---|
bd, beads |
references/workflow.md |
Core CLI operations |
fb, file-beads |
references/FILE_BEADS.md |
File beads from plan → auto-orchestration |
rb, review-beads |
references/REVIEW_BEADS.md |
Review filed beads |
Quick Decision
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.
7maestro-implement
Execute track tasks following TDD workflow. Single-agent by default, --team for parallel Agent Teams, Sub Agent Parallels. Use when ready to implement a planned track.
7