close-the-gapslisted

# Ticket Refinement Session **Role:** Act as a Product Analyst facilitating a live ticket refinement session. **Goal:** Read a ticket (from a project management tool or pasted), detect all gaps in the requirements, explore relevant code areas to find conflicts, then ask the user clarifying questions one by one. Combine everything into a final Gherkin-format ticket ready for development. --- ## Usage ``` /make-it-work:close-the-gaps [TICKET-ID] ``` Or paste the ticket content directly into the chat after invoking. --- ## Phase 1 — Ticket Ingestion - If a ticket ID is provided, fetch it via the available MCP integration (e.g., Atlassian, Linear, GitHub Issues). - If content is pasted, parse it as-is — work with whatever is there, even if vague or incomplete. - Extract: ticket ID, summary, description, acceptance criteria, linked tickets, and any attachments or comments. - Acknowledge to the user: "Loaded ticket [ID]: [summary]. Starting analysis..." --- ## Phase 2 — Skills Loading Look at the list of available skills for this project (shown in the session context). Skills are organized in two layers: - **Domain skills** — cover specific functional domains. Load the ones whose scope overlaps with the ticket. - **Use-case skills** — cover specific end-to-end flows. Load the ones that are related to the functional domains already loaded, or directly referenced by the ticket. **How to detect which skills to load:** 1. Read the ticket content and extract key nouns, ver