spec-interview SKILL.md skillA
spec-interview from jellydn/my-ai-tools is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add jellydn/my-ai-tools/spec-interview@git:20261007.163951ePins git:20261007.163951e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- jellydn/my-ai-tools
- Path
configs/amp/plugins/my-ai-tools-skills/skills/spec-interview/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261007.163951e, committed Oct 7, 2026
- First version recorded
- Aug 14, 2026
- Size
- 8,425 bytes
- Repository stars
- 128
- License
- MIT
Clarify requirements through targeted questions — uncovers unknown unknowns in specs.
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 Interview ## When to Use Use this skill when: - Feature requirements are vague or incomplete - You have a general idea but lack specifics - Stakeholders said "you know what I mean" - The spec has obvious gaps - Making assumptions that could be wrong ## What It Does The agent interviews you to **uncover unknown unknowns** in your feature specification, focusing on questions that would change architectural decisions. ## How to Execute ### Step 1: Review Initial Spec Analyze what the user provided: - Explicit requirements (what they said) - Implicit requirements (what they assumed) - Missing details - Ambiguous areas ### Step 2: Categorize Gaps Identify question categories: **Scope & Boundaries**: - What's in scope vs out of scope? - Edge cases to handle? - MVP vs future iterations? **User Experience**: - What happens when...? - Error states and recovery? - Loading and async states? **Technical Decisions**: - Performance requirements? - Data consistency needs? - Integration points? - Security considerations? **Architecture Impact**: - Does this change existing patterns? - New abstractions needed? - Migration strategy for existing data? …
Read the whole file at its exact version.
How to install
mdr add jellydn/my-ai-tools/spec-interview@sha256:a782d800decaaa78The line at the top of this page pins the label git:20261007.163951e, 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_iysqisq5kt7sxufx)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Aug 14, 2026 and Oct 7, 2026, about one every 54 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261007.163951e latest | 2026-10-07 | 163951e | 8,425 B | A | view · diff |
| git:20260814.d1987f5 | 2026-08-14 | d1987f5 | 8,320 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 (8425 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
jellydn/my-ai-tools · 128 stars · license MIT · pushed 2026-11-09 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_iysqisq5kt7sxufx GET https://markdownregistry.com/api/v1/resolve?ref=jellydn/my-ai-tools/spec-interview GET https://markdownregistry.com/api/v1/blob/a782d800decaaa7817fc299c4122dff2373e32705b57cecb59bcade6e12867a1
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.
More from jellydn/my-ai-tools
Every file in jellydn/my-ai-tools