iw-new-crlisted

# New Change Request Creator Create a complete change request package for the current project. **Change description**: $ARGUMENTS --- ## Step 1: Reserve CR ID Reserve the next available CR ID **immediately** to prevent concurrent agents from claiming the same number. ```bash iw next-id --type cr ``` This atomically allocates the next ID (e.g., `CR-00001`) using a database row-lock. Store the returned ID **exactly as printed** — you will use it verbatim throughout. **CRITICAL**: The `iw next-id` call MUST happen before ANY other work. **CRITICAL**: Use the ID **exactly as returned** (format: `CR-NNNNN`). Do NOT look for tracking files, do NOT use a manually chosen number, do NOT override or "adjust" the returned value for any reason. The database is the sole source of truth for IDs. ## Step 2: Understand the Change (MANDATORY INTERACTION) **NEVER skip this step.** Discuss with the user to ensure alignment. Present what you understood from `$ARGUMENTS`, then ask the user to confirm or correct: 1. **What needs to change?** (current behavior → desired behavior) 2. **Why is this change needed?** (requirement change, optimization, refactor, tech debt, etc.) 3. **Priority**: Critical / High / Medium / Low 4. **Which layers are affected?** (Database / Backend / API / Frontend / Pipeline / Template) 5. **Are there breaking changes?** (API contracts, database schema, integrations) 6. **Is data migration needed?** **WAIT for user answers before proceeding.** ### Determine