63 件（haabe のリポジトリ） ・ 人気順
概要と使いどころ
Explainability (XAI) audit for products containing AI components. Five-stage tier-scaled check: risk classification, stakeholder×question matrix, fidelity audit, system card, recourse path. Honest about what was validated functionally vs what needs user testing.
日本語の概要は準備中です。原文の説明を表示しています。
Audit whether the theories/methodologies a project claims to implement are faithfully operationalized — or name-dropped, partially built, distorted, or over-claimed. Source-grounds the load-bearing theories; tags the rest provisional. Run periodically alongside /framework-health.
日本語の概要は準備中です。原文の説明を表示しています。
Create or update a Wardley Map of how any domain delivers value. Maps the needs it serves, the capabilities involved, how each is evolving (genesis to commodity), and strategic plays. Applies to any domain, not only software.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluate user-facing interfaces against Nielsen's 10 Usability Heuristics. Complements /mycelium:service-check (Downe = service-level quality, Nielsen = interface-level quality).
日本語の概要は準備中です。原文の説明を表示しています。
One command from "plugin installed" to "running brief on your idea." Combines /mycelium:setup (project-state initialization) and /mycelium:interview (10-minute discovery brief) into a single flow. Run this immediately after installing the Mycelium plugin — it's the recommended entry point for first-time users.
日本語の概要は準備中です。原文の説明を表示しています。
Assess team structure against Skelton's Team Topologies. Evaluate cognitive load, interaction modes, and Conway's Law alignment.
日本語の概要は準備中です。原文の説明を表示しています。
Use to conduct STRIDE threat modeling for a system or feature design.
日本語の概要は準備中です。原文の説明を表示しています。
Guide for conducting Torres-style story-based interviews with the people whose experience you're researching, with bias mitigation and a JTBD lens.
日本語の概要は準備中です。原文の説明を表示しています。
Derive this project's own integration conventions from what the code already does, draft them as a wiring contract, and hold new work to it. Closes the built-but-not-wired gap at L3 (walking skeleton) — a mechanism that ships and is never called reads green in every other check.
日本語の概要は準備中です。原文の説明を表示しています。
OWASP secure design review for code and architecture. Checks input validation, authentication, authorization, data protection.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Map the needs of the people you're building or exploring for, independently of solutions, using Allen's User Needs Mapping methodology. Identifies underserved needs that feed into the Opportunity Solution Tree.
日本語の概要は準備中です。原文の説明を表示しています。
Use to evaluate a service or feature against Downe's 15 principles of good services.
日本語の概要は準備中です。原文の説明を表示しています。
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).
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Print your own north-star row from your own record, and nothing else. Reads .claude/harness/decision-log.md, the canvas and the hook logs in this project; prints one line (decisions before the first source file, of which citing outside evidence, kills before code, sessions). Sends nothing anywhere. Opt-in; paste the line where you like or not at all.
日本語の概要は準備中です。原文の説明を表示しています。
Use to build or update an Opportunity Solution Tree from research data. Never from brainstorming.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Lint canvas files for staleness, missing fields, inconsistent evidence types, and orphaned references. Run periodically or before major transitions.
日本語の概要は準備中です。原文の説明を表示しています。
Systematically challenge current assumptions before major decisions. Counters confirmation bias, groupthink, and overconfidence.
日本語の概要は準備中です。原文の説明を表示しています。
Use before starting delivery work. Pre-implementation validation checklist to ensure readiness.
日本語の概要は準備中です。原文の説明を表示しています。
Use to evaluate the current state of a diamond. Checks theory gates, confidence levels, and recommends next action.
日本語の概要は準備中です。原文の説明を表示しています。
Use for self-correcting implementation. Implements the reflexion loop: implement, validate, self-critique, retry (max 3 iterations).
日本語の概要は準備中です。原文の説明を表示しています。
Use when onboarding a new product/project. Progressive interview to understand purpose, vision, north star, and competitive landscape.
日本語の概要は準備中です。原文の説明を表示しています。