Stats
Actions
Tags
From fiddle
Challenge every aspect of this plan or design until we reach shared understanding. Walk down each branch of the decision tree, resolving dependencies between decisions one-by-one.
How this skill is triggered — by the user, by Claude, or both
Slash command
/fiddle:challengeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Challenge every aspect of this plan or design until we reach shared understanding. Walk down each branch of the decision tree, resolving dependencies between decisions one-by-one.
Challenge every aspect of this plan or design until we reach shared understanding. Walk down each branch of the decision tree, resolving dependencies between decisions one-by-one.
If a question can be answered by exploring the codebase, explore the codebase instead of asking.
ARGUMENTS: {ARGS}
--phase discover: Read docs in docs/product/ and docs/technical/, recent beans, and any --context files. Open by synthesizing what discover-docs and external research found — present the scope as you understand it, confirm the user's intent, then challenge assumptions and constraints. Done when scope has no open branches. State "Scope is solid — ready for DEFINE" and stop.
--phase define: Read the design doc (most recent in docs/plans/), panel commentary if present, relevant source files, and any --context files. Challenge edge cases, integration points, panel dissent, failure modes, and sizing. Done when every decision branch is resolved. State "Design holds up — ready for implementation planning" and stop.
Standalone: Challenge whatever the user presents. No phase-specific framing. Done when all branches are resolved — summarize the resolved decision tree and stop.
npx claudepluginhub peel/fiddle --plugin fiddleDiscusses planning phases to identify ambiguities, capture decisions in CONTEXT.md, and lock them before plan generation. Supports phase numbers or --project mode.
Plans implementation by investigating code, writing specs and plans, and validating with a peer agent. Useful before coding for planning, design approach, or scoping.
Guides design validation through collaborative dialogue before coding begins. Use when creating features, building components, or modifying behavior to prevent wasted work.