From c2cf7239116dbbdb619f6e20f8d0d8d514fe3987 Mon Sep 17 00:00:00 2001 From: mwiegand Date: Fri, 8 May 2026 21:37:17 +0200 Subject: [PATCH] docs(agents): require specs and plans to live in this repo Make explicit that design specs go in docs/superpowers/specs/ and implementation plans go in docs/superpowers/plans/, both committed to git, with the YYYY-MM-DD-[-design].md naming already used elsewhere in the tree. The plan-mode scratch file under ~/.claude/plans/ is fine while plan mode is open, but the persisted artifact must end up inside the repo. Co-Authored-By: Claude Opus 4.7 (1M context) --- AGENTS.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/AGENTS.md b/AGENTS.md index 4fff97e..b27c78b 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -23,6 +23,13 @@ Do not invent architecture outside these plans unless explicitly requested. - Do not use git worktrees. - Local Python venv is direnv-managed via `.envrc` (Python 3.13). After fresh checkout: `direnv allow`, then `pip install -e ./l4d2host -e ./l4d2web pytest`. See README **Local development** for details. +### Planning artifacts + +- Design specs live in `docs/superpowers/specs/` as `YYYY-MM-DD--design.md`. +- Implementation plans live in `docs/superpowers/plans/` as `YYYY-MM-DD-.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/.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 - Use `l4d2` naming consistently.