agentic-clarification

To resolve ambiguity in a vague software request, initiate a structured clarification loop that asks focused questions one at a time while concurrently exploring the codebase. This progressively narrows scope and produces a concrete context brief for precise planning.

You can explore the codebase while clarifying requirements by deploying subagents for parallel code exploration during the questioning loop. This surfaces technical constraints and context concurrently, summarizing findings into actionable decisions without raw exploration noise.

A context brief is a consolidated document capturing the goal, scope, technical context, constraints, and success criteria of a request. You need it when vague user inputs require sharpening into a clear scope to enable precise downstream planning.

Yes, iterative clarification works without prior dependencies or components. The skill independently coordinates user questioning with parallel codebase exploration to yield a clear scope and context brief, requiring only a one-line goal description to start.

The best way to prevent rework from unclear project scope is enforcing one-question-per-message discipline alongside parallel codebase exploration. This approach guards against raw exploration noise and generates a standardized context brief capturing actionable decisions.

You should store the context brief in the standardized path docs/engineering-discipline/context. Storing the final brief here routes the consolidated goal, scope, and constraints directly to subsequent planning tools.