feature-requirement-clarification SKILL.md skillA
feature-requirement-clarification from robsonkades/agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add robsonkades/agent-skills/feature-requirement-clarification@git:20261016.c769bd8Pins git:20261016.c769bd8 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- robsonkades/agent-skills
- Path
skills/feature-requirement-clarification/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261016.c769bd8, committed Oct 16, 2026
- First version recorded
- Sep 6, 2026
- Size
- 11,244 bytes
- Repository stars
- 3
- License
- Apache-2.0
Deciding what to ask the user about a feature, when to ask it, and what stops work until it is answered: reusing supplied answers and checking relevant evidence first, pricing each question by what changes if the answer is the other one, batching questions into rounds instead of interrogating, and marking the few that are genuinely blocking. Use when a feature request is ambiguous and the choice is between asking and assuming, when a long list of questions is about to be sent at once, when…
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
# Feature Requirement Clarification ## Purpose Two opposite failures, and both are expensive. An agent that never asks builds a correct implementation of a requirement nobody agreed, and the gap surfaces when it is costly to close. An agent that asks everything turns a feature request into a questionnaire, gets vague answers because the user has stopped reading by question nine, and still ends up guessing. The discriminator is not politeness or thoroughness. It is **consequence**: a question earns a user's attention only when the two answers lead to different work, and only when nothing else available can settle the missing intent, evidence or authority. A focused search can establish a bounded gap; it need not prove that no answer exists anywhere. ## Workflow 1. **Start from the unknowns**, not from a checklist. Trace each question to an existing unknown or record the newly discovered gap; a small Inline task needs only a concise entry. 2. **Reuse supplied answers and the context report.** Check accepted session decisions and applicable policy/contract evidence before asking again. Run a focused repository check only when it could …
Read the whole file at its exact version.
How to install
mdr add robsonkades/agent-skills/feature-requirement-clarification@sha256:f4247a59156800fbThe line at the top of this page pins the label git:20261016.c769bd8, 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_idu4kv6okflq7luw)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 6, 2026 and Oct 16, 2026, about one every 10 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261016.c769bd8 latest | 2026-10-16 | c769bd8 | 11,244 B | A | view · diff |
| git:20260927.9ecadfd | 2026-09-27 | 9ecadfd | 10,469 B | A | view · diff |
| git:20260923.832673e | 2026-09-23 | 832673e | 9,196 B | A | view · diff |
| git:20260911.37b054b | 2026-09-11 | 37b054b | 8,862 B | A | view · diff |
| git:20260906.e6ad4bd | 2026-09-06 | e6ad4bd | 8,529 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 (11244 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
robsonkades/agent-skills · 3 stars · license Apache-2.0 · pushed 2026-10-28 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_idu4kv6okflq7luw GET https://markdownregistry.com/api/v1/resolve?ref=robsonkades/agent-skills/feature-requirement-clarification GET https://markdownregistry.com/api/v1/blob/f4247a59156800fb570a9510550b756ec00e8a0b4409ec0cc3d05134995a8d43
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.