exploring

To clarify vague project requirements, use Socratic exploration to transform incomplete prompts into shared understanding through structured discovery dialogue, ensuring alignment before advancing to specs. This prevents wasted effort by requiring user confirmation at each step.

Scope decomposition is needed when a request covers multiple features or independent subsystems. It detects independent subsystems, recommends breaking complex work into manageable sub-projects, and confirms readiness for the next phase before committing to a proposal.

The best way to turn a vague feature request into a scoped proposal is through implementation research guidance, which explains when to gather evidence and compare approaches before safely handing off to the proposing phase.

Yes, you can compare trade-offs and assess scope limits before committing to a proposal. The exploration phase satisfies requirements for scope assessment and trade-off comparison, transitioning only after user alignment is explicitly achieved.

Your project prompt needs context gathering because unclear, incomplete, or multi-faceted requests must be deeply understood before any implementation begins. Socratic exploration provides this context, preventing wasted effort and rework downstream.