Skip to content

The open-source app everyone uses to manage agents at work

Clarify repo plan docs vs issue plan documents

dotta0d270655ab7b
diff --git a/AGENTS.md b/AGENTS.md
index dc5e9432f9..524c573abe 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -81,8 +81,8 @@ If you change schema/API behavior, update all impacted layers:
4. Do not replace strategic docs wholesale unless asked.
Prefer additive updates. Keep `doc/SPEC.md` and `doc/SPEC-implementation.md` aligned.
-5. Keep plan docs dated and centralized.
-New plan documents belong in `doc/plans/` and should use `YYYY-MM-DD-slug.md` filenames.
+5. Keep repo plan docs dated and centralized.
+When you are creating a plan file in the repository itself, new plan documents belong in `doc/plans/` and should use `YYYY-MM-DD-slug.md` filenames. This does not replace Paperclip issue planning: if a Paperclip issue asks for a plan, update the issue `plan` document per the `paperclip` skill instead of creating a repo markdown file.
## 6. Database Change Workflow