summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDrew Ritter <drew@primeradiant.com>2026-07-20 02:55:09 -0700
committerDrew Ritter <drew@primeradiant.com>2026-07-20 02:55:09 -0700
commit374ea4f14617322bea42d92250584493867dfc7d (patch)
tree3771f9631709c8a5caa85c4e31ba1cd70e8e4f92
parent2e11d4c79aef9d70b207f1619779dffab06956f1 (diff)
writing-plans: keep the commit caveat out of the task templateexp/loop-econ-r
-rw-r--r--skills/writing-plans/SKILL.md7
1 files changed, 2 insertions, 5 deletions
diff --git a/skills/writing-plans/SKILL.md b/skills/writing-plans/SKILL.md
index 898fcda..fd11aba 100644
--- a/skills/writing-plans/SKILL.md
+++ b/skills/writing-plans/SKILL.md
@@ -127,9 +127,9 @@ Expected: PASS
git add tests/path/test.py src/path/file.py
git commit -m "feat: add specific feature"
```
+````
Commit messages describe the change. Never mandate session boilerplate — trailers, bylines, model names — as a per-commit rule; what your session stamps on its commits is not a requirement of the work.
-````
## No Placeholders
@@ -151,10 +151,7 @@ After writing the complete plan, look at the spec with fresh eyes and check the
**3. Type consistency:** Do the types, method signatures, and property names you used in later tasks match what you defined in earlier tasks? A function called `clearLayers()` in Task 3 but `clearFullLayers()` in Task 7 is a bug.
-**4. Constraint hygiene:** Does any Global Constraint mandate a per-commit
-cosmetic absolute, name the authoring model or session, or assert an
-environment fact (version floor, platform, path) you did not verify? Cut
-or verify it.
+**4. Constraint hygiene:** Does any Global Constraint mandate a per-commit cosmetic absolute, name the authoring model or session, or assert an environment fact (version floor, platform, path) you did not verify? Cut or verify it.
If you find issues, fix them inline. No need to re-review — just fix and move on. If you find a spec requirement with no task, add the task.