Recipe Memory

Use this Skill only when automatic draft-memory or active-tool review needs diagnosis or bounded recovery. Normal agents must not spawn, register, specialize, or invoke recipe-memory/draft-review or recipe-memory/tool-review; they are package-owned internal reviewer components.

Diagnose first

inspect target=recipes view=reviews
inspect target=runtime view=triage

Use the review view to distinguish draft and tool scope, current phase, failed stage, bounded error, preserved transaction evidence, and the recorded next action. Use runtime triage only when the reviewer Run itself needs Run-level diagnosis. Follow actors for generic Inspect, Run, and Control semantics.

Recovery Controls

Use runtime Controls only when the review evidence names the matching recovery action:

message target=runtime action=review.retry input={"scope":"draft"}
message target=runtime action=review.retry input={"scope":"tool"}
message target=runtime action=review.reset input={"scope":"draft"}
message target=runtime action=review.reset input={"scope":"tool"}

• review.retry resumes the selected failed review scope while preserving authenticated transaction recovery.
• review.reset clears disposable failure state only. It must reject evidence that requires roll-forward recovery.
• Re-inspect view=reviews after one recovery Control; do not loop retries or resets without changed evidence.

Stop rules

Stop when the phase is healthy or idle, the requested scope does not match the failure, recovery evidence requires deterministic roll-forward, or the reported next action is not retry/reset. Never edit review state, lineage, journals, quarantine, drafts, or persisted Recipes directly. Never bypass automatic review by running its internal Recipes as ordinary capabilities.