Elaborate on specifications through detailed, structured interviews that surface implicit assumptions, contradictions, and downstream consequences. Use whenever the user wants to flesh out a spec, detail requirements, clarify ambiguity, deepen a design doc, or refine a feature description — even if they don't explicitly say "elaborate".
When invoked with arguments:
.md or path separators), read that file and use its content as the base for the interview, then write the refined spec back to the same fileprojects/spec-<summary>.md)When invoked without arguments:
When a file path is provided, do NOT start interviewing immediately after reading. First evaluate the content and present the following as conversational text:
After presenting, focus the interview on the ambiguous or missing areas. Do not re-ask about well-defined areas (only address them if the user wants to revise).
Prioritize questions that surface implicit assumptions
Show how each option affects downstream decisions
Avoid superficial or obvious questions
Flag contradictions and unexplored combinations
Interview in three phases. Move to the next phase only when the current phase is sufficiently covered.
Why — Purpose and motivation
What — Scope and requirements
How — Approach and implementation
Be very in-depth and continue interviewing continually until it's complete, then write the spec to the file.