From mycelium
Runs pre-implementation validation checklist before delivery work, checking constraints, scope, context, tech readiness, security, accessibility, and validation strategy.
npx claudepluginhub haabe/mycelium --plugin myceliumThis skill uses the workspace's default tool permissions.
Pre-delivery validation checklist. Run before every implementation task.
Verifies features/stories meet Definition of Done criteria via checklists for functionality, code quality, testing, and security before completion.
Assesses information completeness for specs, PRDs, tickets, RFCs, and multi-step tasks via reverse thinking, blocking planning until prerequisites verified.
Performs multi-AI validation, scoring, and review of code or documents using Codex and Gemini CLIs during Double Diamond Deliver phase.
Share bugs, ideas, or general feedback.
Pre-delivery validation checklist. Run before every implementation task.
Before scoping any delivery work, establish constraints. Do not propose a plan before knowing the budget.
If time budget < 8 hours, scope aggressively — one vertical slice, no polish. If the initial plan exceeds the time budget, cut scope before presenting it to the user.
Source: Hoskins transcript (2026-04-25) — agent proposed 20-hour plan before learning user had 8 hours. Goldratt (Theory of Constraints — identify the constraint before optimizing). Corrections.md: "Over-scope before constraints."
.claude/canvas/scenarios.yml has scenarios for this solution, and acceptance criteria trace back to scenario success/failure states (Hoskins)Software/AI tool:
Content:
Service:
Software:
Content:
Software: Test approach defined (unit, integration, e2e), edge cases and error scenarios identified. Content: Review process defined (SME, self-checklist, fact-check), learning objectives mapped. AI tool: Eval test cases defined, red-team scenarios planned, bias testing approach chosen. Service: Walkthrough planned, client feedback mechanism defined.
Example:
Success criteria:
1. "Users can complete onboarding in < 5 min" — verified by usability test
2. "API responds in < 200ms at p95" — verified by load test
3. "No new lint or type errors introduced" — verified by CI
Do not proceed to implementation. Instead: