constraint-driven-development skillA

This file is byte-identical to the first copy the registry indexed, one of 6 copies on public GitHub. Same content hash, same audit grade.

constraint-driven-development is agent-read markdown (skill) from nota-america/forgecat-agent-profiles: 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 u.

Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.

What the file says

# 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:
…

Read the whole file at its exact version.

How to install

mdr add nota-america/forgecat-agent-profiles/constraint-driven-development@git:20260916.3a6b22e

mdr add nota-america/forgecat-agent-profiles/constraint-driven-development@sha256:06479d4305f286d2

[![mdr](https://markdownregistry.com/badge/art_seceus7lh6a3yvhv.svg)](https://markdownregistry.com/a/art_seceus7lh6a3yvhv)

Versions

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_seceus7lh6a3yvhv
GET https://markdownregistry.com/api/v1/resolve?ref=nota-america/forgecat-agent-profiles/constraint-driven-development
GET https://markdownregistry.com/api/v1/blob/06479d4305f286d23cfb99f5dc85695896785269664e1f6a8d800e3b71e70c10

Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

More from nota-america/forgecat-agent-profiles

Every file in nota-america/forgecat-agent-profiles

Other files named constraint-driven-development

Browse by kind, by grade A, or by owner.