constraint-driven-development

Editorial and source context

What this Skill does

Constraint Driven Development is a source-indexed Agent Skill for development & engineering work. Based on the SKILL.md description, it focuses on establishes a project's quality bar as a written contract and stops agents quietly lowering it. Use the linked GitHub file to confirm scope and prerequisites before enabling it.

What the author says

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 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.

Compatibility and requirements

• Use an agent runtime that supports Agent Skills and the linked SKILL.md format.
• Confirm the source repository's tools, SDKs, and platform prerequisites for ui and frontend work.

How to install or import it

• Open the linked GitHub SKILL.md and review its scope and setup instructions.
• Install or import the skill using the agent runtime's documented workflow.
• Run a small, non-sensitive test and verify the output before broader use.

Permissions and risks

• Review every command, file path, network request, dependency, and credential scope before enabling it.
• GitHub stars indicate popularity, not safety or correctness; validate the source and test with non-sensitive data.

Example workflows

• Ask an AI agent to apply Constraint Driven Development to ui and frontend work described in the source record.
• Have the agent state assumptions, required tools, and expected output before using this development & engineering skill.
• Compare the result with the linked GitHub SKILL.md and verify it against your project requirements.