minnow-plan skillA
minnow-plan is agent-read markdown (skill) from henrigrimm/minnow: Write an implementation plan in Minnow's orchestrator board schema — front matter with todos, waves, and tasks carrying Build/Test/Accept/Touches. Use when asked for a Minnow plan, an orchestrate/board plan, a wave plan, or a plan under documentation/plans/. Validates the result with Minnow's own parser..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Minnow plan ## What this produces Write `documentation/plans/<kebab-slug>.md` at the top level of the current Minnow checkout. The plan picker uses `ORCHESTRATE_PLANS_PREFIX` in `src/chat/plans/plan-path.ts`. Do not put board plans under `references/` or `verification/`, or use a `-spec.md` or `-research.md` suffix; those files are filtered from the picker. ## Process 1. Restate the request in one sentence. Ask clarifying questions only when scope is genuinely ambiguous. Use `AskUserQuestion` with related questions batched; if the codebase can answer one, read it instead. 2. Explore the relevant code, real file paths, conventions, and test setup before writing. Use `Explore` subagents when the surface is wide. Never use placeholder paths in the finished plan. 3. Choose `large`, `medium`, or `small` granularity and state it in the header. Default to `medium`. 4. Write the plan file. 5. Run `node .claude/skills/minnow-plan/scripts/validate-plan.mjs documentation/plans/<slug>.md`. Fix every error and rerun until it exits cleanly. A plan is not done without a clean run. 6. Report the path, wave count, task count, and successful validation. ## Schema …
Read the whole file at its exact version.
How to install
mdr add henrigrimm/minnow/minnow-plan@git:20260920.5de7156mdr add henrigrimm/minnow/minnow-plan@sha256:d71ba97092583f21Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_mb4reirlz4w3btrn)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5430 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
henrigrimm/minnow · 23 stars · license AGPL-3.0 · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_mb4reirlz4w3btrn GET https://markdownregistry.com/api/v1/resolve?ref=henrigrimm/minnow/minnow-plan GET https://markdownregistry.com/api/v1/blob/d71ba97092583f2184bf15da7ae3ceaf5f11b06324490028e114fa46b8c5bab0
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.