Clarify user requirements with one question at a time.
npx skills add https://github.com/tasai-lab/fractal-dev-workflow --skill questioning
Please help me install this Agent Skill. Skill: questioning Source: https://github.com/tasai-lab/fractal-dev-workflow/tree/main/skills/questioning Command: npx skills add https://github.com/tasai-lab/fractal-dev-workflow --skill questioning
This skill helps teams clarify requirements immediately after receiving a task, reducing back-and-forth and avoiding costly rework during later phases.
Begin by receiving a task description and start asking one clarifying question at a time with 2–4 options and impact descriptions.
High-intent search queries and answers about installing and using this skill.
To clarify product requirements before planning, you need structured requirement elicitation to analyze the task, identify gaps, and surface ambiguities. This prevents costly rework by locking down acceptance criteria and aligning the team before execution begins.
The best way to resolve ambiguous requirements in early-stage development is through a question-driven elicitation loop. If answers remain unclear, automatically investigate the codebase and re-ask with more precise options to ensure completion criteria are met.
You can gather requirements effectively by asking a single clarifying question at a time. Provide 2–4 options with impact descriptions for each question to guide stakeholder decisions and reduce back-and-forth communication during the workflow.
Yes, a question-driven workflow is specifically designed for phased development requirement gathering. It applies to early-stage product tasks and planning phases, enforcing a requirement elicitation loop to ensure completion criteria before advancing to investigation.
Costly rework during later development phases often happens because requirements were not fully clarified immediately after receiving a task. Failing to identify gaps and surface ambiguities before execution leads to misaligned acceptance criteria and extensive corrections.
pingmepiGenerate a structured 7-section product brief from a business statement.
realsigridjinCreate a structured Product Requirements Document from a project description.
g1331Explore ideas and clarify requirements within OpenSpec workflows.
shin0720Generate EARS-format requirements and implementation plans from codebase analysis.
