Read and clarify feature specifications

Surface and resolve open questions in feature specification

Quick clarification before moving to planning; filters out avoidable ambiguity without heavyweight refinement meetings.

• · Reads .specify/feature.json for feature directory
• · Reads spec.md from that directory

• · 1–3 clarifying questions to user (most important first)
• · Updated spec.md with answers, resolved questions removed
• · Exit message: 'no open questions — spec ready for planning' if none

• · None (pure dialogue + file read/write)

• · .specify/feature.json exists with feature directory path
• · spec.md exists in that directory

• · .specify/feature.json missing — cannot locate spec.md (error)
• · spec.md missing open questions section — assumes complete, exits with 'ready for planning'
• · User answer is still vague — follow-up question asked (but counted within 1–3 limit)

• · Limits surface to 1–3 questions (doesn't overwhelm)
• · Ranks by importance (highest impact first)
• · Silent no-op if spec already clear (no artificial questioning)