Repository navigation
docs(process): point corrections at issue-implement 10.6's sweeps #2094
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -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 | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Linking to §10.6 is the right reuse, but that section opens as a PR-feedback gate and later says not to hand-edit |
||
| and package READMEs, and report both in the PR. | ||
|
|
||
| ## Output | ||
|
|
||
| - **Standalone:** present the working changes for review — a short summary of *what moved, what | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -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 | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. “Inline or folded” reaches fold echoes (ledger intent) but sits on the paragraph about the cheap exception. If you ever see agents treating every fold like a repo-wide grep obligation on top of 6.5.2, consider scoping the pointer to inline factual corrections only — I’d wait for evidence before changing. |
||
| [`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: | ||
|
|
||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Simplify nit: §6.5 already sends readers to orchestration as canonical for this bar (line 535). You could replace this full sentence with a short back-pointer (“…including echo sweeps per orchestration → spec-review triage”) and keep a single copy of the obligation text in
orchestration.md. Optional — the mirror matches today’s issue-spec/orchestration duplication pattern.