test-caseslisted

# Generate E2E Test Case Document Generate a structured E2E test case document for: `$ARGUMENTS` ## Step 1: Gather inputs ### Ticket (detect in order, stop at first match) 1. Extract `[A-Z]+-\d+` pattern from `$ARGUMENTS` if present 2. Otherwise: `git rev-parse --abbrev-ref HEAD` — extract ticket from branch name 3. Otherwise: ask — "What's the ticket number? (e.g. SOC-1177)" Derive `TICKET_CODE` by stripping the dash: `SOC-1177` → `SOC1177`. ### Feature name (detect in order, stop at first match) 1. Any non-flag text in `$ARGUMENTS` beyond the ticket 2. Branch name: strip the type prefix and ticket, humanize the remainder - `feat/SOC-1177-host-exclusion` → `Host Exclusion` - `fix/GH-42-null-scanner-result` → `Null Scanner Result` 3. Most recent commit subject on this branch: `git log main...HEAD --oneline | head -1` 4. If nothing found: ask — "What's the feature or fix name?" ### Optional flags (parse from `$ARGUMENTS` if present) - `--envs DEV,TEST,PROD` — environments for the tracking table. **Default: DEV, TEST, PROD** - `--services SMS,BOS` — service prefixes for TC codes. **Default: auto-detect in Step 2** - `--output <filename>` — write to this file. **Default: `TEST-CASES-{TICKET}.md` in current dir** - `--inline` — print document in conversation instead of writing a file ## Step 2: Detect context mode **Check if codebase context already exists in this conversation** — e.g. from a preceding `/plan`, `/issue`, or `/spec` invocation that already spawned th