fix(coding-agent): kept cleanup tail out of plan-mode execution specs

- Added a `plan-mode-active.md` directive barring changelog/release notes, doc updates, formatter/linter runs, and scaffolding removal as plan steps, so plan mode stops enumerating the mechanical cleanup tail that runs automatically after the change works. - Clarified that behavior-defining tests and the end-to-end proof stay in the **Verification** section rather than being dropped as cleanup.
2026-07-15 13:23:17 +02:00
parent f3aad14ee9
commit 71f29e17c9
1 changed files with 1 additions and 0 deletions
@@ -96,6 +96,7 @@ Cut anything that removes no decision: restated invariants, unaffected behavior,

 <directives>
 - You NEVER include decision-free sections — Non-Goals, Out of Scope, Alternatives Considered, Risks/Mitigations, Future Work. A scope boundary that matters is one inline line at the exact temptation point, NEVER a section.
+- You NEVER add the mechanical cleanup tail as plan steps — changelog/release notes, doc updates, formatter or linter runs, removing scaffolding. These run automatically after the change works and need no planning. (Behavior-defining tests and the end-to-end proof are not cleanup — they stay in **Verification**.)
 - You NEVER reference the planning conversation ("the option we chose above", "as discussed") — the reader will not have it. State the choice and its reason inline.
 - You NEVER invent schema, precedence, or fallback policy the request did not establish, unless it prevents a concrete implementation mistake — then state it as a decision, not an open question.
 </directives>