elaborate-spec SKILL.md skillA
elaborate-spec from danielvm-git/bigpowers is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add danielvm-git/bigpowers/elaborate-spec@git:20260726.2ca3448Pins git:20260726.2ca3448 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- danielvm-git/bigpowers
- Path
.cline/skills/elaborate-spec/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260726.2ca3448, committed Jul 26, 2026
- Size
- 3,965 bytes
- Repository stars
- 292
- License
- MIT
Refine a rough idea into a clear, detailed specification through dialogue. Does not produce code. Use when user has a vague idea, wants to think through a feature before planning, or needs to turn "I want X" into a concrete spec.
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
# Elaborate Spec Turn a rough idea into a clear specification through focused dialogue. No code is written during this skill — the output is shared understanding and a refined problem statement. > **HARD GATE** — Do NOT proceed with planning or implementation until the problem space is clearly understood. Success criteria, actors, and scope must be explicit before drafting a plan. ## Process ### 1. Listen first Let the user describe their idea in their own words. Do not interrupt or redirect. Take notes on: - The core problem they're trying to solve - Who is affected (actors) - What success looks like to them - Any constraints they've already identified ### 2. Ask clarifying questions Ask one question at a time. Work through these areas: **Problem clarity** - What is the current behavior (or lack of behavior) that prompted this? - Who experiences this problem? How often? - What's the cost of not solving it? **Solution boundaries** - What is explicitly IN scope? - What is explicitly OUT of scope? - Are there existing solutions (internal or external) this replaces or integrates with? **Success criteria** - How will you know this is done? …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_5poj3gabf5lf3hqy/91bb7f8a058451a45699cdafd5c09530e2f859f9b3dcb35bd99e760d16ec99a3.json
Then /plugin install elaborate-spec@markdownregistry-5poj3gabf5lf3hqy in Claude Code. It installs git:20260726.2ca3448, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add danielvm-git/bigpowers/elaborate-spec@sha256:91bb7f8a058451a4The line at the top of this page pins the label git:20260726.2ca3448, 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_5poj3gabf5lf3hqy)
1 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in danielvm-git/bigpowers/elaborate-spec since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of elaborate-spec from somewhere else? Ask it: where did my elaborate-spec come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Jul 26, 2026.
Watch this file (sign in, one email per new version)
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/elaborate-spec/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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 (3965 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
danielvm-git/bigpowers · 292 stars · license MIT · pushed 2026-11-09 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_5poj3gabf5lf3hqy GET https://markdownregistry.com/api/v1/resolve?ref=danielvm-git/bigpowers/elaborate-spec GET https://markdownregistry.com/api/v1/blob/91bb7f8a058451a45699cdafd5c09530e2f859f9b3dcb35bd99e760d16ec99a3
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.