From 70c9a9a26ada7bd4059c56b3ad993d55fb3f28f5 Mon Sep 17 00:00:00 2001 From: Drew Ritter Date: Mon, 20 Jul 2026 02:14:22 -0700 Subject: [PATCH] sdd: verify mechanical constraints at commit time --- .../implementer-prompt.md | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/skills/subagent-driven-development/implementer-prompt.md b/skills/subagent-driven-development/implementer-prompt.md index ab03c487..119a1c65 100644 --- a/skills/subagent-driven-development/implementer-prompt.md +++ b/skills/subagent-driven-development/implementer-prompt.md @@ -42,8 +42,12 @@ Subagent (general-purpose): 2. Write tests (following TDD if task says to) 3. Verify implementation works 4. Commit your work - 5. Self-review (see below) - 6. Report back + 5. Immediately after each commit, verify it against the Binding Constraint + Values above (commit-message rules, naming rules, fixed literals) while + history is still local. A miss is cheap now — amend or forward-fix at + once — and expensive after your work is delivered. + 6. Self-review (see below) + 7. Report back Work from: [directory] @@ -102,6 +106,10 @@ Subagent (general-purpose): - Did I only build what was requested? - Did I follow existing patterns in the codebase? + **Constraints:** + - Does every commit message satisfy the Binding Constraint Values exactly? + - Did I reproduce mandated literals from the constraint text, not from memory? + **Testing:** - Do tests actually verify behavior (not just mock behavior)? - Did I follow TDD if required?