summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDrew Ritter <drew@primeradiant.com>2026-07-20 16:38:11 -0700
committerDrew Ritter <drew@primeradiant.com>2026-07-20 16:38:11 -0700
commitd1f1ae1f1ed1e1ee82c65e098694d0fb4bb98446 (patch)
tree9c26f880db695165e6053be40c567f067f718918
parent4334ff508ae8dd0e8fd394f921a2a40a90904369 (diff)
sdd: never commit the plan workspace to the project repoexp/loop-econ-rd
-rw-r--r--skills/subagent-driven-development/SKILL.md5
1 files changed, 5 insertions, 0 deletions
diff --git a/skills/subagent-driven-development/SKILL.md b/skills/subagent-driven-development/SKILL.md
index 52102f8..0bd9422 100644
--- a/skills/subagent-driven-development/SKILL.md
+++ b/skills/subagent-driven-development/SKILL.md
@@ -137,6 +137,11 @@ a ledger file, not only in todos.
verbatim into `<workspace>/constraints.md`. Every dispatch's binding
constraint values paste from that file — the plan itself stays closed
after Setup, even across compaction.
+- The workspace is never committed to the project repo. Do not `git add`
+ anything under it, and never write a commit whose purpose is to record,
+ correct, or tidy a workspace artifact — reports and ledgers are session
+ records, not deliverables. If the repo lacks a `.gitignore` entry for
+ `.superpowers/`, leave the directory untracked rather than committing it.
- The ledger is your recovery map: the commits it names exist in git even
when your context no longer remembers creating them. After compaction,
trust the ledger and `git log` over your own recollection.