Zimster gives an agent clear steps, useful tests, and review at the points that matter. One implementation owner stays in charge. Extra agents are used when there is a reason, not as a default.
Zimster keeps the workflow focused: plan when planning is useful, write tests that prove the behavior, review the risky parts, and only call the work complete when the evidence supports it.
See how the workflow is structured →The project is intended for more than one coding-agent environment. The commands differ, but the workflow stays the same.
Add the public repository as a marketplace source, install the plugin, and confirm it appears in the installed list.
codex plugin marketplace add https://github.com/wazimmerman/zimster.gitcodex plugin add zimster@zimster --jsoncodex plugin listUse the Claude-oriented package surface and the install flow documented for the current release.
/plugin marketplace add wazimmerman/zimster/plugin install zimster@zimster/reload-pluginsUse the portable ZIP when you want the skills and supporting files without starting from a harness-specific package.
Download the portable ZIPExtract it into your plugin or skills locationFollow the notes for your coding agentThe plugin keeps useful engineering practices and trims back the parts that tend to make agent runs slow, repetitive, or hard to follow.
The main agent keeps the implementation coherent instead of splitting every task across a growing tree of agents.
RED-GREEN-REFACTOR is used as evidence, not as a label attached after the code already works.
Zimster can use other agents, but only when the work is bounded and the split makes the result better.
A cheaper model does not create a reason to delegate. Model routing is considered only after delegation already makes sense.
Small work stays small. Public interfaces, migrations, security, and other load-bearing changes get a higher proof bar.
Self-review, checkout integrity, independent approval, and final completion are tracked separately.
Set the risk level, the Git disposition, and the minimum proof required.
Use a plan for real choices and multi-step work. Skip the extra ceremony when the task is already clear.
The implementation owner writes the tests, code, and corrections while keeping the whole change in view.
Send out a scout, reviewer, or implementation slice only when the boundary is useful and easy to verify.
Run the affected checks, review the risky seam, and keep the approval tied to the exact candidate.
Map the requirements to proof and report only the completion state the evidence supports.
Twelve skills cover the workflow without turning it into a catalog of overlapping personas.
Selects the smallest useful workflow for the task.
Clarifies consequential choices before coding.
Turns larger work into coherent, testable slices.
Keeps one implementation owner responsible for the change.
Uses observable RED-GREEN-REFACTOR.
Delegates only genuinely independent workstreams.
Matches review depth to the risk in the change.
Checks feedback before changing the implementation.
Reproduces the problem and proves the root-cause fix.
Requires fresh evidence before a success claim.
Creates a clean place for risky changes when needed.
Verifies the result and hands off a clean branch.
The labels below show how far v0.6.0 has been tested in each environment. Some packages have been run directly; others have only had their structure and packaging checked.
| Coding agent | Testing status | What was checked |
|---|---|---|
| Codex | Installed-package verified | The package and install surface were checked in Codex. This is narrower than claiming every workflow path was exercised live. |
| OpenCode | Live verified | The current release includes live verification in OpenCode. |
| Claude Code | Structurally validated | The package shape and related files were checked; hands-on verification is still narrower. |
| Cursor | Structurally validated | The adapter and package surface were checked; marketplace packaging remains a separate step. |
| Kimi Code | Structurally validated | The package surface was checked, with less live evidence than Codex or OpenCode. |
| Pi | Structurally validated | The package declaration and adapter surface were checked; ecosystem distribution work remains. |
All downloads come directly from the v0.6.0 GitHub release.
Installable package for the Codex plugin surface.
Release package for the Claude-oriented install path.
Skills-first package for more general use.
Use this list to verify the release files.
Read the main guides here, or open the corresponding source files on GitHub.
Packages, setup, updates, removal, and install checks.
Delegation, routing, review limits, and local records.
The workflow model, skill set, package surfaces, and proof model.
Validation, release work, receipts, package checks, and updates.
Why the project exists and what it is trying to improve.
Report bugs and beta feedback on GitHub.
Open an issue with the Zimster version, your coding agent, and the steps needed to reproduce it.