MaestroKit

0.13.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

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

Install-PSResource -Name MaestroKit

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.13.0 — 2026-10-12 ### Added - **`hum` skill** — one-shot loose jobs: small, well-scoped changes executed directly without a Plan, carrying the same knowledge-consistency obligations a Plan does. A binding scope gate refuses feature-scale work and routes to `compose` (with the escalation-symmetry rule: accumulating hums in one area are a compose signal); a knowledge-sync checklist (ADR, contexts, system-behavior, repo-fingerprint, principles — each per its own spec's criteria, never unconditional) gates done; high-risk categories abort with a recommendation, like the `tune` subagent. hum also refuses to run while a plan is 🔄 In progress — one active execution per workspace; an inline writer racing in-flight `play` subagents corrupts both. Inline execution is the contract: where a harness wraps the invocation in its generic orchestration contract, the hum skill's boundaries govern — no spawns, no frontier, no substrate detection. New reference spec `references/hum.md` defines the scope-gate triggers, the sync checklist, and the ledger format. - **`jobs/index.md`** — append-only one-line activity ledger (`JOB-NNN` entries; `AUDIT-NNN` drift-audit verdicts), created lazily by hum. Read by `compose` pre-flight and `interlude` for recent loose activity. - **Knowledge drift detection** (`references/conventions.md`) — history-based staleness signal: for each knowledge working file, the last commit that touched it versus source commits since. No sync markers (skills and agents never commit, so a marker cannot know its own landing revision — history already holds the truth). Git is the only observer that sees every contributor, including teammates who bypass the harness entirely; detection is diff-based, warn-only, a tripwire rather than a verdict. - README: optional warn-only CI canary snippet (source changed with no movement under `knowledge/`, `plans/`, `issues/`, or `jobs/`). ### Changed - `interlude`: status snapshot gains a `Drift:` block (file-level staleness with commit counts) and drift joins next-action guidance at low priority — routing small reconciliations to `/hum`, larger ones to `/compose`. `Drift:` and `Jobs:` blocks always render regardless of the `plans | issues | docs` focus argument — they ground the Next recommendation. - `compose`: pre-flight warns — never aborts — when knowledge working files are stale against source history, so a new Plan cannot silently design against stale knowledge. - README: "When not to use it" rewritten — small one-shot work now has a sanctioned path (`/hum`) instead of a ceremony-vs-drift dilemma; the teams bullet now states what the drift audit does and does not fix. - `instruments`: hum added to the `implementation` section's `Plays in` column — inline on the session model, not spawn-routed; the `implementation` assignment guides session-model choice for hum-heavy work. - `conventions.md`: `hum` row in the File Ownership Matrix and the Artifact and Directory Map; new *Knowledge Drift Detection* section (binding on interlude and compose). ### Migration - None; additive skill and reference. Existing Plans, Issues, and knowledge files are untouched. `/hum`, the drift checks, and the canary activate on the next installer run; `jobs/index.md` appears lazily on the first hum job or audit verdict.

FileList

Version History

Version Downloads Last updated
0.13.0 (current version) 4 10/12/2026
0.12.1 6 10/9/2026
0.12.0 3 10/9/2026
0.11.0 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