---
title: "zimster"
description: "A software development workflow for coding agents."
canonical: https://agentpluginsdirectory.com/plugins/zimster
last-updated: 2026-09-25
---

# zimster
A software development workflow for coding agents.
- Slug: zimster
- Publisher: William Zimmerman
- Repository: https://github.com/wazimmerman/zimster
- Manifest: plugin.json
- Version: 0.7.2
- License: MIT
- Category (editorial): code-review
- Skills: 12 (designing-work, dispatching-parallel-agents, finishing-a-development-branch, owner-driven-development, receiving-code-review, risk-adaptive-review, systematic-debugging, test-driven-development, using-git-worktrees, using-zimster, verification-before-completion, writing-plans)
- MCP servers: 0
- Stars: 2
- Repository created: 2026-07-27
- Repository last pushed: 2026-09-01
- Publisher type: User
- Listing: https://agentpluginsdirectory.com/plugins/zimster
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## What zimster does, in the publisher's words

<img

>

One development workflow for coding agents, without the agent sprawl.

From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/wazimmerman/zimster/HEAD/README.md

## Skills

- designing-work: Turn an ambiguous or consequential software request into a compact mission contract before implementation.
- dispatching-parallel-agents: Delegate only genuinely independent workstreams with explicit ownership, budgets, and integration contracts.
- finishing-a-development-branch: Finish or hand off work with complete change inspection, fresh evidence, explicit commit disposition, and a safe branch outcome.
- owner-driven-development: Execute an approved plan with one persistent implementation owner, explicit Git disposition, bounded delegation, and risk-triggered review.
- receiving-code-review: Evaluate review findings technically, fix valid defects in a batch, and preserve evidence when pushing back.
- risk-adaptive-review: Classify risk deterministically, review complete working-tree changes at architectural seams, and converge with one recheck.
- systematic-debugging: Reproduce failures, isolate root cause with evidence, and fix them through a regression test.
- test-driven-development: Develop behavior through verified, behavior-specific RED-GREEN-REFACTOR cycles and falsifiable tests.
- using-git-worktrees: Apply deterministic branch and worktree isolation policy without disturbing unrelated user changes.
- using-zimster: Select the smallest Zimster workflow and risk profile that materially improves a software-development task.
- verification-before-completion: Discover canonical project gates and require fresh, correctly classified evidence before any completion claim.
- writing-plans: Convert an approved mission into a concise vertical-slice plan with risk profile, Git policy, and proof obligations.

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.