haabe

a11y-check

Accessibility audit against WCAG 2.1 AA. Checks semantic HTML, ARIA, keyboard navigation, color contrast, screen reader compatibility.

adopt

Bring Mycelium into a project that already has code. Detects that the repo predates the framework, asks before touching anything, then reads the codebase to draft what it CAN establish (delivery, solution shape) and — the actual point — names what it cannot (purpose, strategy, real user evidence). The output is a discovery backlog with a head start, never a filled canvas.

Testing & QA Solid

assumption-test

Design the smallest viable test to validate or invalidate a critical assumption. Based on Torres's assumption testing framework, organized by Gilad's AFTER model (Assessment → Fact-Finding → Tests → Experiments → Release Results).

bias-check

Use before any research activity or significant decision. Reviews cognitive biases relevant to the current stage.

bvssh-check

Use to evaluate whether current work aligns with Better Value Sooner Safer Happier. Run at diamond completion and periodically.

canvas-health

Lint canvas files for staleness, missing fields, inconsistent evidence types, and orphaned references. Run periodically or before major transitions.

canvas-update

Update canvas sections with new evidence. Ensures canvas stays current as the single source of truth.

corrections-audit

Use to analyze correction trends, surface recurring patterns, and graduate repeat corrections to guardrails or anti-patterns.

cycle-render

Render `.claude/canvas/cycle-history.yml` as a Gantt chart + outcome distribution pie (or ascii / json). Read-only. Consults the attribution registry per `${CLAUDE_PLUGIN_ROOT}/engine/render-conventions.md` consent + privacy gate. Third specialist in the render fleet.

cynefin-classify

Use when facing a new problem to classify its domain (Clear, Complicated, Complex, Chaotic, Confused) and select appropriate methods.

define-done

Pin a measurable, outcome-based Definition of Done for a diamond — a behaviour-change that creates value, not a build-list. Problem-first Socratic sequence; writes definition_of_done to the diamond at birth or retrofits it when missing.

definition-of-done

Use to verify a feature/story meets all Definition of Done criteria before marking complete.

delivery-bootstrap

Use when starting implementation on a new or unfamiliar codebase. Auto-detects tech stack and sets up development context.

devils-advocate

Systematically challenge current assumptions before major decisions. Counters confirmation bias, groupthink, and overconfidence.

diamond-assess

Use to evaluate the current state of a diamond. Checks theory gates, confidence levels, and recommends next action.

diamond-progress

Progress a diamond from one phase to the next. Runs all required theory gate checks, validates evidence, and at Deliver->Complete runs the executable Definition of Done checklist.

diamond-render

Render `.claude/diamonds/active.yml` as a state diagram. Read-only. Default format Mermaid stateDiagram-v2. Recommended at the end of `/mycelium:diamond-assess` so every assessment closes with a visual state-of-play. See `${CLAUDE_PLUGIN_ROOT}/engine/render-conventions.md` for shared render fleet conventions.

dora-check

Assess delivery health metrics. For software: DORA + APEX. For content/AI/service products: product-type-appropriate metrics.

eval-runner

Run eval scenarios to benchmark Mycelium effectiveness. Execute tasks using reflexion loop, validate against success criteria, record metrics.

Code & Development Solid

feedback-review

Aggregate feedback signals across all active loops. Reports health, trajectory, overdue checks, regression warnings, and Goodhart's Law violations.

framework-health

Evaluate Mycelium's own process effectiveness. Measures cycle velocity, discard trends, confidence calibration, gate effectiveness, regression rate. Run quarterly or every 20 cycles.

gist-plan

GIST planning workflow. Structure goals into ideas, steps, and tasks using Gilad's evidence-guided framework.

handoff

Generate structured handoff materials for offline human tasks (interviews, observations, outreach). Creates actionable briefs with phone-friendly capture templates.

harms-check

Use when building anything USER-FACING (or with persuasion/retention/cancellation/consent/pricing flows, or that touches vulnerable people) to surface design-level harm the security/privacy/compliance gates miss: dark/deceptive patterns and foreseeable misuse. Assumes the product works as designed and asks who it could harm and whether it is Happier-negative. NUDGE, not a block.

ice-score

Use to prioritize solutions or opportunities using ICE scoring with evidence-backed confidence.

