haabe

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

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

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

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

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

Non-compliant fixture: handles user content but no wrapping acknowledgment.

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

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

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

Compliant fixture: acknowledges wrapping convention.

Use to conduct STRIDE threat modeling for a system or feature design.

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