dsh-super-code 0.3.11 → 0.4.0

package/builtin/skills/pstack/dsh/docs/guide/10-recipes-and-pitfalls.md

@@ -0,0 +1,184 @@
+> Upstream background reference. For executable DSH procedures and host capabilities, use [PStack on DSH](../../DSH.md) and the adapted Skills. Installation instructions for other hosts below do not configure DSH.
+
+# Recipes and pitfalls
+
+Prompts worth copying, then the mistakes everyone makes once. Swap in your own paths and finish conditions. The recipes are deliberately informal. That's how they get typed in practice, and the skills read intent fine.
+
+![She tastes a finished dish while robots cook from a recipe box, with pinned cards reading /how, /tdd, and /loop above the counter.](./images/recipes.jpg)
+
+## Understand an unfamiliar subsystem
+
+```text
+use /how first to understand how this initialization works. then use /why to figure out why it broke recently.
+```
+
+Mechanics first, history second. Each skill's report tells you which sources it searched, so you know what the answer is grounded in.
+
+## Restate a noisy report before touching code
+
+```text
+/poteto-mode read this thread. restate the underlying issue in your own words, in plain english. don't change any code yet.
+```
+
+A misreading shows up in the restatement, where it costs one message to correct. Keep your own theory to yourself until the agent has stated its own. `/in-your-own-words` asks for the restatement alone, with no playbook.
+
+## Sharpen a prompt before you send it
+
+```text
+/sharpen write the onboarding doc for the new billing service.
+```
+
+The agent names what an expert would do that you didn't ask for, the raw material they'd start from, their methods and tools, and an outside check that the result is right. It hands back your prompt rewritten to ask for that and doesn't do the task. Send the rewrite when it reads right.
+
+## Prototype before you pick
+
+```text
+/poteto-mode prototype a few options for the settings layout. put them behind a switcher and send me screenshots of each.
+```
+
+You pick from things that run, not from descriptions. The agent answers its own layout and timing questions along the way.
+
+## Turn a settled design into a plan
+
+```text
+/poteto-mode turn this design into a plan. small verifiable PRs, each with its own proof.
+```
+
+Ask only after the design settles. The plan is the deliverable, and it names the playbook that will execute it.
+
+## Get a second opinion on a design
+
+```text
+ask /arena for a second opinion on this thread and our approach
+```
+
+Your current design becomes one candidate among several, and the synthesis tells you whether the panel found something better or confirmed what you had. It costs little next to a design that is expensive to reverse.
+
+## Check independent slices in parallel
+
+```text
+/swarm check every package under packages/ against its check.sh. one worker per package. one report.
+```
+
+Each worker owns one package. The parent waits for every slice and returns one `PASS`, `ISSUES`, or `BLOCKED` report instead of raw worker dumps.
+
+## Review a branch skeptically
+
+```text
+/interrogate the whole branch, but skeptically. don't change anything yet. no nitpicks unless it's an actual bug or regression in behavior.
+```
+
+The qualifiers do real work. "don't change anything yet" keeps it read-only, and the nitpick rule pre-filters the noise so the verified findings are worth your time.
+
+## Fix a bug through a failing test
+
+```text
+/poteto-mode repro the duplicate write first. if there's a cheap test path, /tdd it. then fix and rerun.
+```
+
+"if there's a cheap test path" matters. Forcing a test through brittle mocks proves less than running the real command, and the playbook is allowed to say so.
+
+## Repro and fix a report with proof
+
+```text
+/poteto-mode repro this with /verify-<app>. if it repros on main, fix it and show me a video as proof.
+```
+
+"if it repros on main" lets the run stop early when the bug is already gone. The video lets you check the fix before you read the diff.
+
+## Prove a property tests rarely reach
+
+```text
+/create-formal-verification-skill the retry queue. a message must never be delivered twice.
+```
+
+You get one property checked in every case within a stated scope, a counterexample in your code's terms if the code already breaks it, and a project skill the next agent runs on any change to that code.
+
+## Vet a number before you post it
+
+```text
+/benchmark-checklist vet this 40% speedup before it goes in the pr description
+```
+
+You get faster, slower, no measurable difference, or inconclusive, with the run count, the range, and what limits the number.
+
+## Stop correcting the same mistake
+
+```text
+/correct agents keep adding new config flags without registering them in the schema
+```
+
+The fix lands in the repo as architecture, a type, a lint, or a test, so the next agent can't make the mistake.
+
+## Ask how without starting the work
+
+```text
+/poteto-help how do i get poteto-mode to stay on every turn?
+```
+
+You get an answer, a prompt to send, and a link to the source. Nothing runs until you send that prompt.
+
+## Keep a run honest while you're away
+
+```text
+im going to bed, keep going autonomously until every fixture passes. do not stop. keep a decision log i can audit in the morning.
+```
+
+The full contract is on the [overnight page](./07-overnight.md). The short form works once the task and finish condition are already in the conversation.
+
+## Redirect a drifting run
+
+Steering prompts are one line:
+
+```text
+i said the goal is to repro. i did not ask for a fix yet.
+```
+
+```text
+apply prove it works. show me the real output, not the build log.
+```
+
+```text
+/unslop that, no emdashes
+```
+
+You rarely need more words. You need the right name, and [the principles page](./08-principles.md) is the vocabulary.
+
+## Get the reply in plain words
+
+```text
+/bro
+```
+
+That's the whole prompt. [`/bro`](../../skills/bro/SKILL.md) restates the last message like one human talking to another, no jargon, shorter. Use it when a reply is technically thorough and you still don't know what it said.
+
+## Catch up on a chat you left running
+
+```text
+/ketchup
+```
+
+[`/ketchup`](../../skills/ketchup/SKILL.md) tells you in plain words what changed since your last message, then lists each call waiting on you with its pick, evidence, and risk. It changes nothing while it reports.
+
+To watch the catch-up instead, run [`/ketchup-video`](../../skills/ketchup-video/SKILL.md). It shows what happened in a short subtitled video of slides, and lists the calls waiting on you as text under it.
+
+## The pitfalls
+
+- **Enumerating skills in the prompt.** "use /how then /architect then /arena" reorders steps the playbook already sequences. State the goal and constraints. Name a skill only to override a default.
+- **A vague finish condition.** "make it better" gives `/loop` nothing to check. Give a command or artifact that can pass or fail.
+- **Leading with your theory of the cause.** The agent searches wherever you pointed. Ask it to restate the problem first, then share your hunch.
+- **Taking the first design.** One attempt locks in the first shape the model thought of. Ask for prototypes or `/architect` and pick from evidence.
+- **Polishing an abstract plan.** Adversarial review of a plan with no code behind it invents risks that will never happen. Settle the open questions with prototypes, then review what got built.
+- **Parallel agents in one worktree.** They overwrite each other, and nobody can tell which agent changed what. Run them as cloud agents, or say "own worktree per attempt".
+- **Looping before you trust the loop.** A loop that can't verify its own work only makes unchecked work faster. Get the verification skill working first.
+- **Trusting an unvetted number.** A warm cache or a skipped code path can fake a speedup. Run `/benchmark-checklist` before the number goes anywhere.
+- **Correcting the same mistake by hand.** A correction in chat helps one run. `/correct` fixes the repo so no later run repeats it.
+- **Using `/arena` for coverage.** `/arena` repeats one design or code brief, then picks a base and grafts the best parts. `/swarm` partitions slices or declared race arms and aggregates one report.
+- **Accepting every review comment.** Bots and humans both file real catches and noise in one list. `/interrogate` keeps only the findings a rerun proves and lists what it dropped and why, and you can override either way.
+- **Treating `auto` as a model slug.** `auto` and `inherit-parent` mean "omit the model field so the subagent inherits the parent chat model." [Setup](./01-setup.md) covers the roles.
+- **Reporting success off a green build.** A build proves it compiles. Ask for the real command, flow, stored value, or profile, and expect the evidence in the reply.
+- **Writing a `SKILL.md` freehand.** Route it through the [Authoring or modifying a skill playbook](../../skills/poteto-mode/playbooks/authoring-a-skill.md) so validation and review happen.
+
+That's the guide. If you skipped ahead, go back to [setup](./01-setup.md) and run one real task. The habits stick from use, not from reading.
+
+Back to the [guide index](./README.md).