interview

Use when onboarding a new product/project. Progressive interview to understand purpose, vision, north star, and competitive landscape.

jtbd-map

Map the Jobs to be Done (functional, emotional, and social) that people are trying to get done. Based on Christensen's JTBD theory — applies to any object, not only software.

launch-tier

Classify releases into launch tiers and plan go-to-market. Based on Lauchengco's Loved framework.

Code & Development Solid

log-evidence

Record findings from completed offline human tasks (interviews, observations, outreach) back into the canvas. The re-entry point after /mycelium:handoff.

metrics-detect

Detect which external metric sources apply to this product (GitHub, Plausible, Stripe, etc.) and configure adapters. Retrofit entry point for projects that started before v0.14; also runnable to refresh source list when the product grows.

metrics-pull

Pull snapshots from all configured metric sources, compute deltas against prior snapshots, flag unexplained signals, and draft evidence entries for canvas files. One entry point for all external product/market metrics.

migrate-from-legacy

Migrate a Mycelium project from legacy install (npx-degit, framework files in .claude/) to plugin install (framework lives in plugin cache, .claude/ holds project state only). Detects current install form, walks the user through plugin installation, runs the migration script, and verifies project state survived. Idempotent — safe to invoke on already-migrated projects.

Testing & QA Solid

mocked-persona-interview

Use when real user interviews aren't possible (solo/hobby/dogfood projects) but persona work is still needed. Enforces epistemic discipline: adversarial spectrum, pre-committed stop conditions, speculation tagging. NOT a substitute for /mycelium:user-interview when real users are available.

Web & Frontend Solid

ost-builder

Use to build or update an Opportunity Solution Tree from research data. Never from brainstorming.

ost-render

Render `.claude/canvas/opportunities.yml` as a diagram or structured list. Read-only. Default format Mermaid mindmap. Consults the attribution registry per `${CLAUDE_PLUGIN_ROOT}/engine/render-conventions.md` consent + privacy gate. Second specialist in the render fleet.

preflight

Use before starting delivery work. Pre-implementation validation checklist to ensure readiness.

privacy-check

Use to assess Privacy by Design compliance and GDPR/data protection alignment for a feature or system.

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).

reflexion

Use for self-correcting implementation. Implements the reflexion loop: implement, validate, self-critique, retry (max 3 iterations).

render

Central dispatcher for the canvas/state render fleet. Routes intent to a specialist (`/mycelium:diamond-render`, `/mycelium:ost-render`, `/mycelium:cycle-render`) OR lists what's renderable. Cross-cutting views spanning multiple canvases (opp→sol→cycle traceability, confidence-over-time, cluster-graduation-flow) are research-gated and NOT emitted by default. See `${CLAUDE_PLUGIN_ROOT}/engine/render-conventions.md` for shared conventions.

Testing & QA Solid

retrospective

Structured retrospective after completing a delivery increment or diamond. Captures learning for continuous improvement.

scaffold-cost-check

Measure Mycelium's own scaffold token cost (CLAUDE.md + engine + harness + canvas + memory) and surface a structured estimate. One-shot audit; pair with /framework-health for trend tracking.

Code & Development Solid

security-review

OWASP secure design review for code and architecture. Checks input validation, authentication, authorization, data protection.

service-check

Use to evaluate a service or feature against Downe's 15 principles of good services.

setup

First-run setup for the Mycelium plugin. Creates project-state directories (.claude/canvas, .claude/diamonds, .claude/memory, .claude/harness) and minimal starter files in the user's project. Optionally provisions opencode runtime support (a starter scaffold) when opencode is detected or requested. Idempotent — re-running on an initialized project is a no-op. Run this once after installing the Mycelium plugin and before invoking other skills.

canvas-sync

Synchronize canvas state across team sessions via git. Ensures all team members see the same product knowledge.

fan-out

Parallel agent orchestration for OST exploration. Fan-out multiple solution explorations, fan-in results to compare and select winners.

ping

Smoke-test skill that confirms the Mycelium plugin loaded correctly. Returns a deterministic marker string for plugin-shape validation. Not for end-user invocation in normal use.

prompt-optimizer

A/B test CLAUDE.md instruction changes against eval benchmarks. Capture baselines, test variants, compare results.