Skill: clarification-under-underspecification

1. Capability Definition & Real Case

• Professional Definition: The ability to notice that the user has not yet provided enough information, resist premature full-solution attempts, and ask focused clarification questions before committing to an answer.
• Dimension Hierarchy: Conversational Robustness->Underspecification Resilience->clarification-under-underspecification

Real Case

[Case 1]

• Initial Environment: A user reveals a task in fragments over multiple turns. The assistant has enough partial context to guess a likely solution path, but not enough information to complete the task correctly yet.
• Real Question: Let’s make a 35-minute playlist. Let’s add Taylor Swift songs. Let’s also put some Maroon 5. I prefer Taylor Swift, let’s do 20 minutes of that. So that leaves 15 minutes for Maroon 5.
• Real Trajectory: 1. Treat the early turns as incomplete shards rather than final specifications. 2. Ask whether the user wants actual songs, a plan, or API actions if the platform context is still unclear. 3. Wait to formulate a final action until all necessary structure is present. 4. Once clarified, generate the final constrained solution cleanly without inheriting earlier mistaken assumptions.