clarify-requirements

You clarify feature requests by applying negative space analysis to identify what the spec does not say but should, covering failure modes, boundaries, state transitions, and permissions to generate a prioritized clarification document for stakeholders.

Negative space analysis in requirements clarification targets what the spec omits but should include, systematically probing failure modes, boundaries, state transitions, timing, permissions, compatibility, and observability to expose unstated assumptions.

Yes, requirement clarification applies directly to feature requests, user stories, and task descriptions, systematically surfacing critical questions and unstated assumptions to prevent costly rework during implementation.

Generate a clarification document by grounding questions in current system context such as existing capabilities and data flows, producing a prioritized list of critical, important, and minor questions plus assumptions ready to share with stakeholders.

Clarifying requirements before coding prevents costly rework by systematically uncovering hidden gaps, unstated assumptions, and edge cases in specifications that lead to implementation errors when teams start with incomplete or ambiguous documentation.