sprint-to-jiralisted

# Sprint → Jira Ticket Pipeline Reads a sprint planning markdown file, generates an agile user story (JSON) for each row in the Feature Summary table, and creates a Jira ticket for each one via `create_jira_ticket.sh`. ## Instructions ### Step 1: Locate inputs 1. Identify the sprint markdown file — use the file the user referenced or the current working directory. 2. Find `create_jira_ticket.sh`: ```bash find /Users/alysidi -name "create_jira_ticket.sh" 2>/dev/null | head -1 ``` 3. Confirm `JIRA_API_TOKEN` is set in the environment (the script checks for it). ### Step 2: Parse the Feature Summary table Read the markdown file and extract every row from the **Feature Summary** table. For each row, capture: - **Title** — column "Title" - **Summary** — column "Summary" - **BusinessContext** — column "Business Context" (may be empty) ### Step 3: Create a task list Use `TaskCreate` to create one task per feature before processing any of them. Subject format: ``` Agile story + Jira ticket: <Title> ``` ### Step 4: Process each feature sequentially For each feature (one at a time — clipboard is shared): 1. **Mark task `in_progress`** with `TaskUpdate`. 2. **Generate agile story JSON** using the schema below. Infer missing fields from the title and summary. Use the `agile-story` skill's output format but extend it to match what `create_jira_ticket.sh` expects: ```json { "Topic": "<Title>", "Story": "As a <persona>, I want <capability> so that <outcome>.", "B