abmach
- 10 skills
- 0 followers
- 6 hours ago last updated
- ▌ Score · abmachDocument implementation changes - audit finished code and update docs, README, and CHANGELOG for shipped features; invoked by orchestrate when Docs Affected = true, via "/score PLAN-001" for one plan, or "/score" alone for batch mode
- ▌ Arrange · abmachArrange tests - design and create integration and E2E test specs from a Plan for features about to enter integration testing; invoked by orchestrate or via "/arrange PLAN-001"
- ▌ Compose · abmachCompose technical solutions - map a feature request to a Plan with milestones as a DAG, test tiers, and development specs; invoked via "/compose <feature>" to design before orchestrate executes
- ▌ Prelude · abmachInitialize a non-Maestro workspace by scanning the codebase to create Repo Fingerprint, Contexts, and ADRs so the bundle is ready to use; invoke via "/prelude" once when adopting Maestro into an existing project
- ▌ Audition · abmachAudition tests - execute test suites and capture pass/fail results, screenshots, and artifacts for visual regression routing; invoked by orchestrate after arrange or via "/audition <scope>"
- ▌ Rehearse · abmachRehearse - stress-test a plan against the project's domain model by challenging assumptions, sharpening terminology, and updating contexts/ADRs inline; invoked via "/rehearse <plan or feature>" to refine language before orchestrate or after compose flags ambiguity
- ▌ Elaborate · abmachElaborate plans - distill detail from higher-quality models into a Plan to fill gaps and simplify execution for simpler models; invoked via "/elaborate PLAN-001" after compose but before orchestrate to add implementation guidance and test strategy
- ▌ Interlude · abmachStatus interlude - summarize workspace state (active, blocked, and failed plans; open issues by priority; docs pending) from the Plans Index and Issues Index and suggest the next action, modifying nothing; invoked via "/interlude [plans | issues | docs]"
- ▌ Instruments · abmachConfigure the instruments - assign AI models to each section of the Maestro workflow (cheap implementation, reasoning-heavy composition, etc.), stored in knowledge/instruments.md with per-harness application guidance; invoked via "/instruments [section]"
- ▌ Orchestrate · abmachOrchestrate feature implementation - execute an existing Plan as a parallel DAG by spawning play subagents, then arrange + audition for tests, route visual regressions to tune; invoked via "/orchestrate PLAN-001"