fit-validate-plan SKILL.md skillA
fit-validate-plan from davidteren/intent-engineering is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add davidteren/intent-engineering/fit-validate-plan@git:20261009.55f76eePins git:20261009.55f76ee in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- davidteren/intent-engineering
- Path
plugins/expectation-fit/skills/fit-validate-plan/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261009.55f76ee, committed Oct 9, 2026
- First version recorded
- Oct 9, 2026
- Size
- 11,222 bytes
- Repository stars
- 3
- License
- MIT
Validate a plan, spec, or requirements document against the four expectation-fit lenses before implementation — surfacing surprising designs, non-idiomatic or reinvented approaches, needless complexity/scope, and missing UX decisions (states, flows, IA, accessibility). Returns dimensional 0-10 ratings and the gaps to resolve first. Use when a plan or spec doc exists. Run it on the final plan text, after any document review (for example ce-doc-review) and before implementation. It does not…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Expectation Fit — Plan Validation
Reviews a *document* (plan, spec, or requirements) for the design decisions that, if
left surprising / non-idiomatic / over-complex / UX-incomplete, will derail
implementation. Catches the problem at the cheapest point — before code exists. Fans
out the four lenses in plan mode, each rating its dimensions 0-10 and naming the gaps.
## Argument parsing
`out:`, `prior:` and `lenses:` are shared tokens, defined once in
`${CLAUDE_PLUGIN_ROOT}/references/config-resolution.md` (Shared tokens). Their rows below
list only this skill's difference.
| Token | Effect |
|-------|--------|
| `mode:agent` | Emit JSON; no interactive routing. Writes a report file only with `out:`. |
| `out:<path>` | Shared token. |
| `prior:<report-path>` | Shared token. Turns the run into a re-check: each prior gap is marked closed or still open. |
| `config:<path>` | Override project config directory (walk-up / `EXPECTATION_FIT_CONFIG_DIR` otherwise). |
| `lenses:<list>` | Shared token. |
…Read the whole file at its exact version.
How to install
mdr add davidteren/intent-engineering/fit-validate-plan@sha256:6aa3ffba356e026bThe line at the top of this page pins the label git:20261009.55f76ee, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_aved6gctu57izrai)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, all committed on Oct 9, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261009.55f76ee latest | 2026-10-09 | 55f76ee | 11,222 B | A | view · diff |
| git:20261009.e1a8e27 | 2026-10-09 | e1a8e27 | 11,256 B | A | view · diff |
| git:20261009.ccd3209 | 2026-10-09 | ccd3209 | 11,134 B | A | view · diff |
| git:20261009.5c19224 | 2026-10-09 | 5c19224 | 11,053 B | A | view · diff |
| git:20261009.2085429 | 2026-10-09 | 2085429 | 10,626 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 (11222 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
davidteren/intent-engineering · 3 stars · license MIT · pushed 2026-10-09 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_aved6gctu57izrai GET https://markdownregistry.com/api/v1/resolve?ref=davidteren/intent-engineering/fit-validate-plan GET https://markdownregistry.com/api/v1/blob/6aa3ffba356e026bc4a55eca8daf9eb488e89cced421b054ab7d23f307d9dd3a
Your AI assistant 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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.