kiln-clarify

To resolve ambiguities in feature requirements before planning, you can use a structured clarification workflow that detects gaps across functional scope, data model, UX flow, and non-functional constraints, ensuring underspecified requirements are fully addressed before development begins.

The best way to clarify underspecified specs interactively is through a one-question-at-a-time loop. This workflow generates a prioritized queue of up to five clarifying questions, guiding responses incrementally to ensure testable updates to the specification.

You log clarifications by automatically creating and updating a dedicated Clarifications section within the active spec. The workflow logs per-session bullets and applies atomic, incremental updates to the specification as answers are accepted.

Yes, you can use this structured questioning workflow on any active feature specification. It operates directly on the existing spec to generate prioritized questions, update accepted answers, and report completion with touched sections and next steps.

Feature planning fails when requirements are underspecified because unaddressed ambiguities in scope, data models, and constraints lead to misaligned development. A structured clarification workflow prevents this by resolving these gaps before planning begins.