Clarify ambiguous product requirements in Claude Code
Find language that cannot become an acceptance criterion and record the original wording, ambiguity type, proposed definition, and confirmation status.
中文Install in Claude Code
A Claude Code project and a written requirement. Keep proposals pending until the product owner confirms.
- Review `.claude/skills/requirements-clarify/SKILL.md` and its requirements at the pinned GitHub commit.
- Create `.claude/skills/requirements-clarify/` in your project and save the reviewed file as `.claude/skills/requirements-clarify/SKILL.md`.
- Start Claude Code from that project's root, then select `/requirements-clarify` in the slash menu.
Example task
The preview requirement says `Show the report quickly` and applies to a local summary preview. No finish event or passing threshold is agreed. Consider 800 ms as a proposal.What to check
Output pending item `AMB-001: preview <= 800 ms`. Record the original and the undefined speed target. Propose timing from pressing Preview to seeing the first screen. Ask the product owner to confirm.
Original SKILL.md on GitHub · Updated
Frequently asked question
How can a word like quickly become testable?
Keep the original text, identify the missing threshold or test conditions, and propose a measurable timing target with a measurement method. Add it to the specification after confirmation.