harness-discovery

To turn vague project ideas into actionable plans, apply Socratic questioning to clarify ambiguous project goals and constraints. This structured discovery process produces a concise summary and defines the next actionable workflow step.

The best way to clarify ambiguous project goals during early-stage planning is using Socratic questioning to expose purpose and success criteria. This method generates a structured discovery summary capturing constraints and the chosen architectural direction.

Yes, you can leverage optional explorer subagents for bounded repository investigations when local context is insufficient. They operate on demand to gather missing codebase context required to decide between multiple architectural approaches.

Deciding between multiple architectural approaches requires Socratic questioning to expose project constraints and trade-offs. This produces a structured discovery output that captures the chosen direction and defines the next workflow step.

Use a discovery workflow for software planning when the next move is unclear or you are initiating a new feature in a codebase. It helps establish shared understanding of problem statements and acceptance criteria before large work begins.