From 5a1e13dc395e209a2b80b016f826c4d08c64c72b Mon Sep 17 00:00:00 2001
From: Leo <5024409+0xTenable@users.noreply.github.com>
Date: Mon, 14 Sep 2026 20:19:23 -0700
Subject: [PATCH] poteto-mode: fetch latest main before starting work or
 spawning agents

Add a non-negotiable trigger so sessions and spawned workers start from
origin/main. Cloud agents and worktree workers inherit the checkout or
base branch they spawn from, so a stale local base hands every worker a
stale start and surfaces later as avoidable conflicts.

Written with Devin.
---
 pstack/skills/poteto-mode/SKILL.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/pstack/skills/poteto-mode/SKILL.md b/pstack/skills/poteto-mode/SKILL.md
index 7559dea0..d7651bfa 100644
--- a/pstack/skills/poteto-mode/SKILL.md
+++ b/pstack/skills/poteto-mode/SKILL.md
@@ -16,6 +16,7 @@ The Principles section below grounds every trigger. In your reply, name each pri
 
 Remaining triggers:
 
+- Starting development or spawning code-writing agents → `git fetch origin main` first, then branch or rebase onto it so work starts from latest main. A worker inherits the checkout or base branch it spawns from; a stale base hands every worker a stale start.
 - Nontrivial change, architecture decision, or "are we sure?" → the **how** skill.
 - About to `AskQuestion` on a "which approach", "how should I", or "what should this do" fork → classify it before you ask. If the answer is a fact you could observe by running something (behavior, timing, layout, output, perf, even whether an eval separates), it is not the human's to answer. Sketch it via the Prototype playbook (`playbooks/prototype.md`) and let the result decide. If the task is a read-only Investigation whose deliverable is a cited answer, stay in it and answer from the evidence rather than building a sketch. Reserve the question for a genuine product or preference call no experiment can settle.
 - Any code → name the data shape first, and choose its organizing structure per **principle-model-the-domain**.