pstack: operate PDCA harness when present

pstack/skills/poteto-mode/SKILL.md

@@ -32,6 +32,7 @@ Remaining triggers:
 - Bugbot or the agentic security review commented → skeptical posture. They catch real bugs and also file non-issues and nitpicks, so assess each on its merits and dismiss noise with a concrete reason instead of churning code. Triage fix / dismiss / ask via the built-in **babysit** skill.
 - Broken skill mid-task → fix it in its own PR. Don't block. Don't silently work around it.
 - Long, autonomous, or multi-phase work, or any task the user steps away from to review later ("going to bed", "trust it when i'm back", "/loop until X") → a decision trail via the **show-me-your-work** skill. Commit it when stakes need an auditable record; keep it local otherwise.
+- Workspace has a PDCA harness (`docs/OPERATOR.md`, `docs/HARNESS.md`, or `harness/`) → read `references/pdca-harness.md`, then the repo operator contract. You are the preferred Orchestrator. Advance Plan/Do only via `/intake-next` and `/build-next`. Do not invent board state from chat. Do not `/loop /poteto-mode` as a station. Delivery / pre-implementation / validate-upstream asks → playbook **Operate PDCA harness**.
 
 ## Principles
 
@@ -132,4 +133,5 @@ A large or cross-cutting effort (a migration across many call sites, an ambitiou
 - **Session pickup.** Resuming or taking over a prior agent's in-flight work from a transcript, cloud-agent URL, or pushed branch. `playbooks/session-pickup.md`.
 - **Pause safely.** Suspending in-flight work cleanly so it can be resumed, on an explicit pause, going offline, a Cursor restart, or imminent context compaction. The complement to Session pickup. Full steps: `playbooks/pause-safely.md`.
 - **Multi-phase or multi-PR plan.** Work that spans phases or stacked PRs. `playbooks/multi-phase-plan.md`.
+- **Operate PDCA harness.** Repo has `docs/OPERATOR.md` / `docs/HARNESS.md` / `harness/` and the user wants delivery advanced, validated, or operated. `playbooks/operate-pdca-harness.md`.
 - **Opening a PR.** Invoked at the end of every other playbook. `playbooks/opening-a-pr.md`.

pstack/skills/poteto-mode/playbooks/operate-pdca-harness.md

@@ -0,0 +1,14 @@
+### Operate PDCA harness
+
+**You are Orchestrator.** The shelf is authority. Load the kit contract; do not invent board state.
+
+Triggered when the workspace has a PDCA harness (`docs/OPERATOR.md`, `docs/HARNESS.md`, or `harness/`) and the user wants delivery advanced, validated, or explained as an operator.
+
+1. Read `references/pdca-harness.md`, then `docs/OPERATOR.md` (or `docs/HARNESS.md` / `harness/tree/…` equivalents).
+2. Throughput checkpoint stays one line: `throughput checkpoint: n/a, harness operator` unless a Feature/Bug fix playbook also applies to product code.
+3. Match the user ask to an **alias** in `docs/OPERATOR.md` (`plan`, `validate`/`pre-do`, `pin wi-N`, `build`/`do`, `status`). Expand to that file’s **Full commands** block. Echo the expansion in `action:`.
+4. Run one tick of the expanded station skill (or print the full `/loop` text if they only asked what to run). Spawn Planner / Gate Reviewer / Implementer / Reviewer as `poteto-agent` per the harness roles doc.
+5. Emit the tick status line the skill requires. Stop on the published signals.
+6. Apply **unslop** to the reply.
+
+No nested `/loop` from inside a tick. Opening a PR only when a station or product Feature asks for it.

pstack/skills/poteto-mode/references/pdca-harness.md

@@ -0,0 +1,43 @@
+# PDCA harness detection
+
+When the workspace has a PDCA harness, poteto-mode is the **preferred Orchestrator**. The harness kit owns the protocol. This file does not duplicate it.
+
+## Detect
+
+Any of these means a harness is present:
+
+- `docs/OPERATOR.md`
+- `docs/HARNESS.md`
+- `harness/tree/docs/OPERATOR.md` or `harness/tree/docs/HARNESS.md`
+- `.cursor/skills/intake-next/SKILL.md` and `.cursor/skills/build-next/SKILL.md`
+
+Prefer `docs/OPERATOR.md` (or the `harness/tree/…` equivalent). Fall back to `docs/HARNESS.md`.
+
+## Load
+
+1. Read the operator contract (OPERATOR, else HARNESS).
+2. Do not invent Plan/Do board moves from chat.
+3. Advance only via station skills: `/intake-next`, `/build-next`, pin `/build-next wi-N`.
+4. Before HITL yes, expect `python3 scripts/gate_check.py --gate <gate_id>` (exit 1 → Planner, exit 2 → Gate Reviewer, exit 0 → human yes/no).
+5. Spawn role agents with `subagent_type: "poteto-agent"` per the harness `docs/AGENT-ROLES.md`.
+6. Pre-implementation stop is `AWAITING_PIN`. Never pin from intake. Never treat `/loop /poteto-mode` as a station.
+
+## Aliases
+
+If the user says a short name, expand using the **Aliases** table in `docs/OPERATOR.md`, then run the matching **Full commands** block. Echo the expansion in the tick `action:`.
+
+| Alias | Station |
+| --- | --- |
+| `plan` / `intake` | Plan loop |
+| `validate` / `pre-do` | Pre-Do validation loop |
+| `pin wi-N` | `/build-next wi-N` |
+| `build` / `do` | Do loop |
+| `status` | Read-only shelf report |
+
+Synonyms (“validate upstream”, “run until pre-implementation”, “advance plan”) use the same rows. Do not invent new Cursor slash skills for aliases.
+
+## Route phrases
+
+If the user asks to run delivery or names an alias without a station slash command, expand via OPERATOR.md and run (or print) that full command. Do not freestyle a parallel backlog.
+
+If only `/poteto-mode` is attached with no station and the request is clearly delivery, load OPERATOR and either expand `plan`/`validate` or name the alias table. Do not freestyle a parallel backlog.