constraintslisted

> Source: [addyosmani/agent-skills - skills/constraint-driven-development](https://github.com/addyosmani/agent-skills/tree/main/skills/constraint-driven-development), adapted. # Constraints Prose standards do not survive the end of a session. This skill produces a written record of this repo's bar, with numbers, that can be checked mechanically. The interview needs a live user. In a non-interactive context (CI, `/loop`, autonomous runs), apply only the floor, note that you did, and flag the rest for a human. ## Process ### 1. Detect before you ask Never ask what you can read. Check `package.json`, the test runner and its coverage output, `eslint.config.*` or `biome.json`, `.github/workflows/`, and `.claude/`. Report what you found in two lines, then ask only what is left. ### 2. Four questions, each with a default Follow the one-question-per-turn discipline from `rules/communication.md`. Every question has a default, so "I don't know" still produces a working config. Stop at four. ```text Q1: Beyond the floor, which of these do you want enforced? (a) coverage on new code (b) security scanning (c) performance budgets (d) accessibility (e) architecture boundaries GUESS: (a) and (b). DEFAULT if unsure: (a) and (b). Note the cost: (c) and (d) need a running URL, (e) needs a rules file. Q2: When a check fails mid-task, block or warn? GUESS: block. DEFAULT: block on the floor, warn on the rest for two weeks. Q3: Target numbers in mind, or measure today and hol