Generate a custom checklist for the current feature based on user requirements.
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
## Checklist Purpose: "Unit Tests for English"
**CRITICAL CONCEPT**: Checklists are **UNIT TESTS FOR REQUIREMENTS WRITING** - they validate the quality, clarity, and completeness of requirements in a given domain.
**NOT for verification/testing**:
- ❌ NOT "Verify the button clicks correctly"
- ❌ NOT "Test error handling works"
- ❌ NOT "Confirm the API returns 200"
- ❌ NOT checking if code/implementation matches the spec
**FOR requirements quality validation**:
- ✅ "Are visual hierarchy requirements defined for all card types?" (completeness)
- ✅ "Is 'prominent display' quantified with specific sizing/positioning?" (clarity)
- ✅ "Are hover state requirements consistent across all interactive elements?" (consistency)
- ✅ "Are accessibility requirements defined for keyboard navigation?" (coverage)
- ✅ "Does the spec define what happens when logo image fails to load?" (edge cases)
**Metaphor**: If your spec is code written in English, the checklist is its unit test suite. You're testing whether the requirements are well-written, complete, unambiguous, and ready for implementation - NOT whether the implementation works.
## User Input
```text
$ARGUMENTS
```
…
The line at the top of this page pins the label git:20260920.e596793, 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.
A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (20420 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
GitHub
pisberg/vibetags · 25 stars · license MIT · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7erp2vbm4cg43vrs
GET https://markdownregistry.com/api/v1/resolve?ref=pisberg/vibetags/speckit-checklist
GET https://markdownregistry.com/api/v1/blob/812b2a102310470141b313670a51e7f33fe4f673a3b8c3d97ddff4abce2e5fbd
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.
pisberg/vibetags · .claude/skills/add-annotation/SKILL.md · Add a new @AI... guardrail annotation to VibeTags — register it in GuardrailAnnotations, then wire it through every…
pisberg/vibetags · .claude/skills/add-platform/SKILL.md · Add support for a new AI coding tool, IDE, PR-reviewer, or context-packer to VibeTags — wire a new generated output…
pisberg/vibetags · .claude/skills/bump-dependencies/SKILL.md · Bump every third-party dependency, plugin and toolchain pin in VibeTags to its latest stable release, mirror the pins…
pisberg/vibetags · .claude/skills/consultation-loop/SKILL.md · Pre-push adversarial interrogation of the current branch's diff by a fresh reviewer with no memory of writing it - five…
pisberg/vibetags · .claude/skills/consumer-regression-suite/SKILL.md · Build every downstream consumer of VibeTags against a chosen VibeTags version and report which ones actually pass. Use…
pisberg/vibetags · .claude/skills/correctness-hunt/SKILL.md · Run a bug hunt against this repository under a fixed work order - baseline the suite, hunt with named bug-shape lenses…
pisberg/vibetags · .claude/skills/load-tests/SKILL.md · Run the VibeTags benchmark harness in load-tests/ and report the numbers honestly — annotation-volume and memory…
pisberg/vibetags · .claude/skills/release/SKILL.md · Cut a new VibeTags release — bump the version everywhere, update the CHANGELOG, open the release PR, and create the…
pisberg/vibetags · .claude/skills/speckit-analyze/SKILL.md · Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after…
pisberg/vibetags · .claude/skills/speckit-clarify/SKILL.md · Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and…
pisberg/vibetags · .claude/skills/speckit-constitution/SKILL.md · Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent…
dceoy/speckit-agent-skills · .cursor/skills/speckit-checklist/SKILL.md · Generate a custom checklist for the current feature based on user requirements.
