sdd: verify mechanical constraints at commit time

This commit is contained in:
Drew Ritter
2026-07-20 02:14:22 -07:00
parent aaa0a8f0f4
commit 70c9a9a26a

View File

@@ -42,8 +42,12 @@ Subagent (general-purpose):
2. Write tests (following TDD if task says to) 2. Write tests (following TDD if task says to)
3. Verify implementation works 3. Verify implementation works
4. Commit your work 4. Commit your work
5. Self-review (see below) 5. Immediately after each commit, verify it against the Binding Constraint
6. Report back 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] Work from: [directory]
@@ -102,6 +106,10 @@ Subagent (general-purpose):
- Did I only build what was requested? - Did I only build what was requested?
- Did I follow existing patterns in the codebase? - 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:** **Testing:**
- Do tests actually verify behavior (not just mock behavior)? - Do tests actually verify behavior (not just mock behavior)?
- Did I follow TDD if required? - Did I follow TDD if required?