package/builtin/skills/pstack/dsh/docs/guide/README.md

@@ -0,0 +1,40 @@
+> Upstream background reference. For executable DSH procedures and host capabilities, use [PStack on DSH](../../DSH.md) and the adapted Skills. Installation instructions for other hosts below do not configure DSH.
+
+# The pstack guide
+
+pstack works best when you stop micromanaging the agent. You describe what you want and how you'll know it's done. `/poteto-mode` picks the playbook, runs the other skills as the steps need them, and shows you the evidence. This guide teaches that habit with realistic prompts.
+
+Here's what you'll learn:
+
+1. [Set up pstack](./01-setup.md). Install the plugin and pick your models.
+2. [Route work through `/poteto-mode`](./02-poteto-mode.md). Give it a goal and watch it pick a playbook.
+3. [Understand the code](./03-understand.md). A read-only investigation, then `/how`, `/why`, `/teach`, and `/recall` before you edit anything.
+4. [Design the change](./04-design.md). `/architect`, `/arena`, `/swarm`, `/interrogate`, prototypes, and plans before code locks in a shape.
+5. [Build and clean the change](./05-build-and-clean.md). The build playbooks, `/tdd`, `/unslop`, and `/no-comments`.
+6. [Verify and ship](./06-verify-and-ship.md). Prove behavior on the real app, formally verify what tests rarely reach, vet numbers with `/benchmark-checklist`, then open a focused PR and drive it to merged.
+7. [Run work while you sleep](./07-overnight.md). Trust before loops, an overnight contract, a decision log you can audit, and Projects and automations that scale past one agent.
+8. [Steer with principle names](./08-principles.md). The 24 names that redirect an agent mid-task.
+9. [Make it yours](./09-make-it-yours.md). Your own mode, `/correct` for repeated mistakes, and how to test a skill change.
+10. [Recipes and pitfalls](./10-recipes-and-pitfalls.md). Prompts to copy and mistakes to skip.
+
+Read the pages in order the first time. After that, each page stands alone.
+
+When you're stuck, or can't tell which skill fits, type [`/poteto-help`](../../skills/poteto-help/SKILL.md) with your question:
+
+```text
+/poteto-help which skill should i use to review this branch?
+```
+
+It answers, hands you a prompt to send, and links the skill or guide page the answer came from. It doesn't start the work, because a pstack run spends real tokens, so you send the prompt when you're ready. It runs only when you type it.
+
+## If you only remember one thing
+
+Give the agent a goal and a way to check it, in your own words:
+
+```text
+/poteto-mode the export writes duplicate rows when a retry lands mid-run. repro first, then fix and verify.
+```
+
+You don't need to name a playbook or list skills. "repro first" and a checkable outcome are all the routing signal `/poteto-mode` needs. It matches the Bug fix playbook, copies the steps into a todo list, and calls the right skills as each step fires.
+
+Next: [Set up pstack](./01-setup.md).

