Update global agent completion rules

2026-07-18 14:09:46 -05:00
parent f25b8a3836
commit e4b77a63a6
6 changed files with 27 additions and 6 deletions
@@ -40,6 +40,7 @@ Required variables:
 - Add Issue is enabled only when the active tab's base URL is already in the URLs list and that URL is linked to a Gitea repo.
 - The Add Issue view must show the Gitea repo that will receive the issue and the active URL the extension believes it is attached to.
 - The Add Issue form must let the user select the agent file for handoff. Agents are managed in the Agents view, persisted in `chrome.storage.local`, and the initial agent is `GLOBAL AGENT` backed by `AGENTS.md`.
+- The default `GLOBAL AGENT` rules must instruct downstream agents to close the Gitea issue after pushing the implementation and to leave a Gitea issue comment when delivery is blocked, partial, or risky.
 - The Add Issue view intentionally omits the redundant view header title/description.
 - Add Issue and selected issue editing expose these label options: `Change Request`, `Idea`, `Tabitha`, `Orson`, `Belisarius`, `Ozymandias`, and `Ready`.
 - New issues default to `Change Request` selected unless the user changes the label selection.
@@ -80,7 +81,7 @@ Required variables:
 - The Agents view must allow adding, editing, and deleting agent files.
 - At least one agent must remain available so Add Issue always has a handoff file.
 - Agent records are persisted in `silmaAide.agents`.
- The default `GLOBAL AGENT` should remain agnostic and use template variables instead of hard-coded project paths where possible.
+- The default `GLOBAL AGENT` should remain agnostic and use template variables instead of hard-coded project paths where possible. The built-in persisted global agent should pick up required completion rules without replacing unrelated custom text.

 ## Agent Checklist