Skip to content

haabe/mycelium

v0.332.0MIT

I realized I let the agent start coding before I was sure it was working on the right thing, so I built this. Now it doesn't get to write code before there's a reason. The agent asks who this is for. It asks what you're assuming, and what would show you wrong. The rules run as hooks, so once you have started it in a repo the build stays shut until the answers are there. Purpose, strategy, opportunities, then delivery and market feedback. It adds skills and hooks, keeps its own state in a .claude/ folder, and won't edit the files already in your repo unless you ask it to.

GitHubOpen Website
skills

receipt-render

Render a completed diamond's work as a shareable, factual one-page "work receipt" (problem framed, assumptions tested, what was killed vs kept) carrying an origin line + a volitional onward-handoff data flow. Read-only. Consults the attribution registry per ${CLAUDE_PLUGIN_ROOT}/engine/render-conventions.md consent + privacy gate. Follows the render fleet's shared conventions + consent gate (Check 43 applies via the -render name); a standalone shareable-artifact generator, NOT a /render dispatcher target. Audience fixed external (a hand-it-over artifact).

Read SKILL.md at the source

Pinned to revision d44421b0667b, so it is the text this page describes rather than whatever the author pushed since.

Files

Every link opens the file at its source, pinned to the revision this page describes.