package/builtin/skills/pstack/dsh/docs/harness/claude-code.md

@@ -0,0 +1,69 @@
+> Upstream background reference. For executable DSH procedures and host capabilities, use [PStack on DSH](../../DSH.md) and the adapted Skills. Installation instructions for other hosts below do not configure DSH.
+
+# pstack in Claude Code
+
+pstack skills use Cursor names. In Claude Code, read this file once per session, then map each Cursor name in a skill with the tables below. `<pstack>` means the folder that holds `skills/` and `docs/`. If a Cursor field has no row, drop it and say so. Never pass a field or value the tool schema rejects.
+
+## Tools
+
+| Cursor | Claude Code |
+| --- | --- |
+| `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. |
+| 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`. |
+
+## Subagent fields
+
+| Cursor | Claude Code |
+| --- | --- |
+| `subagent_type: generalPurpose` | `subagent_type: "general-purpose"` |
+| `poteto-agent`, `comment-sicko` | `pstack:poteto-agent`, `pstack:comment-sicko` |
+| `readonly: true` | `subagent_type: "Explore"`. It keeps `Bash`, so the brief also says "do not edit files", and you check `git status` afterward. |
+| `readonly: false` | `general-purpose`. It keeps the session's MCP servers. |
+| `environment: "cloud"` | `isolation: "worktree"`. Name the branch or commit the worker checks out. |
+| `environment: "local"` | Omit. |
+| `cloud_base_branch: <b>` | Tell the worker to check out `<b>` first. |
+| `run_in_background: true` | Omit. Subagents run in the background by default and notify you when they finish. |
+| `resume` | Spawn a new agent and paste the earlier result into its brief. |
+| `file_attachments` | List the paths in the brief. |
+
+## Models
+
+| Cursor | Claude Code |
+| --- | --- |
+| `claude-<family>-<version>-<effort>[-fast]`, such as `claude-opus-5-5-xhigh` | `model: "opus"` and `effort: "xhigh"`. `model` takes only `opus`, `sonnet`, `haiku`, `fable`. Drop `-fast`. |
+| A `grok-*`, `gpt-*`, or other non-Claude slug | Omit `model` so the agent runs on the session model, and say so. |
+| `auto` or `inherit-parent` | Omit `model`. |
+| The `pstack-models.mdc` rule, `~/.cursor/rules/pstack-models.mdc` | `~/.claude/rules/pstack-models.md`. Claude Code loads it into every new session, so its role lines are already in context. If they are not, read the file. If the file or the role's line is missing, use the skill's default slug. |
+| A role value `<model> <effort>`, such as `opus high` | `model: "opus"` and `effort: "high"`. |
+
+## setup-pstack
+
+Claude Code loads every `.md` file in `~/.claude/rules/` into each new session, so `setup-pstack` writes its rule there. Follow its steps with these changes:
+
+- Detect. The detected models are the `model` values that the `Agent` tool schema lists, each with an effort from its `effort` values. Write a real model as `<model> <effort>`, such as `opus xhigh`. The effort is the last token, so the budget step works as written.
+- Defaults. Map each default slug with the rows above: `claude-opus-5-5-xhigh` is `opus xhigh`, and `grok-4.7-xhigh-fast` is `inherit-parent`.
+- Write. Write `~/.claude/rules/pstack-models.md` with no frontmatter, then the comment lines, the `# budget` line, and one line per role from step 5. Overwrite the whole file. Never put the role lines in `CLAUDE.md` or `AGENTS.md`.
+
+## Paths
+
+| Cursor | Claude Code |
+| --- | --- |
+| `.cursor/skills/`, `~/.cursor/skills/` | `.claude/skills/`, `~/.claude/skills/` |
+| `~/.cursor/plugins/`, `.cursor-plugin/plugin.json` | `~/.claude/plugins/`, `.claude-plugin/plugin.json` |
+| `.cursor/rules/*.mdc`, always-applied rules | `CLAUDE.md`, or `AGENTS.md` when no `CLAUDE.md` exists. Claude Code never reads `.mdc` files. The model rule is the exception. See Models. |
+| `https://github.com/cursor/plugins/blob/main/pstack/<path>` | `<pstack>/<path>` when that file exists. The plugin ships the skills, `docs/guide/`, and `README.md`. Read the local copy and never fetch it. Give the user the URL when they need a link. |
+| Transcripts in `~/.cursor/projects/<slug>/agent-transcripts/` | `~/.claude/projects/<slug>/<session>.jsonl`. The slug is the workspace path with each `/` and `.` changed to `-`, so `/Users/you/proj` is `-Users-you-proj`. The newest `.jsonl` directly in that folder is the current session. Its `<session>/subagents/` folder holds subagent transcripts. Read only this workspace's folder. |
+
+## Cursor-only features
+
+Claude Code has no Cursor Automations, Bugbot, Cursor cloud agents, or built-in PR tool. When a step needs one, put one line in your reply, `Skipped in Claude Code: <step>. <reason>.`, then go on to the next step. Do not stop, ask, or retry. When a later step needs what the skipped step made, such as a URL or a key, leave a placeholder and name it in the line.
+
+| Cursor | Claude Code |
+| --- | --- |
+| Cursor Automations: routines, `update_state` routine calls, `api2.cursor.sh/automations` webhooks, routine wakes, and `SendToUser` secret requests | Skip with the line. |
+| Bugbot | Bugbot comments on a GitHub PR are ordinary review threads, so triage them with the forge command that the step gives. Skip a step that starts, waits for, or configures Bugbot when the PR has no Bugbot check or comment. |
+| Cursor cloud agents | `environment: "cloud"` maps to a worktree, as in Subagent fields. Skip a step that needs the cloud agent itself, such as its dashboard status or its own machine. |
+| A built-in PR tool | Use the forge command that the step gives, such as `gh pr create`. That is not a skip, so write no line. |

