Poteto mode

Recover after compaction or truncation

After a known compaction, context summary, or truncation notice, read this entry on its own before the next governed action. Restore the active playbook path and current step from the existing worklist, task record, or resume note. Then read and apply task triggers, the active playbook, and its required current-step references one governing file per outer tool response, or in verified bounded chunks. Require complete returned governing guidance before any governed action. If a runtime or tool return is shortened or reports truncation, read the missing content before continuing. A named read command, successful process exit, or remembered summary does not establish complete returned content. Reconcile completed work, evidence, phase, outstanding gates, and existing grants there. Continue the same task without a new human pause or repeated completed work. Preserve required watcher and verification checks. A remembered green summary does not replace them.

If governing guidance is unavailable, report the exact missing file. Withhold only actions whose prerequisites you cannot establish. Read the runtime retention evidence when runtime retention or restoration affects a decision. A file within the repository byte budget does not guarantee runtime retention.

Playbooks

Open a worklist whose first items are the matched playbook's opening prose and then its steps, copied verbatim, before any task-specific items. Use the pstack-harness skill to select the best native carrier from live capability descriptions, without depending on a product-specific tool name. A step you choose not to do stays in the list with a one-line skipped: <reason>. Match the task to a playbook below, open its file, and copy its steps verbatim. Copy the prose before step 1 as the first item, because it carries rules the steps assume. Record the matched playbook path with that item, keeping the copied prose and steps verbatim; the in-progress item supplies the current step.

For a large or cross-cutting effort (a migration across many call sites, an ambitious multi-part change), or work the user steps away from to trust later, use the figure-it-out skill even when a narrower playbook like Feature fits. Use the figure-it-out skill whenever no bundled playbook fits. It designs a bespoke, rigorous playbook for the task. A standing project-scale program (multi-day, many stacked PRs, a fleet of subagents under one coordinator) routes to Orchestrate instead. figure-it-out designs one bespoke run, orchestrate runs the program.