Convert ambiguous user requests into detailed, testable specifications.
npx skills add https://github.com/yash-gadodia/claude-init --skill clarify-yash-gadodia
Please help me install this Agent Skill. Skill: clarify Source: https://github.com/yash-gadodia/claude-init/tree/main/templates/skills/clarify Command: npx skills add https://github.com/yash-gadodia/claude-init --skill clarify-yash-gadodia
This Skill helps in converting ambiguous or multi-interpretable requests into clear, testable specifications, ensuring that the intent and requirements are well-defined before implementation.
Use the /clarify command to start the process of turning a vague request into a structured spec.
High-intent search queries and answers about installing and using this skill.
Requirement clarification transforms ambiguous requests into testable specifications by guiding you through a structured dialogue to explore context, clarify intent, propose approaches, and write a detailed spec for user approval.
Requirement clarification is the process of converting ambiguous requests into clear, testable specifications. You need it before code review or implementation to ensure intent and requirements are well-defined and multi-interpretable requests are resolved.
Writing a testable spec involves exploring the context of the feature request, clarifying the underlying intent, proposing technical approaches, and drafting the specification. An automated review step then ensures the spec is complete and testable before user approval.
Yes, you can automate specification review to verify completeness, testability, and scope adherence. An automated spec reviewer evaluates the drafted requirements against these criteria before presenting the final spec for user approval.
The best way to structure a requirement clarification dialogue is to sequentially explore the context, clarify the user's intent, propose technical approaches, and write the specification. This structured process ensures ambiguous requests become testable specs.
Your specification fails to capture project intent when requirement clarification is skipped, leaving ambiguous requests unresolved. Using a structured dialogue to explore context and clarify intent before writing the spec ensures the actual requirements are well-defined.
BellaBeTransform Canvas strategy into structured product requirements and user stories.
nextbysamExecutes approved specification proposals sequentially with TodoWrite task tracking and test validation.
osovvGenerate structured implementation plans from approved spec.xml files.
slinkardbrandonEvaluate technical specifications for buildability and implementability.