package/builtin/skills/pstack/dsh/scripts/capture.mjs

@@ -0,0 +1,80 @@
+#!/usr/bin/env node
+import { mkdir, mkdtemp, open, readFile, realpath, writeFile } from 'node:fs/promises'
+import { createReadStream } from 'node:fs'
+import { createHash } from 'node:crypto'
+import { spawn } from 'node:child_process'
+import { join, relative, resolve, isAbsolute } from 'node:path'
+import { fileURLToPath } from 'node:url'
+
+async function inside(root, path) {
+  const actual = await realpath(path), local = relative(root, actual)
+  if (local === '..' || local.startsWith('..' + (process.platform === 'win32' ? '\\' : '/')) || isAbsolute(local)) throw new Error('Evidence path is outside the workspace')
+  return actual
+}
+async function digest(path) {
+  const hash = createHash('sha256'); let bytes = 0
+  for await (const chunk of createReadStream(path)) { hash.update(chunk); bytes += chunk.length }
+  return { bytes, sha256: hash.digest('hex') }
+}
+const save = (path, value) => writeFile(path, JSON.stringify(value, null, 2) + '\n', { flag: 'wx', mode: 0o600 })
+
+/** Execute argv once, without a shell, and retain evidence in a unique project directory. */
+export async function captureCommand(argv, cwd = process.cwd()) {
+  // Own the submitted arguments before I/O; spreading also exposes sparse holes.
+  if (Array.isArray(argv)) argv = [...argv]
+  if (!Array.isArray(argv) || !argv.length || !argv[0] || argv.some(arg => typeof arg !== 'string' || arg.includes('\0'))) throw new TypeError('Expected nonempty string argv')
+  const root = await realpath(cwd), scratch = join(root, 'scratch')
+  await mkdir(scratch, { recursive: true })
+  await inside(root, scratch)
+  const directory = await mkdtemp(join(scratch, 'pstack-evidence-')), temporary = join(directory, 'tmp')
+  await mkdir(temporary, { mode: 0o700 })
+  await save(join(directory, 'command.json'), { version: 1, cwd: root, argv })
+  const stdout = await open(join(directory, 'stdout.txt'), 'wx', 0o600)
+  const stderr = await open(join(directory, 'stderr.txt'), 'wx', 0o600)
+  let outcome
+  try {
+    outcome = await new Promise((resolveRun, reject) => {
+      const child = spawn(argv[0], argv.slice(1), {
+        cwd: root, env: { ...process.env, TMPDIR: temporary, TMP: temporary, TEMP: temporary },
+        stdio: ['ignore', stdout.fd, stderr.fd], windowsHide: true,
+      })
+      let failure
+      const interrupt = signal => { child.kill(signal) }
+      const onTerm = () => interrupt('SIGTERM'), onInt = () => interrupt('SIGINT')
+      process.on('SIGTERM', onTerm); process.on('SIGINT', onInt)
+      child.once('error', error => { failure = { kind: 'spawn-error', code: error.code ?? 'UNKNOWN', message: error.message } })
+      child.once('close', (code, signal) => {
+        process.removeListener('SIGTERM', onTerm); process.removeListener('SIGINT', onInt)
+        if (failure) resolveRun(failure)
+        else if (signal) resolveRun({ kind: 'signal', signal })
+        else if (Number.isInteger(code)) resolveRun({ kind: 'exit', code })
+        else reject(new Error('Command ended without an exit status'))
+      })
+    })
+  } finally { await stdout.close(); await stderr.close() }
+  const result = { version: 1, outcome, command: await digest(join(directory, 'command.json')), stdout: await digest(join(directory, 'stdout.txt')), stderr: await digest(join(directory, 'stderr.txt')) }
+  await save(join(directory, 'result.json'), result)
+  return { directory: relative(root, directory), ...result }
+}
+
+/** Verify retained bytes; command success and truth of an audit claim are separate. */
+export async function verifyCapture(directory, cwd = process.cwd()) {
+  const root = await realpath(cwd), target = await inside(root, resolve(root, directory))
+  const result = JSON.parse(await readFile(await inside(root, join(target, 'result.json')), 'utf8'))
+  if (result.version !== 1 || !result.outcome) throw new Error('Invalid evidence result')
+  for (const [key, file] of [['command', 'command.json'], ['stdout', 'stdout.txt'], ['stderr', 'stderr.txt']]) {
+    const actual = await digest(await inside(root, join(target, file)))
+    if (actual.sha256 !== result[key]?.sha256 || actual.bytes !== result[key]?.bytes) throw new Error('Evidence changed: ' + file)
+  }
+  return { ...result, directory: relative(root, target), verified: true }
+}
+
+if (process.argv[1] && resolve(process.argv[1]) === fileURLToPath(import.meta.url)) {
+  try {
+    const argv = process.argv.slice(2)
+    if (argv[0] === '--verify' && argv.length !== 2) throw new Error('Usage: capture.mjs --verify DIRECTORY')
+    const result = argv[0] === '--verify' ? await verifyCapture(argv[1]) : await captureCommand(argv)
+    console.log(JSON.stringify(result))
+    if (!result.verified) process.exitCode = result.outcome.kind === 'exit' ? result.outcome.code : result.outcome.kind === 'signal' && result.outcome.signal === 'SIGINT' ? 130 : result.outcome.kind === 'signal' && result.outcome.signal === 'SIGTERM' ? 143 : 1
+  } catch (error) { console.error(error.message); process.exitCode = 2 }
+}

