diff --git a/AGENTS.md b/AGENTS.md
index b27c78b..f414fe4 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -27,8 +27,12 @@ Do not invent architecture outside these plans unless explicitly requested.
 
 - Design specs live in `docs/superpowers/specs/` as `YYYY-MM-DD-<topic>-design.md`.
 - Implementation plans live in `docs/superpowers/plans/` as `YYYY-MM-DD-<topic>.md` (suffix the topic with `-v1`/`-v2`/etc. if a plan is versioned).
-- Commit both to git as soon as the user approves them.
-- Do not leave specs or plans outside this repo. The `~/.claude/plans/<slug>.md` plan-mode scratch file is acceptable while plan mode is open; the persisted artifact must end up under `docs/superpowers/` and be committed.
+- **Every spec and every plan must be committed to this repo.** No exceptions. As soon as the user approves a spec or a plan, the next action is `git add` + `git commit` of that file under `docs/superpowers/`.
+- The `~/.claude/plans/<slug>.md` plan-mode scratch file is acceptable *only* while plan mode is open. The moment plan mode exits with an approved design, copy the content into `docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md` and commit it — do not leave the design only in the scratch file.
+- Before claiming a feature is "shipped", verify both files exist in-tree:
+  - `git ls-files docs/superpowers/specs/ | grep <topic>` returns the spec.
+  - `git ls-files docs/superpowers/plans/ | grep <topic>` returns the plan.
+- Push to the remote when the user asks, not automatically.
 
 ### Naming and boundaries