requirements-clarity — Claude Code plugin: clarify specs before coding
requirements-clarity — a Claude Code plugin that resolves ambiguous or complex requirements through structured dialogue before implementation starts. Runs when task descriptions are unclear or need refinement.
MIT ★ 2,707 updated 2026-03-05
/plugin marketplace add softaworks/agent-toolkit
/plugin install requirements-clarity@agent-toolkitWhat requirements-clarity does
The plugin brings focused questioning into the workflow: instead of jumping to code, Claude asks targeted questions to pin down what actually needs to be built. Works in Claude Code. Most useful when a spec is sketchy, contains gaps or conflicts, or when it's unclear how a feature fits into the broader codebase.
It uses the built-in skill skills/requirements-clarity. Clear requirements from the start cut rework down: fewer surprises, faster development.
What it helps with
- clarify vague or incomplete feature descriptions
- resolve contradictions in requirements
- dig into how a complex feature should work
- establish acceptance criteria and edge cases
Example prompts for the agent
- Help me figure out what the auth flow requirements should include
- Let's clarify which fields belong in the feedback form
- Walk through how API caching should behave in this context
How to install requirements-clarity
Plugin marketplace
/plugin marketplace add softaworks/agent-toolkit/plugin install requirements-clarity@agent-toolkitStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about requirements-clarity
How do I install requirements-clarity in Claude Code?
Run two commands in order: /plugin marketplace add softaworks/agent-toolkit, then /plugin install requirements-clarity@agent-toolkit.
What does requirements-clarity do?
It clarifies unclear or complex requirements by asking focused questions, so you understand the full scope before coding begins.
When should I use this plugin?
When a spec is incomplete, contradicts itself, or you're unsure how a feature fits into the rest of the system.
Source text
requirements-clarity · MIT
Clarify ambiguous requirements through focused dialogue before implementation. Use when requirements are unclear or features are complex. Skills: skills/requirements-clarity
© softaworks · MIT · softaworks/agent-toolkit