[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CNQPRDTA4V6M0RWR2VMZ2T":3,"skill-same:01M7CNQPRDTA4V6M0RWR2VMZ2T":56},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7CNQPRDTA4V6M0RWR2VMZ2T","conduct",null,"Run the conductor pattern on a project under docs\u002Fprojects\u002F — read where it stands, brief a subagent on the next phase, verify the named proof independently, record findings, move the status lines, commit the phase whole to main. Use for \"\u002Fconduct \u003Cproject>\", \"conduct square\", \"do the next phase of gateway\", \"where does registry stand\", or \"close vault phase 5\".","dglazkov\u002Ftown","dglazkov","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1934?v=4","01M7CNQMH6SZHW4FP7K9ZPAF7R","Dimitri Glazkov","01M7CNQMJ6N3G5S23B9JQGKYDB",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdglazkov\u002Ftown\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fconduct\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: conduct\ndescription: Run the conductor pattern on a project under docs\u002Fprojects\u002F — read where it stands, brief a subagent on the next phase, verify the named proof independently, record findings, move the status lines, commit the phase whole to main. Use for \"\u002Fconduct \u003Cproject>\", \"conduct square\", \"do the next phase of gateway\", \"where does registry stand\", or \"close vault phase 5\".\nargument-hint: \"\u003Cproject> [status | \u003Cphase number> | one]\"\n---\n\n# conduct: one phase of a project, verified, recorded, committed\n\nA project under `docs\u002Fprojects\u002F\u003Cname>\u002F` is three documents: `journey.md`\n(the acceptance suite), `design.md` (the argument), `phases.md` (the\nwalk). This skill is how the walk is walked. The session that runs it is\nthe **conductor**. It does not build; it briefs a subagent that builds,\nthen it verifies the proof the phase named up front, never taking the\nsubagent's word for it, and only then writes the record and commits.\nThen it goes on to the next phase. **The default is unattended**: the\nconductor runs until the leg is done or until the next step needs a\nperson, and nothing else stops it. A person is needed for exactly three\nthings: a token or a login, a paid plan or a cloud resource (a ⚑ step),\nand a hand the journey names (a second machine, a click in a browser, an\nOAuth consent screen). Everything else, a wrong design, a proof that\ncannot be run as written, a doc that disagrees with another, is the\nconductor's decision to take, record, and commit.\n\nThe project's `phases.md` is the contract. Its opening paragraphs carry\nrules of its own (where a proof must run, what stands in for a real\nservice until the phase whose job is the real one). Those rules win over\nanything here. The house rules in `AGENTS.md` apply to everyone,\nconductor and subagent alike.\n\n## Arguments\n\n- `\u002Fconduct \u003Cproject>`: orient, then conduct phase after phase until a\n  step needs a person or the leg is done. Commit and push after each\n  phase; the user reads progress from the commits on `main`, not from\n  a report they must wait for.\n- `\u002Fconduct \u003Cproject> status`: orient and report, change nothing.\n- `\u002Fconduct \u003Cproject> \u003CN>`: conduct that phase and stop after it. If an\n  earlier phase is NOT STARTED, conduct it first and say so; phases run\n  in order for a reason.\n- `\u002Fconduct \u003Cproject> one`: the next phase only, then stop.\n\n## Status vocabulary\n\nOne of four words on each phase's `**Status:**` line, followed by the\ndate it last moved and one sentence of what holds:\n\n- **NOT STARTED.** Nothing built.\n- **PART-DONE.** Every proof that can run here has run; the walk that\n  closes it waits on something named in an Open finding (a person, a\n  second machine, a paid plan).\n- **CLOSED.** The proof held, walk included. A phase that claims a\n  journey closes only when the journey was walked for real.\n- **WITHDRAWN**, or a phase re-cut with a `**Formerly: …**` record at the\n  end of its section. What was built and why it went stays in the doc.\n\n## 0. Orient\n\nRun the status script first. It is mechanical on purpose: where-we-are,\nevery phase's status, the next phase's proof and ⚑ steps, the Open\nroster, and a lint of the docs' own rules.\n\n```sh\n\u002FUsers\u002Fdimitriglazkov\u002FDocuments\u002Fcode\u002Ftown\u002F.claude\u002Fskills\u002Fconduct\u002Fstatus.sh \u003Cproject>\n```\n\nThen the brief script, for the phase you will conduct, into the\nscratchpad; §1 is what to do with what it writes. It refuses a phase\nwhose status is not NOT STARTED, printing the word, unless `--any`, and\nrefuses a journey the phase names that `journey.md` lacks, which is the\nfirst gate below, found early.\n\n```sh\n\u002FUsers\u002Fdimitriglazkov\u002FDocuments\u002Fcode\u002Ftown\u002F.claude\u002Fskills\u002Fconduct\u002Fbrief.sh \u003Cproject> \u003CN> > \u003Cscratchpad>\u002Fbrief.md\n```\n\nThen read, in this order: the phase's section in `phases.md`; every\njourney it names, in `journey.md`; the parts of `design.md` those cite;\nthe Findings of the phases before it (they are the things the design\ndid not know); `AGENTS.md`. Note the wall clock; a Finding records what\na phase cost.\n\n**Four gates before any code:**\n\n- **The docs agree.** If the phase's Proof, the journey's steps, and the\n  design's mechanism disagree, fix the docs first, as their own commit,\n  before briefing anyone. Journey.md says which way: the mechanism\n  changes. Building on a contradiction produces a facade that satisfies\n  one document and not the other, and the subagent will not tell you\n  which.\n- **Nothing is owed to another project.** The where-we-are paragraph\n  says when a phase waits on another project's phase. If so, conduct\n  that phase of the other project first, under the same rules, then\n  come back. Say so in the report; do not stop for it.\n- **⚑ provision steps are asked, not done.** Each one creates a cloud\n  resource, spends money, or needs a login. Before the phase starts,\n  list them to the user with the price, and get a yes for each. A step\n  without a yes is the subagent's stop line: it builds up to it and\n  reports. This is the one gate that waits on a person, so before\n  stopping at it, do every phase and every part of this phase that does\n  not need the answer, so the ask is the only thing left.\n- **What runs on the box is proved on a box.** A phase whose Work\n  touches what the box runs or how it is reached (`src\u002Fbox.ts`, the\n  object, the isolate or the window, `src\u002Fwire.ts`, `docs\u002Fharness.md`,\n  `scripts\u002Fbox.mjs`, a shop's `runtime: worker`) and whose Proof names\n  no ring gets one, as a docs fix before briefing: `pnpm hermetic --ring\n  account` for the wire, `--ring agent` for what an agent meets. Its run\n  is a ⚑ step, asked with its price. Fakes and workerd did not see tent\n  phase 0's first finding, a fresh box answering 500 after its deploy\n  called it ready; the account ring did, on its first run.\n\n## 1. Brief\n\nWrite the brief to a file in the scratchpad so it can be reread, reused\nif the subagent must be restarted, and quoted in the commit. The script\nwrites it (§0) and the conductor edits it: the brief is the phase's\nsection verbatim plus what the subagent needs to not guess, and the\nscript copies every part of that the docs hold, by the same conventions\n`status.sh` reads them by:\n\n```\n# \u003Cproject> phase \u003CN>: \u003Ctitle> — briefed \u003Cdate> at \u003Ccommit>\n\n## Asked before the phase starts   (the phase's ⚑ steps, or none)\n## The phase                       (phases.md section, verbatim)\n## The journeys it closes          (every journey its **Closes:** names, whole)\n## The mechanism                   (design.md's names table; every heading as a sed -n line)\n## Findings so far that bind you   (every earlier phase's, verbatim; then the Open roster)\n## House rules                     (AGENTS.md, verbatim; the project's own rules paragraph, verbatim)\n## What you own                    (the paths the phase names; then the tail)\n```\n\nThe conductor then pastes into the mechanism the design sections the\nphase leans on, and anywhere the brief needs it what the docs do not\nsay, and gives it to the subagent. The tail, what the subagent owns,\nwhere it stops, and what it returns, is `brief.sh`'s, and this skill\nno longer quotes it.\n\nSpawn with the Agent tool (`general-purpose`). Parallel subagents belong\ninside a phase, splitting its Work list by file ownership, never across\nphases. A subagent's final report is not shown to the user; you relay\nwhat matters.\n\n## 2. Verify\n\nThis is the conductor's job and nobody else's. The subagent's report is\na map; the phase's **Proof** paragraph is the territory. Run the proof\nas written there, from the repo root, in the order written, and read\nexit codes rather than tails (`| tail` and a trailing `echo` both report\nthe last command's status, not the suite's).\n\nThe checklist, every phase:\n\n- `git status --short`: only the phase's files changed, no leftovers,\n  no secrets file (`.env`, `.dev.vars`, a token in a fixture) in the\n  diff, nothing under `docs\u002Fprojects\u002F`.\n- The whole suite and typecheck, not just the new tests, by the commands\n  `AGENTS.md` names. The project's rules say where a test must run; a\n  test that passes somewhere else proves that somewhere else works. If\n  CI runs a subset, a green workflow is not the proof. If you ran a\n  subset, name what you skipped in the report, or run it.\n- The named proof, command by command.\n- A mutation the Proof names, by `node scripts\u002Fmutate.mjs \u003Cfile> --from\n  '\u003Ctext>' --to '\u003Ctext>' -- \u003Ccommand>`, which backs the file up, runs the\n  command, and puts the file back by copy: in box phase 0 a conductor\n  reverted a mutation with `git checkout` in a dirty tree and wiped the\n  builder's uncommitted work.\n- The walk, when the phase has one: against a real deployment, a real\n  model, a real service, a real credential. Walks find what fixtures\n  cannot. A phase with a walk is not CLOSED until the walk is walked.\n- The ring, when the Proof holds `pnpm hermetic`. A Proof that names a\n  walk over the box writes the ring's line,\n  `pnpm hermetic --ring agent --sheep \u003Cdir> --repo \u003Cowner\u002Fname> --issue \u003Cn>`,\n  with the github token on its stdin; the conductor types it, never the\n  builder, since the ring pitches a tent on the account and spends money,\n  and the findings record the ring's exit and the stage's report.\n  `brief.sh` carries this sentence into the brief of any phase whose\n  Proof holds `pnpm hermetic`.\n- Open the new tests and ask of each: could this fail? What does it\n  exercise, the thing or a stand-in for the thing? A test that asserts\n  what the code returns, rather than what the journey requires, proves\n  the code agrees with itself.\n- Read the diff for a facade: a surface that imitates a program, a shim\n  that satisfies the fixture's calls only, a refusal sentence that\n  changed without its test.\n\n**Work that fails goes back down.** Send the failure to the same\nsubagent with `SendMessage`, so it keeps its context: the exact command,\nthe exact output, the line of the Proof or journey it violates. Do not\nfix code yourself; the conductor edits documents. A doc fix the failure\nexposes (a Proof that cannot be run as written) is yours, before\nsending it back.\n\n## 3. Record\n\nWhen the proof holds, and only then, write the record. All of it in one\nchange, so the docs never disagree with each other:\n\n- **Findings**, under the phase: one dated line per claim, about forty\n  words, `- **YYYY-MM-DD — Claim.** Evidence.` The argument goes in the\n  commit message, not here. A Findings section stays under three\n  hundred words. Something a later phase must pay for is an Open entry:\n  `- **YYYY-MM-DD — Open: what.** Who or what it waits on.` The status\n  script lists the roster.\n- **The Status line** of the phase: the word, the date, one sentence of\n  what holds.\n- **The where-we-are paragraph**: which phases stand where, what the\n  next thing to do is (`\u003Cproject> phase N`), what waits on a person and\n  what waits on work.\n- **`journey.md` front matter**: `status:` (`planned`, `partial`,\n  `done`) and the `note:` retold to include this phase.\n- **`design.md`'s opening line**, the dated one: `Nothing built` while\n  planned, what is built once a phase closes, `Done` when the project\n  is. The status script lints it against the front matter.\n- **The projects index**, `docs\u002Fprojects\u002FREADME.md`: the project's\n  \"where it stands\" cell, which must not be more right than the docs\n  it summarizes, and must not be less.\n- **Another project's docs**, when this phase changed something they\n  describe. `grep -rn` the file or term across `docs\u002Fprojects\u002F` and fix\n  each mention, so a reader of that project is not told a stale fact.\n- **Citations name their project**: `gateway phase 2`, never `phase 2`.\n\nRun the status script again. Its lint must be clean for what you\ntouched; pre-existing hits are reported, not silently absorbed.\n\n## 4. Commit\n\nOne commit per phase, the phase whole: code, tests, the record. Title\n`\u003Cproject> phase \u003CN>: \u003Ctitle>` for a phase that moved, `\u003Cproject>: \u003Cwhat>`\nfor anything smaller. The body is the argument: what was built, what the\nproof showed, what was found, in prose a reader who was not here can\nfollow. End with the session trailer the harness gives you. Commit to\n`main` and push; do not bunch phases on a branch. The user reads\nprogress from the commits.\n\nThen go on to the next phase. Write a short report between phases (the\nphase, its new status, the proof and what it printed, the findings) so\na reader following along has one; do not wait for a reply to it. The\nfull report comes when you stop.\n\n## Stopping\n\nThe conductor stops for a person, and for nothing else. The stop is\nalways recorded first, so a later session can pick up from the docs\nalone:\n\n- **PART-DONE, waits on a person.** Local proofs green; the walk needs a\n  second machine, a login, a token, a paid plan, or a hand. Status\n  PART-DONE, an Open finding naming exactly what and whom, where-we-are\n  says so, commit, push. Then, before stopping, look past it: if the\n  next phase needs none of that, conduct it. Stop only when every phase\n  left needs the person. The final report puts every ask in one list,\n  each one sentence with its price.\n\nTwo things look like stops and are not. Decide them, record them, go on:\n\n- **The design is wrong.** The subagent found the mechanism does not\n  hold. Change `design.md` as its own commit with the reason, then\n  re-brief. A phase can be withdrawn; it cannot be quietly redefined.\n  This is the conductor's call, not the user's, and the commit message\n  is where the user hears the argument.\n- **The proof cannot be run as written.** The Proof paragraph asks for\n  something the repo cannot produce. Fix the Proof, say why in the\n  commit, then continue. Never mark a phase by a proof that was not the\n  one named.\n\n**Before the leg's final report**, when its commits touched what the\nbox runs or how it is reached and no ring ran on the last of them, run\n`pnpm hermetic --ring account` once on that commit, asked with its\nprice like any ⚑ step, and put its exit and its verdict line in the\nreport. A ring nothing runs rots quietly: it needs a token, a sheep\ncheckout, and a standing station, and CI runs none of them.\n\nWhen in doubt whether something needs a person, ask: is the missing\nthing a credential, money, or a hand? If not, it is yours.\n\n## Things that have gone wrong before\n\nThese are from sheep, the repo this skill came from, and from town.\nThe pattern is the same here and so are the failure modes.\n\n- A subagent said the suite passed; it had run `npm test | tail`, and\n  six tests had failed. Read the exit code.\n- Two suites and two typechecks passed while the CLI was broken,\n  because the break was in a command only the walk runs. Walk.\n- A twelve-verb `git` passed every test against a fixture that used\n  neither `--depth` nor `git diff`'s header, and the model fabricated a\n  real-looking diff to cover for it. A facade that is almost the thing\n  costs more than a shell that says it lacks it. Read the diff for one.\n- Journey docs were recast while phases still said the old thing; a\n  reader found three names for one phase. Record everything in one\n  change.\n- Provisioning happened before it was asked (a deploy on a scratch\n  account was fine; a paid plan would not have been). ⚑ steps are asked\n  with the price, every time.\n- A subagent edited `phases.md` and the conductor edited it too; the\n  merge lost a finding. The conductor owns the record.\n- The shell's cwd was inside a submodule and a relative `cd` chain did\n  nothing. Absolute paths in every command you give a subagent.\n- In box phase 0 the conductor reverted a Proof's mutation with `git\n  checkout`, in a tree holding the builder's uncommitted work, and the\n  builder had to redo two files. Mutate by `scripts\u002Fmutate.mjs`, which\n  restores by copy, never by `git`.\n- In wagon phase 0 the conductor ran the Proof's mutation, which built\n  `dist\u002F` from the mutant, then walked with `bin\u002Ftownd.js`, which runs\n  `dist\u002F` without asking whether it is fresh; the walk imported past the\n  check the mutation removed. Walk before mutating, or `pnpm build` first.\n","# conduct: one phase of a project, verified, recorded, committed\n\nA project under `docs\u002Fprojects\u002F\u003Cname>\u002F` is three documents: `journey.md`\n(the acceptance suite), `design.md` (the argument), `phases.md` (the\nwalk). This skill is how the walk is walked. The session that runs it is\nthe **conductor**. It does not build; it briefs a subagent that builds,\nthen it verifies the proof the phase named up front, never taking the\nsubagent's word for it, and only then writes the record and commits.\nThen it goes on to the next phase. **The default is unattended**: the\nconductor runs until the leg is done or until the next step needs a\nperson, and nothing else stops it. A person is needed for exactly three\nthings: a token or a login, a paid plan or a cloud resource (a ⚑ step),\nand a hand the journey names (a second machine, a click in a browser, an\nOAuth consent screen). Everything else, a wrong design, a proof that\ncannot be run as written, a doc that disagrees with another, is the\nconductor's decision to take, record, and commit.\n\nThe project's `phases.md` is the contract. Its opening paragraphs carry\nrules of its own (where a proof must run, what stands in for a real\nservice until the phase whose job is the real one). Those rules win over\nanything here. The house rules in `AGENTS.md` apply to everyone,\nconductor and subagent alike.\n\n## Arguments\n\n- `\u002Fconduct \u003Cproject>`: orient, then conduct phase after phase until a\n  step needs a person or the leg is done. Commit and push after each\n  phase; the user reads progress from the commits on `main`, not from\n  a report they must wait for.\n- `\u002Fconduct \u003Cproject> status`: orient and report, change nothing.\n- `\u002Fconduct \u003Cproject> \u003CN>`: conduct that phase and stop after it. If an\n  earlier phase is NOT STARTED, conduct it first and say so; phases run\n  in order for a reason.\n- `\u002Fconduct \u003Cproject> one`: the next phase only, then stop.\n\n## Status vocabulary\n\nOne of four words on each phase's `**Status:**` line, followed by the\ndate it last moved and one sentence of what holds:\n\n- **NOT STARTED.** Nothing built.\n- **PART-DONE.** Every proof that can run here has run; the walk that\n  closes it waits on something named in an Open finding (a person, a\n  second machine, a paid plan).\n- **CLOSED.** The proof held, walk included. A phase that claims a\n  journey closes only when the journey was walked for real.\n- **WITHDRAWN**, or a phase re-cut with a `**Formerly: …**` record at the\n  end of its section. What was built and why it went stays in the doc.\n\n## 0. Orient\n\nRun the status script first. It is mechanical on purpose: where-we-are,\nevery phase's status, the next phase's proof and ⚑ steps, the Open\nroster, and a lint of the docs' own rules.\n\n```sh\n\u002FUsers\u002Fdimitriglazkov\u002FDocuments\u002Fcode\u002Ftown\u002F.claude\u002Fskills\u002Fconduct\u002Fstatus.sh \u003Cproject>\n```\n\nThen the brief script, for the phase you will conduct, into the\nscratchpad; §1 is what to do with what it writes. It refuses a phase\nwhose status is not NOT STARTED, printing the word, unless `--any`, and\nrefuses a journey the phase names that `journey.md` lacks, which is the\nfirst gate below, found early.\n\n```sh\n\u002FUsers\u002Fdimitriglazkov\u002FDocuments\u002Fcode\u002Ftown\u002F.claude\u002Fskills\u002Fconduct\u002Fbrief.sh \u003Cproject> \u003CN> > \u003Cscratchpad>\u002Fbrief.md\n```\n\nThen read, in this order: the phase's section in `phases.md`; every\njourney it names, in `journey.md`; the parts of `design.md` those cite;\nthe Findings of the phases before it (they are the things the design\ndid not know); `AGENTS.md`. Note the wall clock; a Finding records what\na phase cost.\n\n**Four gates before any code:**\n\n- **The docs agree.** If the phase's Proof, the journey's steps, and the\n  design's mechanism disagree, fix the docs first, as their own commit,\n  before briefing anyone. Journey.md says which way: the mechanism\n  changes. Building on a contradiction produces a facade that satisfies\n  one document and not the other, and the subagent will not tell you\n  which.\n- **Nothing is owed to another project.** The where-we-are paragraph\n  says when a phase waits on another project's phase. If so, conduct\n  that phase of the other project first, under the same rules, then\n  come back. Say so in the report; do not stop for it.\n- **⚑ provision steps are asked, not done.** Each one creates a cloud\n  resource, spends money, or needs a login. Before the phase starts,\n  list them to the user with the price, and get a yes for each. A step\n  without a yes is the subagent's stop line: it builds up to it and\n  reports. This is the one gate that waits on a person, so before\n  stopping at it, do every phase and every part of this phase that does\n  not need the answer, so the ask is the only thing left.\n- **What runs on the box is proved on a box.** A phase whose Work\n  touches what the box runs or how it is reached (`src\u002Fbox.ts`, the\n  object, the isolate or the window, `src\u002Fwire.ts`, `docs\u002Fharness.md`,\n  `scripts\u002Fbox.mjs`, a shop's `runtime: worker`) and whose Proof names\n  no ring gets one, as a docs fix before briefing: `pnpm hermetic --ring\n  account` for the wire, `--ring agent` for what an agent meets. Its run\n  is a ⚑ step, asked with its price. Fakes and workerd did not see tent\n  phase 0's first finding, a fresh box answering 500 after its deploy\n  called it ready; the account ring did, on its first run.\n\n## 1. Brief\n\nWrite the brief to a file in the scratchpad so it can be reread, reused\nif the subagent must be restarted, and quoted in the commit. The script\nwrites it (§0) and the conductor edits it: the brief is the phase's\nsection verbatim plus what the subagent needs to not guess, and the\nscript copies every part of that the docs hold, by the same conventions\n`status.sh` reads them by:\n\n```\n# \u003Cproject> phase \u003CN>: \u003Ctitle> — briefed \u003Cdate> at \u003Ccommit>\n\n## Asked before the phase starts   (the phase's ⚑ steps, or none)\n## The phase                       (phases.md section, verbatim)\n## The journeys it closes          (every journey its **Closes:** names, whole)\n## The mechanism                   (design.md's names table; every heading as a sed -n line)\n## Findings so far that bind you   (every earlier phase's, verbatim; then the Open roster)\n## House rules                     (AGENTS.md, verbatim; the project's own rules paragraph, verbatim)\n## What you own                    (the paths the phase names; then the tail)\n```\n\nThe conductor then pastes into the mechanism the design sections the\nphase leans on, and anywhere the brief needs it what the docs do not\nsay, and gives it to the subagent. The tail, what the subagent owns,\nwhere it stops, and what it returns, is `brief.sh`'s, and this skill\nno longer quotes it.\n\nSpawn with the Agent tool (`general-purpose`). Parallel subagents belong\ninside a phase, splitting its Work list by file ownership, never across\nphases. A subagent's final report is not shown to the user; you relay\nwhat matters.\n\n## 2. Verify\n\nThis is the conductor's job and nobody else's. The subagent's report is\na map; the phase's **Proof** paragraph is the territory. Run the proof\nas written there, from the repo root, in the order written, and read\nexit codes rather than tails (`| tail` and a trailing `echo` both report\nthe last command's status, not the suite's).\n\nThe checklist, every phase:\n\n- `git status --short`: only the phase's files changed, no leftovers,\n  no secrets file (`.env`, `.dev.vars`, a token in a fixture) in the\n  diff, nothing under `docs\u002Fprojects\u002F`.\n- The whole suite and typecheck, not just the new tests, by the commands\n  `AGENTS.md` names. The project's rules say where a test must run; a\n  test that passes somewhere else proves that somewhere else works. If\n  CI runs a subset, a green workflow is not the proof. If you ran a\n  subset, name what you skipped in the report, or run it.\n- The named proof, command by command.\n- A mutation the Proof names, by `node scripts\u002Fmutate.mjs \u003Cfile> --from\n  '\u003Ctext>' --to '\u003Ctext>' -- \u003Ccommand>`, which backs the file up, runs the\n  command, and puts the file back by copy: in box phase 0 a conductor\n  reverted a mutation with `git checkout` in a dirty tree and wiped the\n  builder's uncommitted work.\n- The walk, when the phase has one: against a real deployment, a real\n  model, a real service, a real credential. Walks find what fixtures\n  cannot. A phase with a walk is not CLOSED until the walk is walked.\n- The ring, when the Proof holds `pnpm hermetic`. A Proof that names a\n  walk over the box writes the ring's line,\n  `pnpm hermetic --ring agent --sheep \u003Cdir> --repo \u003Cowner\u002Fname> --issue \u003Cn>`,\n  with the github token on its stdin; the conductor types it, never the\n  builder, since the ring pitches a tent on the account and spends money,\n  and the findings record the ring's exit and the stage's report.\n  `brief.sh` carries this sentence into the brief of any phase whose\n  Proof holds `pnpm hermetic`.\n- Open the new tests and ask of each: could this fail? What does it\n  exercise, the thing or a stand-in for the thing? A test that asserts\n  what the code returns, rather than what the journey requires, proves\n  the code agrees with itself.\n- Read the diff for a facade: a surface that imitates a program, a shim\n  that satisfies the fixture's calls only, a refusal sentence that\n  changed without its test.\n\n**Work that fails goes back down.** Send the failure to the same\nsubagent with `SendMessage`, so it keeps its context: the exact command,\nthe exact output, the line of the Proof or journey it violates. Do not\nfix code yourself; the conductor edits documents. A doc fix the failure\nexposes (a Proof that cannot be run as written) is yours, before\nsending it back.\n\n## 3. Record\n\nWhen the proof holds, and only then, write the record. All of it in one\nchange, so the docs never disagree with each other:\n\n- **Findings**, under the phase: one dated line per claim, about forty\n  words, `- **YYYY-MM-DD — Claim.** Evidence.` The argument goes in the\n  commit message, not here. A Findings section stays under three\n  hundred words. Something a later phase must pay for is an Open entry:\n  `- **YYYY-MM-DD — Open: what.** Who or what it waits on.` The status\n  script lists the roster.\n- **The Status line** of the phase: the word, the date, one sentence of\n  what holds.\n- **The where-we-are paragraph**: which phases stand where, what the\n  next thing to do is (`\u003Cproject> phase N`), what waits on a person and\n  what waits on work.\n- **`journey.md` front matter**: `status:` (`planned`, `partial`,\n  `done`) and the `note:` retold to include this phase.\n- **`design.md`'s opening line**, the dated one: `Nothing built` while\n  planned, what is built once a phase closes, `Done` when the project\n  is. The status script lints it against the front matter.\n- **The projects index**, `docs\u002Fprojects\u002FREADME.md`: the project's\n  \"where it stands\" cell, which must not be more right than the docs\n  it summarizes, and must not be less.\n- **Another project's docs**, when this phase changed something they\n  describe. `grep -rn` the file or term across `docs\u002Fprojects\u002F` and fix\n  each mention, so a reader of that project is not told a stale fact.\n- **Citations name their project**: `gateway phase 2`, never `phase 2`.\n\nRun the status script again. Its lint must be clean for what you\ntouched; pre-existing hits are reported, not silently absorbed.\n\n## 4. Commit\n\nOne commit per phase, the phase whole: code, tests, the record. Title\n`\u003Cproject> phase \u003CN>: \u003Ctitle>` for a phase that moved, `\u003Cproject>: \u003Cwhat>`\nfor anything smaller. The body is the argument: what was built, what the\nproof showed, what was found, in prose a reader who was not here can\nfollow. End with the session trailer the harness gives you. Commit to\n`main` and push; do not bunch phases on a branch. The user reads\nprogress from the commits.\n\nThen go on to the next phase. Write a short report between phases (the\nphase, its new status, the proof and what it printed, the findings) so\na reader following along has one; do not wait for a reply to it. The\nfull report comes when you stop.\n\n## Stopping\n\nThe conductor stops for a person, and for nothing else. The stop is\nalways recorded first, so a later session can pick up from the docs\nalone:\n\n- **PART-DONE, waits on a person.** Local proofs green; the walk needs a\n  second machine, a login, a token, a paid plan, or a hand. Status\n  PART-DONE, an Open finding naming exactly what and whom, where-we-are\n  says so, commit, push. Then, before stopping, look past it: if the\n  next phase needs none of that, conduct it. Stop only when every phase\n  left needs the person. The final report puts every ask in one list,\n  each one sentence with its price.\n\nTwo things look like stops and are not. Decide them, record them, go on:\n\n- **The design is wrong.** The subagent found the mechanism does not\n  hold. Change `design.md` as its own commit with the reason, then\n  re-brief. A phase can be withdrawn; it cannot be quietly redefined.\n  This is the conductor's call, not the user's, and the commit message\n  is where the user hears the argument.\n- **The proof cannot be run as written.** The Proof paragraph asks for\n  something the repo cannot produce. Fix the Proof, say why in the\n  commit, then continue. Never mark a phase by a proof that was not the\n  one named.\n\n**Before the leg's final report**, when its commits touched what the\nbox runs or how it is reached and no ring ran on the last of them, run\n`pnpm hermetic --ring account` once on that commit, asked with its\nprice like any ⚑ step, and put its exit and its verdict line in the\nreport. A ring nothing runs rots quietly: it needs a token, a sheep\ncheckout, and a standing station, and CI runs none of them.\n\nWhen in doubt whether something needs a person, ask: is the missing\nthing a credential, money, or a hand? If not, it is yours.\n\n## Things that have gone wrong before\n\nThese are from sheep, the repo this skill came from, and from town.\nThe pattern is the same here and so are the failure modes.\n\n- A subagent said the suite passed; it had run `npm test | tail`, and\n  six tests had failed. Read the exit code.\n- Two suites and two typechecks passed while the CLI was broken,\n  because the break was in a command only the walk runs. Walk.\n- A twelve-verb `git` passed every test against a fixture that used\n  neither `--depth` nor `git diff`'s header, and the model fabricated a\n  real-looking diff to cover for it. A facade that is almost the thing\n  costs more than a shell that says it lacks it. Read the diff for one.\n- Journey docs were recast while phases still said the old thing; a\n  reader found three names for one phase. Record everything in one\n  change.\n- Provisioning happened before it was asked (a deploy on a scratch\n  account was fine; a paid plan would not have been). ⚑ steps are asked\n  with the price, every time.\n- A subagent edited `phases.md` and the conductor edited it too; the\n  merge lost a finding. The conductor owns the record.\n- The shell's cwd was inside a submodule and a relative `cd` chain did\n  nothing. Absolute paths in every command you give a subagent.\n- In box phase 0 the conductor reverted a Proof's mutation with `git\n  checkout`, in a tree holding the builder's uncommitted work, and the\n  builder had to redo two files. Mutate by `scripts\u002Fmutate.mjs`, which\n  restores by copy, never by `git`.\n- In wagon phase 0 the conductor ran the Proof's mutation, which built\n  `dist\u002F` from the mutant, then walked with `bin\u002Ftownd.js`, which runs\n  `dist\u002F` without asking whether it is fresh; the walk imported past the\n  check the mutation removed. Walk before mutating, or `pnpm build` first.\n",{"name":5,"description":7,"argument-hint":24},"\u003Cproject> [status | \u003Cphase number> | one]","main","bebf29d900673d506137495318c6bcd6f3b69e92",".claude\u002Fskills\u002Fconduct","https:\u002F\u002Fgithub.com\u002Fdglazkov\u002Ftown","https:\u002F\u002Fgithub.com\u002Fdglazkov","http:\u002F\u002Fglazkov.com\u002F","2026-09-15 12:17:01",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add dglazkov\u002Ftown --skill conduct",{"tool":38,"command":39},"bunx","bunx skills add dglazkov\u002Ftown --skill conduct",{"tool":41,"command":42},"pnpm","pnpm dlx skills add dglazkov\u002Ftown --skill conduct","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdglazkov\u002Ftown\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fconduct\u002FSKILL.md",true,[46,52],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"brief.sh","SCRIPT","脚本",10261,"https:\u002F\u002Fgithub.com\u002Fdglazkov\u002Ftown\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fconduct\u002Fbrief.sh",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"status.sh",5668,"https:\u002F\u002Fgithub.com\u002Fdglazkov\u002Ftown\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fconduct\u002Fstatus.sh",[57],{"skillNo":58,"name":59,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":60,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7CNQX48863BMBGVHQHJAAYZ","town","https:\u002F\u002Fgithub.com\u002Fdglazkov\u002Ftown\u002Fblob\u002Fmain\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fdglazkov\u002Ftown\u002Fblob\u002Fmain\u002FSKILL.md",[],[]]