Clarify

Load and scan the spec for ambiguities across these categories:

Mark each: Clear / Partial / Missing

Generate questions (max 5 total):

• Only ask questions whose answers materially impact architecture, configuration, or deployment
• Prioritize by (Impact x Uncertainty) — highest first
• Each question must be answerable with multiple choice (2-5 options) or short answer

Ask ONE question at a time:

• For multiple-choice: recommend the best option with reasoning, then show all options
• After answer: record it, move to next question
• Stop when: all critical ambiguities resolved, user says "done", or 5 questions asked

After EACH accepted answer, update the spec:

• Add/create a ## Clarifications section
• Append: - Q: <question> → A: <answer>
• Update the relevant spec section
• Save immediately after each integration

Update pass counter in spec.md:

• Look for a **Passes**: line near the top of the spec (after the metadata block)
• If it exists, increment the clarify counter and update its status. Do NOT modify other skill counters.
• If it doesn't exist, add **Passes**: clarify: 1 ✓ (or without ✓ if issues were found) after the last metadata line (before ## Context)
• Set ✓ if no ambiguities were found (clean pass), remove ✓ if issues were found/questions asked
• Example: **Passes**: clarify: 2 ✓ means 2 passes, last one was clean

Report completion:

• Number of questions asked & answered
• Path to updated spec
• Sections touched
• Suggested next step (/plan-feature)