EthanYoQ · Oct 24, 2026 · cursor · Oct 24, 2026 · cursor · Oct 24, 2026
diff --git a/harness/pstack/claude-code/agents/poteto-agent.md b/harness/pstack/claude-code/agents/poteto-agent.md
diff --git a/harness/pstack/claude-code/docs/harness/claude-code.md b/harness/pstack/claude-code/docs/harness/claude-code.md
diff --git a/pstack/agents/poteto-agent.md b/pstack/agents/poteto-agent.md
@@ -7,3 +7,5 @@ is_background: true
 # Poteto subagent
 
 You are operating as poteto-mode's full agent style. The chat that receives `/poteto-mode` owns the playbook, the todo list, and every Task spawn. You are one of its delegates. Read the `poteto-mode` skill's `SKILL.md` in full before doing any work, including its inline Principles index. Use the absolute path your parent gave you. With no path, before any other work, search `~/.cursor/plugins/` for a file whose path ends in `skills/poteto-mode/SKILL.md`. If more than one file matches, use the copy whose `.cursor-plugin/plugin.json` has the highest `version`. Your skill catalog hides this skill, so a missing catalog entry does not mean pstack is absent. If no such file exists, stop and tell your parent. Navigate to a leaf `principle-*` skill whenever you apply that principle.
+
+When your brief hands you playbook steps, open a todolist of them before your first edit. A step that needs a Task spawn you cannot make, or were told not to make, goes back to your parent. List it under "Returned to parent" in your reply instead of skipping it. End your reply with the skill, playbook, and principle files you read.
diff --git a/pstack/docs/harness/claude-code.md b/pstack/docs/harness/claude-code.md
@@ -8,7 +8,7 @@ pstack skills use Cursor names. In Claude Code, read this file once per session,
 | --- | --- |
 | `Task` | `Agent` |
 | `AskQuestion` | `AskUserQuestion`. In `-p` mode it is absent, so ask in plain text. |
-| Open a todolist | Use `TodoWrite` if the session offers it. Otherwise keep the list in your reply and update it at each phase. |
+| Open a todolist | Use `TodoWrite` if the session offers it. Otherwise write the list to a Markdown file before your first edit, mark each item done or `skip: <reason>` as you go, and name the file in your reply. A background subagent's reply reaches its parent only when it finishes, so a list kept in the reply is no checkpoint. |
 | Run another pstack skill (`/name` or "the **name** skill") | `Read` `<pstack>/skills/<name>/SKILL.md` and follow it. The `Skill` tool refuses most pstack skills. When you tell the user to type it, write `/pstack:<name>`. |
 | `Grep`, `Glob` | `Bash` with `rg` when the session has no `Grep` or `Glob`. |
Original file line number	Diff line number	Diff line change
Expand Up		@@ -7,3 +7,5 @@ is_background: true
		# Poteto subagent

		You are operating as poteto-mode's full agent style. The chat that receives `/poteto-mode` owns the playbook, the todo list, and every Task spawn. You are one of its delegates. Read the `poteto-mode` skill's `SKILL.md` in full before doing any work, including its inline Principles index. Use the absolute path your parent gave you. With no path, before any other work, search `~/.cursor/plugins/` for a file whose path ends in `skills/poteto-mode/SKILL.md`. If more than one file matches, use the copy whose `.cursor-plugin/plugin.json` has the highest `version`. Your skill catalog hides this skill, so a missing catalog entry does not mean pstack is absent. If no such file exists, stop and tell your parent. Navigate to a leaf `principle-*` skill whenever you apply that principle.

		When your brief hands you playbook steps, open a todolist of them before your first edit. A step that needs a Task spawn you cannot make, or were told not to make, goes back to your parent. List it under "Returned to parent" in your reply instead of skipping it. End your reply with the skill, playbook, and principle files you read.
cursor Bot Oct 24, 2026 Copy link Copy Markdown Choose a reason for hiding this comment The reason will be displayed to describe this comment to others. Learn more. Return rule catches implementation steps Medium Severity · Logic Bug The new return rule sends any playbook step that needs a `Task` spawn the delegate cannot make, or was told not to make, back to the parent. Implementation steps are written as "delegate to a subagent," so they match. Feature is the only playbook that tells a no-spawn delegate to own the diff. ^{Reviewed by Cursor Bugbot for commit fdc0a9d. Configure here.}