peel/fiddle

deliver

Use after implementation to analyze drift, update documentation, evolve evaluation, and close a completed epic.

Langue du texte source : anglais

orchestrate

Use when starting or resuming a full development lifecycle for a feature or explicit epic.

Langue du texte source : anglais

write-plan

Use when you have a spec or requirements for a multi-step task, before touching code.

Langue du texte source : anglais

using-fiddle

Use when working with the Fiddle portable skills library, choosing lifecycle skills, or adapting Fiddle instructions across Claude, Codex, and Pi harnesses.

Langue du texte source : anglais

develop-holistic

Use after all per-task evaluations complete — assesses cross-domain integration and creates remediation beans

Langue du texte source : anglais

develop-loop

Use when a single task bean needs implementation and evaluation — called by fiddle:develop, not directly.

Langue du texte source : anglais

develop

Use when implementing an epic's task beans through the evaluator loop — after plan and beans exist

Langue du texte source : anglais

brainstorm

Use before creative work or behavior changes to clarify intent, explore tradeoffs, and produce an approved design.

Langue du texte source : anglais

challenge

Use when a plan or design needs assumptions, constraints, and decision branches resolved before progressing.

Langue du texte source : anglais

define

Use after discovery to turn confirmed scope into an approved design, implementation plan, and ready-to-execute beans.

Langue du texte source : anglais

adr

Use when recording a consequential technical decision; captures context, the chosen option, and consequences in a new architecture decision record.

Langue du texte source : anglais

backlog

Use when capturing an idea, technical debt, or observation that is not ready for a planned bean.

Langue du texte source : anglais

define-beans

Use when sizing a planned task into task or feature beans based on its test-driven implementation complexity.

Langue du texte source : anglais

deliver-docs

Use after a completed epic or significant change to update technical docs and capture resulting decisions or debt.

Langue du texte source : anglais

discover-docs

Use when bootstrapping or reviewing project documentation through concise Socratic discovery and targeted updates.

Langue du texte source : anglais

discover

Use before defining a feature or epic to gather context, research options, and challenge scope assumptions.

Langue du texte source : anglais

feedback

Use when recording a user signal with its context, observation, implication, and confidence for future analysis.

Langue du texte source : anglais

panel

Use when evaluating architectural approaches or design decisions — runs structured multi-model adversarial analysis with cross-review and synthesis

Langue du texte source : anglais

debug

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Langue du texte source : anglais

finish-branch

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Langue du texte source : anglais

init

Use when starting fiddle on a new project — scaffolds docs, orchestrate.json, and beans from templates.

Langue du texte source : anglais

insights

Use when preparing for a planning cycle or when feedback has accumulated — synthesizes structured feedback entries into persona files and insight summaries that discover and brainstorm phases consume.

Langue du texte source : anglais

tdd

Use when implementing any feature or bugfix, before writing implementation code

Langue du texte source : anglais

worktrees

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

Langue du texte source : anglais

verify

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

Langue du texte source : anglais

quickfix

Use when the user wants a quick one-shot implementation of a small, unambiguous task — skips full orchestrate in favor of clarify, implement, PR

Langue du texte source : anglais

evaluate

Use when scoring an implementation against its task spec — dispatched by develop-loop, not directly

Langue du texte source : anglais

runtime-evidence

Use when an evaluator needs to interact with a running application before scoring dimensions

Langue du texte source : anglais