package/builtin/skills/pstack/dsh/skills/architect/SKILL.md

@@ -0,0 +1,82 @@
+---
+name: architect
+description: "Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape."
+disable-model-invocation: true
+---
+
+Read [DSH host operations](../../DSH.md) once before executing this workflow.
+
+
+# Architect
+
+Sketch types, function signatures, class shapes, and module boundaries with `not implemented` bodies and pseudocode. Synthesize across multiple model perspectives, then fill in code against the chosen sketch.
+
+## Start
+
+Open a todolist with one entry per phase before starting.
+
+1. Ground
+2. Sketch
+3. Agree
+4. Implement
+5. Scrap
+
+## Phase A: Ground the problem
+
+Build a real mental model of every system the new code touches. Run the **how** skill over the relevant subsystems. Naming a file isn't grounding. Produce the architectural explanation `how` prescribes. If the design redefines ownership or layering, also run the **why** skill on the existing shape so the rationale becomes a constraint, not a guess.
+
+Skip Phase A only when the work is genuinely greenfield with no surrounding system to integrate.
+
+## Phase B: Sketch
+
+Run the **arena** skill with the design-sketch task and the Phase A grounding artifacts. Pass `references/runner-prompt.md` as each runner's prompt.
+
+Use the architect runners panel from DSH project preferences, preserving its list length. Follow the adapted arena runner rules: two structural alternatives by default, actual available model routes only, otherwise inherited-model independent runs with the limitation reported.
+
+Design it twice. Require at least two structurally distinct candidates before synthesis, even when the first looks sufficient. This is the **exhaust-the-design-space** principle skill made concrete. Whole-shape alternatives, not point fixes inside one shape.
+
+Screen every candidate against [`references/design-red-flags.md`](references/design-red-flags.md) before synthesis. Assume the next contributor is an agent that sees only the files it opened, copies the nearest example, and takes the shortest path that compiles. Prefer the design where a change that looks right from one file is right for the whole repo.
+
+Compare viable candidates on interface depth. Prefer the design that hides more complexity behind a smaller, simpler public surface. A rich interface can keep call chains short by concentrating capability instead of scattering it across layers.
+
+Arena returns one synthesized design package. Its synthesis decision fills the rationale's "Synthesis decision" section.
+
+## Phase C: Agree (opt-in)
+
+Default: proceed directly to implementation with the synthesized design. No human checkpoint.
+
+Opt in to a checkpoint when the invoker explicitly asks: "/architect with checkpoint," "stop and show me before implementing," or similar. Then surface the synthesized design and pause for sign-off.
+
+The synthesis can ship as its own commit either way, as the "scaffold first" mode of the **foundational-thinking** principle skill. Planned and scoped breakage during fill-in is fine, per the **outcome-oriented-execution** principle skill. For adversarial pressure on the design before implementing, run the **interrogate** skill on the synthesized sketch.
+
+If the human pushes back on the shape (in a checkpoint or after the fact), treat that as Phase A evidence. Re-ground and re-run Phase B before writing more code.
+
+## Phase D: Implement against the sketch
+
+Replace `not implemented` bodies with code, pseudocode with logic. The synthesized sketch is the contract. Deviations from it are signal to surface, not friction to absorb silently. If a function needs a parameter the sketch didn't anticipate, ask whether the sketch was wrong, the requirement was missed, or the implementation is overreaching.
+
+## Phase E: Scrap when the architecture is wrong
+
+If implementation keeps producing friction the sketch can't absorb, throw the sketch out. Don't bolt fixes onto a wrong design, per the **redesign-from-first-principles** and **fix-root-causes** principle skills.
+
+The signal is a *pattern*, not single instances. Tells:
+
+- The same shape of workaround appearing repeatedly across unrelated code.
+- Multiple unrelated edge cases that all need special-case branches.
+- Types that need escape hatches (`any`, casts, optional fields always set in practice) to compile.
+- The "we need a lock" reflex when the sketch said the state wasn't shared.
+- Callers having to know the abstraction's internal rules to use it.
+- Two or more independent Phase D deviations of the same shape across the implementation.
+
+Use judgment. A few edge cases don't condemn an architecture. Some problems are legitimately complex. Complexity in the data is not complexity in the design.
+
+When you scrap:
+
+1. Re-run the **how** skill over what's been built.
+2. Redesign as if the new constraints had been day-one assumptions, per redesign-from-first-principles.
+3. Subtract before adding, per the **subtract-before-you-add** principle skill. The new sketch should be smaller than the old one before it grows.
+4. Return to Phase B and re-run arena.
+
+## Outputs
+
+The caller's usage is written first and the type sketch derived from it. One file with new types and signatures for small changes. Module map plus type definitions for larger work. The rationale ships alongside, shaped per `references/rationale-template.md`, including the usage sketch and the synthesis decision.

