Your agent already plans, swarms, and ships. What it can't do alone — prove the result, remember the decision, know when it's actually done. The garden closes that gap.
bus7 events published · phase.start · evidence.record · gate.check
loomGATE PASSED · proven, not self-reported ✓
stop 01 / 08 — the garden gate
every garden starts at the gate
wicked-garden reads the shape of each task — a typo fix, a schema migration, a 2am incident — and applies exactly that much rigor, gating each phase on re-derived evidence. Install it once; it curates everything that follows.
❋9 work-shape archetypes route the right amount of rigor
❋Evidence-gated phases fail closed — never a vacuous green
❋The gate compiles into any repo and runs with nothing installed
the garden itself
stop 05 / 08 — the memory bed
your agent finally remembers
Persistent, searchable knowledge from plain markdown and SQLite full-text search. No vector DB, no embeddings — session 47 picks up exactly where session 1 left off, and you can read every byte. A code graph maps what words can't: blast-radius, callers, and lineage on demand.
❋Full-text search + agent reasoning, not cosine distance
❋Chunks → synthesized wiki — every claim traces back to a file
❋Code graph of your repo — blast-radius, callers, lineage on demand
now it remembers
stop 06 / 08 — the playbook bed
it knows how, not just what
Repo-specific playbooks generated from HEAD — fix-bug, add-feature, verify — with the exact files, the wiring step, and the gotcha that bites. Your agent stops re-deriving the method every session.
❋Playbooks read HEAD, so they track your code instead of rotting
❋Diff-aware refresh — only what moved re-runs
❋Cross-CLI via the skills standard
now it knows your repo
stop 03 / 08 — the trellis
every bed, wired right
The orchestration runtime the set stands on: compose resolves, version-checks, and installs every peer, and the conduct gate re-runs verifiers through the vault — failing closed, never rubber-stamping. One doctor call tells you what's missing.
❋doctor — every peer's health in a single call
❋Resolution ladder respects where you installed each peer
❋Fail-closed gate verdicts, with attestations
the kit, wired right
stop 02 / 08 — the evidence bed
a floor that can't lie
Every claim is recorded with the criteria it must clear, then re-derived instead of trusted — integrity checked deterministically, judgment rendered by an independent evaluator that isn't the agent who did the work. Garden blocks without it.
❋Integrity tier — recompute the hashes, re-run the verifier, CI-safe
❋Append-only, tamper-evident attestations — criteria frozen to evidence
the evidence floor — in place
stop 04 / 08 — the proving bed
green finally means green
A Writer → Executor → Reviewer pipeline with enforced separation — the reviewer reads cold evidence and never sees the executor's context. 40 specialist agents, one SQLite ledger, a plain-English oracle.
❋Independent verdicts — reviewer never sees executor context
❋SQLite ledger with a plain-English oracle
green means green
stop 07 / 08 — the irrigation
your tools finally talk
A local-first event bus over one SQLite file — producers fire and forget, subscribers catch up at their own pace. No broker, no daemon, no ports; the whole garden coordinates without glue.
❋Fire-and-forget — producers never block, degrade gracefully if absent
❋At-least-once delivery with cursors that survive restarts
❋One SQLite file. No server. No infrastructure.
now your tools talk
stop 01 / 08 — the garden gate
every garden starts at the gate
wicked-garden reads the shape of each task — a typo fix, a schema migration, a 2am incident — and applies exactly that much rigor, gating each phase on re-derived evidence. Install it once; it curates everything that follows.
❋9 work-shape archetypes route the right amount of rigor
❋Evidence-gated phases fail closed — never a vacuous green
❋The gate compiles into any repo and runs with nothing installed
the garden itself
also from the garden
It's 11pm. The deck's due tomorrow.
Tell it what you need — board deck, landing page, demo video — and watch it build in your browser. Point at anything that's off and say what to fix. Export clean HTML, PDF, native PowerPoint, or a narrated video. No code. No design tickets. Just you and the deadline.
wicked-garden curates the rest. The third command runs inside Claude Code — it asks which optional layers you want and installs your picks at their latest versions.
01
add from marketplace
02
install the gate
03
pick your toolsruns inside Claude Code · choose testing, memory, playbooks, bus, and more
