dev-step--clarify-requirements

To clarify task requirements and reduce ambiguity, you need to elicit missing details from stakeholders and document them in a standardized template. This structured output approach formalizes vague task requests into precise, testable requirements.

The best way to formalize a vague product feature request is to run a clarification dialogue that gathers acceptance criteria and non-functional requirements. This produces a complete formal requirements document ready for stakeholder review.

You can generate a structured requirements document by providing a task description and known constraints. The Skill processes these inputs to produce a formal requirements block listing each requirement and its description alongside a keywords section.

Yes, you can use structured questioning to define requirements for software and research tasks. The clarification process applies across product, software, and research domains by proactively asking questions to resolve ambiguity and identify missing information.

Yes, clarifying requirements before development prevents scope creep by transforming vague task requests into precise, testable definitions. Eliciting essential details upfront establishes strict boundaries and formalizes stakeholder expectations.

The structured task definition output uses a standardized template featuring a keywords section and a formal requirements block. This formatted requirements document lists each requirement alongside its description for stakeholder review.