package/builtin/skills/pstack/dsh/skills/architect/references/design-red-flags.md

@@ -0,0 +1,57 @@
+# Design red flags
+
+Screen every candidate before synthesis. A red flag is a reason to revise or reject the shape.
+
+## Shallow module
+
+A shallow module exposes a large interface while hiding little complexity. Judge depth by the capability and policy hidden behind the public surface relative to the size of that surface. Prefer a simple interface backed by substantial behavior.
+
+Do not confuse a deep module with a deep call chain. A deep call chain scatters understanding across layers. A deep module concentrates capability behind one interface.
+
+Look for these signs:
+
+- Callers coordinate several methods to complete one operation.
+- Public options expose internal stages or implementation choices.
+- Learning the interface does not save the caller from learning the implementation.
+
+## Information leakage
+
+Information leakage makes multiple modules depend on the same internal decision. A representation, policy, or protocol detail appears in more than one place, so changing it requires coordinated edits.
+
+Public re-exports of transport or wire types are leakage. Parse external data into domain types behind the interface. Keep storage schemas, framework objects, and protocol details private.
+
+## Temporal decomposition
+
+Temporal decomposition organizes modules by execution order instead of the knowledge they own. Separate load, validate, transform, and save stages often repeat one representation and its invariants across several boundaries.
+
+Group code around domain knowledge and ownership. Methods that run at different times can still belong to one module when they protect the same decisions.
+
+## Pass-through method
+
+A pass-through method forwards the same arguments to another method with the same shape. It adds a layer without hiding complexity.
+
+Remove it or move responsibility to the module that can complete the operation. Keep a forwarding boundary only when it adds policy, adaptation, or a distinct abstraction.
+
+## Split ownership
+
+More than one module writes the same state or keeps its own copy of it. An agent that edits one writer can't see the others, so their rules diverge.
+
+Give each piece of state one owner. Other modules read it or ask the owner to change it.
+
+## Two ways to do one task
+
+The design supports more than one way to do the same task. An agent copies whichever way it finds first, so every way keeps gaining callers.
+
+Keep one way. Move callers off the others and delete them in the same change.
+
+## Importable internals
+
+A caller can import a module's internals. An agent takes the shortest path that compiles, so it imports them directly and they become part of the interface.
+
+Make internals unreachable from outside the module, so an import from outside fails the build.
+
+## Hand-synced list
+
+Two or more places list the same items, and adding an item means editing every list. An agent that sees one list updates only that one.
+
+Keep one list and derive the others from it. If a list can't be derived, make the build fail when the lists disagree.

