constraint-driven-development

# Constraint-Driven Development ## Overview Other skills in this pack describe what good looks like. `code-review-and-quality` gives you five axes. `test-driven-development` gives you a cycle. `security-and-hardening` gives you a threat list. All of that lives in prose the agent reads and may or may not follow, and none of it survives the end of the session. This skill produces something different: a written record of **this project's** bar, with numbers, that outlives the conversation and can be checked mechanically. The reason matters. When you wrote the code, reading it told you whether it was any good. An agent writes more in an afternoon than you will read that week, so the judgement moves out of your head and into checks that run around the loop. Those checks need to exist, they need numbers you actually chose, and they need to fire close enough to the work that the agent fixes its own output. Spec-driven development says what to build. Test-driven development proves it works. Constraint-driven development defines what "good enough to ship" means, before anyone argues about it in a pull request. ## When to Use Apply this skill when: - Starting a project or a significant feature and no quality bar is written down - The user asks to "set up constraints", "add quality gates", "define our standards", or "stop the agent shipping junk" - An agent is producing volume nobody is reading line by line - CI has checks but nobody can say which ones block a merge and which on...