constraint-driven-development
Establishes a project's quality bar as a written contract
by addyosmaniFree
Description
constraint-driven-development is an agent skill from Addy Osmani's agent-skills collection that writes a project's quality bar down as a contract, so that an agent cannot quietly lower it. Other skills in the collection describe what good looks like, but that guidance lives in prose and does not survive the end of a session. This skill produces a written record of the project's bar, with numbers, that outlives the conversation and can be checked mechanically. The reasoning is that an agent writes more in an afternoon than a person can read in a week, so the judgment has to move out of a reviewer's head and into checks that run around the work. Those checks need numbers the team has chosen, and they need to run close enough to the work that the agent can fix its own output. The skill interviews the user on which dimensions matter and suggests sensible defaults. Constraint-driven development decides what good enough to ship means before the argument happens in a pull request.…
Highlights
- Quality bar written as a checkable contract
- Numbers chosen by the team
- Interview on which dimensions matter
- Checks that run around the agent's work
Ratings & Reviews
No ratings yet
Be the first to rate constraint-driven-development.
People also visit
migrate-to-shoehorn
Migrate test files from `as` type assertions to @total-typescript/shoehorn
benchmark-optimization-loop
Convert 'make it faster' requests into a bounded measured optimization loop
cpp-testing
Use only when writing/updating/fixing C++ tests, configuring GoogleTest/CTest
constraint-driven-development FAQ
What does the constraint-driven-development skill do?
It writes a project's quality bar as a written, numeric contract, so an agent cannot quietly lower it.
How do I install it?
Run: npx skills add https://github.com/addyosmani/agent-skills --skill constraint-driven-development
Who decides the numbers?
The team does. The skill interviews the user on which dimensions matter and supplies sensible defaults where they are needed.
How does it relate to other skills in the collection?
Spec-driven development says what to build and test-driven development proves it works. This skill sets what good enough to ship means.
What security checks has it passed?
skills.sh lists three audits: Gen Agent Trust Hub Pass, Socket Pass and Snyk Pass.
What are the best constraint-driven-development alternatives?
Popular alternatives to constraint-driven-development include migrate-to-shoehorn, tdd and agent-self-evaluation. See all constraint-driven-development alternatives