diff --git a/.agents/skills/issue-spec/SKILL.md b/.agents/skills/issue-spec/SKILL.md index 4ecfe16c84..57afefbc00 100644 --- a/.agents/skills/issue-spec/SKILL.md +++ b/.agents/skills/issue-spec/SKILL.md @@ -547,7 +547,7 @@ For each piece of feedback ask the only question that matters at this altitude: **Settle on the loop, not on the assertion.** A claim asserted *once* — however confidently, however wrong it sounds — is ordinary triage: answer it, fold it, or drop it with a pointer to the code. The trigger is the **second** pass: the claim came back after being answered, or the spec has already flipped on it, or two rounds reached opposite conclusions. That repetition is the signal prose has failed on it, and it's the one case where another round of argument is predictably wasted. Fire then, and not before — POC-ing every assertion would replace a two-round review with a queue of experiments, which costs more than the debate did. -**The default is Note, and the burden of proof is on folding.** If you can't name which decision card or which part of the approach changes, it isn't spec-level. The one cheap exception: genuine factual corrections and broken references get fixed inline without ceremony — they don't move the design, so they don't cost a round. +**The default is Note, and the burden of proof is on folding.** If you can't name which decision card or which part of the approach changes, it isn't spec-level. The one cheap exception: genuine factual corrections and broken references get fixed inline without ceremony — they don't move the design, so they don't cost a round. Any correction, inline or folded, still owes its echoes: before the push, run [`issue-implement`](../issue-implement/SKILL.md) 10.6's word and surface sweeps over every claim you corrected, and report both. Two instincts to override, because both run the wrong way: diff --git a/.agents/skills/polish-docs/SKILL.md b/.agents/skills/polish-docs/SKILL.md index 425dd828e4..113cc9ae9c 100644 --- a/.agents/skills/polish-docs/SKILL.md +++ b/.agents/skills/polish-docs/SKILL.md @@ -100,6 +100,10 @@ Restructuring breaks links and moves anchors — prove it didn't: `@docusaurus/plugin-client-redirects`). - Re-read moved/merged pages once as a reader to confirm the rearrangement flows. +Where the pass changed what a page asserts, not only its wording, sweep every claim you corrected: +run [`issue-implement`](../issue-implement/SKILL.md) 10.6's word and surface sweeps over the docs +and package READMEs, and report both in the PR. + ## Output - **Standalone:** present the working changes for review — a short summary of *what moved, what diff --git a/docs/contributing/orchestration.md b/docs/contributing/orchestration.md index c8910ead01..62aca8e544 100644 --- a/docs/contributing/orchestration.md +++ b/docs/contributing/orchestration.md @@ -495,7 +495,9 @@ altitude: *does acting on this change the approach?* Then pick exactly one dispo name which decision or which part of the approach changes, it is not spec-level — it's a note. Genuine factual corrections and broken references are the one cheap exception: fix them inline without ceremony (they don't move the design, so they don't -cost a round). +cost a round). Any correction, inline or folded, still owes its echoes: before the push, run +[`issue-implement`](../../.agents/skills/issue-implement/SKILL.md) 10.6's word and surface +sweeps over every claim you corrected, and report both. Two things follow that are worth stating outright, because the instinct runs the other way: