AI Agent Workflow Collection

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

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

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

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

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

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

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

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

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

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

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 definitionofdone to the diamond at birth or retrofits it when missing.

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

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

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.

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 ${CLAUDEPLUGINROOT}/engine/render-conventions.md for shared render fleet conventions.

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

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

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

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

Evaluate Mycelium's own process effectiveness. Measures cycle velocity, discard trends, confidence calibration, gate effectiveness, regression rate.

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

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.

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

Map user Jobs to be Done across functional, emotional, and social dimensions. Based on Christensen's JTBD theory.