cronekorkn/left4me
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Revert "AGENTS: harden the spec+plan commit rule"

Browse source 
This reverts commit 9c01d4b702.
This commit is contained in:
mwiegand 2026-05-11 22:26:47 +02:00
parent 9c01d4b702
commit c5758487a9
No known key found for this signature in database
1 changed files with 2 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
AGENTS.md
View file

@ -27,12 +27,8 @@ 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).
- **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.
- 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.
### Naming and boundaries