Claude Code Requirements Clarity Skill for Finding Gaps Before Coding
Check an ambiguous request for missing scope, interactions, technical constraints, and business value. Clarify high-impact gaps before drafting verifiable requirements.
中文Install in Claude Code
Use Claude Code with the pinned skill directory and a project participant who can confirm decisions. Bring the original request and known constraints.
- Get the complete `cli-tool/components/skills/productivity/requirements-clarity` directory from the pinned GitHub checkout.
- Copy it under the target project's `.claude/skills/`. Confirm `.claude/skills/requirements-clarity/SKILL.md`, open Claude Code at the project root, and call `/requirements-clarity`.
Example task
The request is Add reading-list export. Only administrators may export. Ask about the file format, current filters versus all rows, and what happens when the list is empty.What to check
The first round should cover material scope and edge cases. Once confirmed, record the selected format, administrator access, and empty-list behavior as acceptance criteria.
Original SKILL.md on GitHub · Updated
Frequently asked question
Why ask only a few questions at a time?
Resolve decisions that can change the design first. Use those answers to narrow later questions and avoid collecting irrelevant detail.