constraint-driven-development
Establishes a project's quality bar as a written contract and stops agents quietly lowering it. Interviews the user on which dimensions matter, supplies sane default thresholds when they have no numbe
What it does
Establishes a project's quality bar as a written contract and stops agents quietly lowering it. Interviews the user on which dimensions matter, supplies sane default thresholds when they have no number in mind, records everything in CONSTRAINTS.md, and watches the diff for a weakened bar — new @ts-ignore or eslint-disable suppressions, skipped or deleted tests, assertions stripped out, unimplemented stubs, thresholds edited down. Use when no quality bar is written down, when the user says "set up constraints" or "define our standards", when the user wants dimensions they care about — accessibility, web performance, coverage — set up as enforced constraints, when an agent keeps silencing checks or skipping tests to get to green, when you need a coverage or performance threshold and don't know what number to pick, or when an agent writes more code than anyone will read.
Quality judgment
An exceptionally complete skill: it covers detection, a bounded interview with defaults, a canonical artifact (CONSTRAINTS.md), concrete tooling with install/run commands, lifecycle placement, anti-gaming guards, ratchets, defaults with rationale, rationalizations, red flags, and verification checklists. The only minor gaps are reliance on sibling skills (interview-me, floor-guard reference) whose absence here leaves small dangling references, and no worked end-to-end example of a real session.