package/builtin/skills/pstack/dsh/skills/architect/references/rationale-template.md

@@ -0,0 +1,35 @@
+# Rationale template
+
+The prose that ships alongside the type sketch. One page. Sentence-case headings, no boilerplate. Replace the italic notes with actual content.
+
+## Problem
+
+*One paragraph. What we're trying to do, and what about the existing system or constraints makes the shape non-obvious. If [Phase A](../SKILL.md#phase-a-ground-the-problem) surfaced constraints the design must honor (existing types to interop with, callers we can't break, invariants that crossed our boundary), name them here so the reader sees the same constraints you saw.*
+
+## Usage (caller's view)
+
+*Write this first, before the type sketch. Show the README or quickstart the consumer reads, plus two or three realistic call sites in their own code. What they import, what they call, what comes back. The type sketch in [Shape](#shape) is derived from this. The two must agree. When they diverge, reconcile the sketch to the usage, not the reverse. The caller's experience is the spec. The types serve it.*
+
+## Shape
+
+*The recommended architecture. Data structures first. Then how data flows through the signatures. Name the load-bearing decisions. State which invariants are encoded in types, where validation lives, and what the system deliberately does not do. Judge interface depth explicitly. State what complexity the public surface hides, what remains exposed to callers, and why the interface is no larger than needed. Cite the principle behind each decision (e.g., `per boundary-discipline`). Don't restate it.*
+
+## Synthesis decision
+
+*Filled in by [arena](../../arena/SKILL.md). Records which candidate became the base and why, what was adapted from each of the others, and what was rejected and why.*
+
+## Tradeoffs accepted
+
+*One bullet per tradeoff the chosen shape makes. Form: "we accept X in exchange for Y." Name anything a future reader might mistake for an oversight, including things that look like premature optimization or premature simplification.*
+
+## Alternatives considered
+
+*Required. Name at least one concrete alternative shape, with one line on why it lost. Judge each alternative on interface depth, not implementation simplicity alone. Name the complexity it exposes to callers and the complexity it hides. Two or three alternatives belong here when the design space had real contenders. One is fine when the constraints forced the answer, with the conclusion phrased as "this was the only viable shape because..." Avoid listing flavors of the same shape. This section covers design alternatives the chosen shape considered and rejected, not other runner candidates.*
+
+## Open questions and risks
+
+*Things you noticed during the sketch that the human needs to weigh in on, and risks worth flagging before implementation starts. Phrase as questions, not assertions, so the human's answer is the resolution rather than a comment.*
+
+## Next implementation step
+
+*The first thing to build against the sketch. One sentence. What you'd start writing immediately after synthesis (or after Phase D sign-off, if a checkpoint was opted into).*

package/builtin/skills/pstack/dsh/skills/architect/references/runner-prompt.md

@@ -0,0 +1,20 @@
+# Architect runner prompt
+
+The orchestrator passes this file through to every parallel candidate runner during Phase B and fills in the variable inputs around it: the task, the Phase A grounding artifacts, the isolated working directory, and the path to write outputs. The working directory is a git worktree when available, otherwise a per-runner subdirectory under the sketch dir. What matters is independence between candidates.
+
+You are producing one candidate design in architect's parallel exploration. Read the **architect** skill in full first. That's the workflow you're inside. Output a candidate design package: type sketch, function signatures, module map, and prose rationale shaped per [`rationale-template.md`](rationale-template.md).
+
+Apply the following discipline. The orchestrator compares candidates on these axes to pick a base.
+
+- Caller's usage first. Write the README-style usage and two or three real call sites before the types, then derive the type sketch from them. The usage is the spec. The two must agree, so reconcile the sketch to the usage, not the reverse.
+- Data structures first. Get the core types right and the code becomes obvious. Trace each dominant access pattern through the proposed structure. If the answer is "we'll add a map / index / cache later," the structure is wrong.
+- Interface depth. Compare the capability hidden behind the public surface relative to the size of that surface. Prefer a simple interface that pulls complexity into the callee, even when the implementation becomes less simple. Do not put transport or wire types on the public API. Parse into domain types behind the interface.
+- Shared state: if two actors might both write, ask "what happens?" If the answer isn't "nothing," default to per-actor state with a merge at the read boundary, per the **separate-before-serializing-shared-state** principle skill.
+- Make boundaries visible. `not implemented` errors for bodies, `// TODO` pseudocode for tricky logic, doc comments stating intent and invariants. A reader should trace data from input to output by reading types and signatures alone.
+- Encode invariants in types: hard-to-misuse types > runtime checks > prose comments, per the **encode-lessons-in-structure** principle skill.
+- Validate at boundaries, trust types inside, per the **boundary-discipline** principle skill. Business logic as pure functions. The shell stays thin.
+- Single source of truth per invariant. Derive instead of sync.
+- Idempotent state transitions where applicable, per the **make-operations-idempotent** principle skill. Ask what happens if the operation runs twice or crashes halfway.
+- Short call chains. If tracing the flow needs more than three files, flatten the hierarchy, per the **laziness-protocol** and **minimize-reader-load** principle skills.
+
+You are one of the parallel runners, each on a different model. Produce the best design your model can make. Don't hedge against the others. Differences between candidates are the signal used to pick a base and graft. Converging on a safe-looking middle defeats the exploration.