From 738a0c82e1e814ddcb98b5a05cc1edb06dc174d9 Mon Sep 17 00:00:00 2001 From: Erich Blume Date: Mon, 23 Feb 2026 15:46:55 -0800 Subject: [PATCH] Address PR feedback: simplify invariant rule, drop 'prior chains' MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - Remove "prior Mikado chains" from C1 doc search step — completed chains are just documentation, not a special category - Collapse the two "not allowed" bullets into a single rule: no card may be introduced after any code or card-closing commit Co-Authored-By: Claude Opus 4.6 --- docs/how-to/agent-change-process.md | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/docs/how-to/agent-change-process.md b/docs/how-to/agent-change-process.md index 1cc09dd..60d5db0 100644 --- a/docs/how-to/agent-change-process.md +++ b/docs/how-to/agent-change-process.md @@ -42,7 +42,7 @@ A change with enough complexity or risk that a human should review it, but not s ### Process 1. Run `mise run ai-docs` to load context -2. **Search related docs** — read existing documentation, reference cards, and prior Mikado chains related to the change area +2. **Search related docs** — read existing documentation and reference cards related to the change area 3. **Create a feature branch** and open a PR early (draft is fine) 4. **Documentation first** — commit doc changes reflecting the desired end state before writing code. This helps the reviewer understand intent and catches design issues early 5. **Implement** — commit code changes, pushing as you go. The PR gets updated along the way and the user can review and comment at any point @@ -84,10 +84,7 @@ main ← [card commits] ← [code, close] ← [code, close] ← ... ← [finaliz 3. A cycle should target a single leaf node (though closing multiple in one cycle is acceptable if the code supports it) 4. Cycles repeat until the chain is complete -**What is NOT allowed:** - -- Introducing a new Mikado card after any code or card-closing commit (new cards require a branch reset — see below) -- Closing a Mikado card before all cards it depends on have been introduced +**The one rule:** No Mikado card may be introduced after any code or card-closing commit. New cards require a branch reset (see below). **The length-zero case:** It is valid for the "planning layer" to have zero commits on the branch — this happens when all Mikado cards were introduced in earlier sessions and are already in main's history. The invariant is satisfied.