Use after implementation to analyze drift, update documentation, evolve evaluation, and close a completed epic.
Use when starting or resuming a full development lifecycle for a feature or explicit epic.
Use when you have a spec or requirements for a multi-step task, before touching code.
Use when working with the Fiddle portable skills library, choosing lifecycle skills, or adapting Fiddle instructions across Claude, Codex, and Pi harnesses.
Use after all per-task evaluations complete — assesses cross-domain integration and creates remediation beans
Use when a single task bean needs implementation and evaluation — called by fiddle:develop, not directly.
Use when implementing an epic's task beans through the evaluator loop — after plan and beans exist
Use before creative work or behavior changes to clarify intent, explore tradeoffs, and produce an approved design.