implement-with-tdd skillA
implement-with-tdd is agent-read markdown (skill) from stevepolitodesign/skills: Implement a SPEC, plan, or feature outside-in, with TDD..
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
# Implement with TDD Work from the outside in and let each failure name the next move. Stop at shameless green; a later step refactors. The discipline exists because you're fluent enough to write plausible code for almost anything, and plausible isn't correct. A failing test tells them apart. ## What you were handed The thing to build: `$ARGUMENTS` If that's empty, ask. If it's a path, read it. Take the acceptance criteria as the scope. Those are behavior, and behavior is what you can test. A suggested design, a test path, an ordering: that's a guess from a session that never ran the suite. Yours will run it, so your evidence is better. Where the repo contradicts the plan the repo is right — say so rather than diverge quietly. A `## Where to look` section is the exception to that distrust, not to the scope rule. Those paths are where a prior session already found the relevant code, so they save you the search and not the judgment: open them before you go looking for anything else, and treat nothing on the list as work you owe. The criteria are still the whole scope. If a path is gone or turns out to be irrelevant, skip it and say so in the report — don't edit the SPEC. …
Read the whole file at its exact version.
How to install
mdr add stevepolitodesign/skills/implement-with-tdd@git:20260916.114dbbfmdr add stevepolitodesign/skills/implement-with-tdd@sha256:9661eb4b400642b1Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_xziutxunmg3u2dhm)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260916.114dbbf latest | 2026-09-16 | 114dbbf | 7,160 B | A | view · diff |
| git:20260915.6a51426 | 2026-09-15 | 6a51426 | 6,682 B | A | view · diff |
| git:20260903.d25ad65 | 2026-09-03 | d25ad65 | 6,713 B | A | view · diff |
| git:20260824.84f78a9 | 2026-08-24 | 84f78a9 | 6,923 B | A | view · diff |
| git:20260820.9f0498a | 2026-08-20 | 9f0498a | 6,285 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7160 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
stevepolitodesign/skills · 3 stars · license none · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_xziutxunmg3u2dhm GET https://markdownregistry.com/api/v1/resolve?ref=stevepolitodesign/skills/implement-with-tdd GET https://markdownregistry.com/api/v1/blob/9661eb4b400642b19e7f874044ea3bbd79ef4f120f9d69ce9b5617f32685d235
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.