From 86c1ff4f82ce3b8ddd4a17991819d0b5fe993c2c Mon Sep 17 00:00:00 2001 From: axiomlogicnexus Date: Wed, 6 May 2026 17:33:32 +0200 Subject: [PATCH] Record task-summary closing paragraph rule --- AGENTS.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/AGENTS.md b/AGENTS.md index 57382cb..3e5daa2 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -11,4 +11,6 @@ When Visual Studio MCP tools are available, prefer semantic solution/project/doc When the user says continue, interpret it as continue in logical sequence, not merely resume the nearest open task. If two options are paired and one logically widens or completes the lane needed by the other, do that sequence rather than picking an isolated substep out of order. The default continuation target is: scope the current packet, implement it, validate it, and keep going until the safe package is ready to land unless validation fails or a real decision is required. +When providing a task summary, use the last paragraph to propose and display the next best clean roadmap implementation moves or the next best bounded implementation slice. That closing paragraph should be specific to the latest landed state and should not fall back to generic wrap-up text. + When a task is safely complete, stage, commit, and push it without waiting for a separate reminder. Prefer landing the full aligned package after the widening/closure work is done, rather than committing intermediate fragments that leave the intended sequence half-finished.