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.
**Ownership and checkbox lifecycle**:
…
The line at the top of this page pins the label git:20261014.d4aca79, 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.
GET https://markdownregistry.com/api/v1/artifacts/art_773fo5dpl2tj47n7
GET https://markdownregistry.com/api/v1/resolve?ref=oryx-labs/oryxos/speckit-checklist
GET https://markdownregistry.com/api/v1/blob/43009036898a3242742336fd3582c2c5909d12fd9a7d6894eb8608b43ccd27ad
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.
oryx-labs/oryxos · .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…
oryx-labs/oryxos · .claude/skills/speckit-clarify/SKILL.md · Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and…
oryx-labs/oryxos · .claude/skills/speckit-constitution/SKILL.md · Create or update the project constitution from interactive or provided principle inputs.
oryx-labs/oryxos · .claude/skills/speckit-converge/SKILL.md · Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new…
oryx-labs/oryxos · .claude/skills/speckit-implement/SKILL.md · Execute the implementation plan by processing and executing all tasks defined in tasks.md
oryx-labs/oryxos · .claude/skills/speckit-plan/SKILL.md · Execute the implementation planning workflow using the plan template to generate design artifacts.
oryx-labs/oryxos · .claude/skills/speckit-tasks/SKILL.md · Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
dceoy/speckit-agent-skills · .cursor/skills/speckit-checklist/SKILL.md · Generate a custom checklist for the current feature based on user requirements.
