start-discussion

To clarify vague software ideas before implementation, use a guided discovery conversation that applies reflective questioning to uncover constraints and desired outcomes, ensuring you determine whether the work is a feature, refactor, or bug investigation.

Feature triage and requirements discovery are needed during early-stage conversations when you have an ambiguous concern or idea. This exploratory process surfaces the real problem and desired outcome to determine if the work warrants action or no action at all.

You can explore an ambiguous problem without premature file creation by maintaining a verbal-only discussion that synthesizes multi-turn context. This approach captures constraints and intent through conversation design, explicitly avoiding ADR drafting until the problem is clear.

The best way to determine if an idea is a new feature or a refactor is through intent clarification and routing. After several turns of exploratory conversation, the likely shape of the work is identified and the right handoff path is offered.

Yes, you can use exploratory conversation design for early-stage software planning. It guides ambiguous problem discussions by reflecting your situation and asking focused open-ended questions to gather context before handing off into planning workflows.

You should avoid using a discovery conversation when you already have clear constraints and desired outcomes. This process is strictly for early-stage exploration where intent is ambiguous, and it requires handoff into feature-start workflows once the problem becomes clear.