spec-readiness SKILL.md skillA
spec-readiness from eltmon/overdeck is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add eltmon/overdeck/spec-readiness@git:20260618.e501626Pins git:20260618.e501626 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- eltmon/overdeck
- Path
sync-sources/skills/spec-readiness/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260618.e501626, committed Jun 18, 2026
- First version recorded
- May 22, 2026
- Size
- 15,730 bytes
- Repository stars
- 35
- License
- MIT
Evaluate an issue or epic's requirements readiness before development begins. Produces a scored report (0-100) across 5 dimensions with detailed findings, actionable blockers, and a JSON sidecar for dashboards. Works with any issue tracker (Linear, GitHub, GitLab, Rally, Jira). Use a wrapper skill to customize branding and tracker-specific field mappings.
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
# Spec Readiness — Orchestrator
## Philosophy
The most important work on a feature is the PRD/spec, not the implementation. Every major overrun traces back to **requirements incomplete when development started.** This skill measures requirements maturity as a **leading indicator**.
## Wrapper Architecture
This is the **core scoring engine**. It is designed to be wrapped by a thin customization layer.
### How Wrapping Works
A wrapper skill overrides branding, tracker bindings, and field mappings by providing a `config.yaml`:
```
1. Check: Does ~/.overdeck/skills/spec-readiness-*/config.yaml exist?
2. If yes: Load tracker bindings, field mappings, branding, conventions
3. If no: Use defaults (generic branding, auto-detect tracker)
```
### Wrapper Config Schema
```yaml
# ~/.overdeck/skills/spec-readiness-mycompany/config.yaml
tracker:
type: linear | github | gitlab | rally | jira
tools:
get_issue: "mcp__linear__get_issue"
list_child_issues: "mcp__linear__list_issues"
get_comments: "mcp__linear__list_comments"
search_issues: "mcp__linear__list_issues"
get_relations: "mcp__linear__get_issue" # with includeRelations=true
…Read the whole file at its exact version.
How to install
mdr add eltmon/overdeck/spec-readiness@sha256:6ecc76db4fe1a4baThe line at the top of this page pins the label git:20260618.e501626, 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_pvejqfgypgq5q6uz)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between May 22, 2026 and Jun 18, 2026, about one every 27 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260618.e501626 latest | 2026-06-18 | e501626 | 15,730 B | A | view · diff |
| git:20260522.817c2c7 | 2026-05-22 | 817c2c7 | 15,738 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 (15730 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
eltmon/overdeck · 35 stars · license MIT · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_pvejqfgypgq5q6uz GET https://markdownregistry.com/api/v1/resolve?ref=eltmon/overdeck/spec-readiness GET https://markdownregistry.com/api/v1/blob/6ecc76db4fe1a4babb89548ebe0d20e4a82d35e6a93f87c568573962581f21c3
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.