agents: handle review failure, work in slices

Amolith created

Change summary

dot_config/AGENTS.md | 2 ++
1 file changed, 2 insertions(+)

Detailed changes

dot_config/AGENTS.md 🔗

@@ -8,6 +8,8 @@ Following are Amolith's preferences.
   - github.com or "issue": `gh issue view https://github.com/USER/REPO/issues/XXX` where XXX is the issue number. USER and REPO are required, so if you can't determine this from branch/remotes, ask me _before_ running the `gh` command.
   - todo.sr.ht, "todo", or "ticket: `hut todo ticket show -t '~USER/TRACKER' XXX` where XXX is the ticket number. I'll refer to these as todos or tickets. USER and TRACKER are required, so if you can't determine this from branch/remotes, ask me _before_ running the `hut` command.
     - Run `git remote -v` and notice whether any of the remotes include 'soprani.ca', 'sopranica', 'singpolyma', variations of 'cheogram', or 'sgx-XXX' where XXX is an arbitrary string (for example, sgx-jmp, sgx-bwmsgsv2, sgx-endstream, etc.). If any of those keywords are found, the relevant tracker is `~singpolyma/soprani.ca`.
+- If the code review tool fails with a "subagent exceeded max turn limit" error, that means the scope of our review request as too broad and we should split that request into multiple with narrower scopes.
+- We work in small, vertical slices of functionality that are verifiable and testable separately from the rest of the change. I generally prefer you guide me through breaking what I suggest down into those slices because I tend to suggest changes that are far too broad and large. Investigation can happen at once, but implementation must be broken into those slices with thorough testing and manual verification between.
 
 IMPORTANT: When I ask you to plan first, I want you to first slow down and make sure you're taking your time and deliberating prior to jumping in and fulfilling my request. You'll need to look around at any mentioned files, or explore them to identify which are relevant, prior to deciding on a course of action. Only once you've broken the request down and have a solid idea what changes are necessary should you infer a list of tasks/todos. Once you've made the plan, stop and ask me to review it. Once I explicitly confirm, you may get started.