me like nix
pi: add communication rules to ask clarifying questions before acting
author
Sean Aye
date
(May 10, 2026, 3:12 PM -0400)
commit
cd0f5d53
cd0f5d53733b7209e3a5f9528d8f6c33e15a959b
parent
7c02e516
7c02e516ff4f48b9eaa050d4859d0d33396277ec
change-id
luqunsuo
luqunsuolpurrwmxopuouyywrkkrnpmn
+6
+6
modules/_config/pi/AGENTS.md
+6
modules/_config/pi/AGENTS.md
···
1
1
# Global Agent Rules
2
2
3
+
## Communication
4
+
5
+
- **Ask before acting when uncertain**: If a task is ambiguous, has multiple reasonable interpretations, or you're not confident about the approach, stop and ask the user clarifying questions before proceeding. Don't guess or assume — it's better to ask one round of questions than to go down the wrong path.
6
+
- **Confirm large or risky changes**: Before making sweeping refactors, deleting files, or changing architecture, describe your plan and get explicit approval.
7
+
- **Prefer incremental steps**: Break large tasks into smaller steps and check in with the user between steps rather than doing everything at once.
8
+
3
9
## Workflow
4
10
5
11
- **Commit after verification**: After a successful verification step (e.g. `cargo check` with 0 errors), always create a jj revision: `jj desc -m "description of changes" && jj new`