MaestroKit

0.11.0

MaestroKit - plan/implement/test/document workflow installer, validators and packaging for AI coding agents.

Minimum PowerShell version

7.0

Installation Options

Copy and Paste the following command to install this package using PowerShellGet More Info

Install-Module -Name MaestroKit -RequiredVersion 0.11.0

Copy and Paste the following command to install this package using Microsoft.PowerShell.PSResourceGet More Info

Install-PSResource -Name MaestroKit -Version 0.11.0

You can deploy this package directly to Azure Automation. Note that deploying packages with dependencies will deploy all the dependencies to Azure Automation. Learn More

Manually download the .nupkg file to your system's default download location. Note that the file won't be unpacked, and won't include any dependencies. Learn More

Owners

Copyright

(c) 2026 Arthur Biazon Machado. MIT licensed.

Package Details

Author(s)

  • Arthur Biazon Machado

Tags

AgentSkills AI ClaudeCode OpenCode OhMyPi Workflow

Functions

Install-Maestro Test-MaestroKit Invoke-MaestroSmokeInstall

PSEditions

Core

Dependencies

This module has no dependencies.

Release Notes

## 0.11.0 — 2026-10-09 ### Changed - `orchestrate`: Phase 1 rebuilt from static wave scheduling into a frontier loop over dependency-ordered milestones — the frontier expands after every return; all ready milestones spawn together per the harness's Execution Substrate (new per-harness appendix: OMP batch/async/isolation, Claude Code parallel agents + worktree isolation, OpenCode multi-call foreground; capability-based detection ladder, portable baseline as default). - Conflict scans and serialize-or-risk prompts replaced by write-safety classes: disjoint write units run in parallel, overlapping units are ordered by construction, isolated spawns are exempt. - Re-plan revision rule: at Retries >= 3 orchestrate attempts exactly one milestone revision (spec change + Decision Log entry + Retries reset) before failing a milestone; a second exhausted revision marks it Failed and halts dependents. Intent-touching failures are never re-planned — they halt for the user (fix-forward). - Plan spec: Dependencies are ordering hints for frontier selection, not an execution contract; new append-only Decision Log section (orchestrate-written); file-overlap rule reframed as write-safety. - Approval scope narrowed: cue approves the Intent plus the initial milestone set; execution-time re-plan revisions do not require re-approval while the Intent is unchanged. - play: sequencing boundary reworded — the caller owns ordering and frontier decisions; dependencies are ordering hints. - instruments: reports the detected execution substrate alongside model assignments; interlude signals re-worded around re-plan revision exhaustion. ### Migration - Existing Plans run unchanged: milestone header format, Retries, and Approved fields are untouched — Dependencies are simply read as ordering hints. - Already-approved Plans keep their approval; no re-run of cue is required.

FileList

Version History

Version Downloads Last updated
0.13.0 4 10/12/2026
0.12.1 6 10/9/2026
0.12.0 3 10/9/2026
0.11.0 (current version) 2 10/9/2026
0.10.1 16 9/24/2026
0.10.0 7 9/23/2026
0.9.6 21 9/4/2026
0.9.5 7 9/4/2026
0.9.4 11 8/29/2026
0.9.3 8 8/25/2026
0.9.2 8 8/25/2026
0.9.1 3 8/25/2026
0.8.2 10 8/25/2026
0.7.2 7 8/25/2026
0.7.1 7 8/25/2026
Show more