prepare-issue-contextlisted

# Prepare Issue Context ## Purpose De-risk the next implementation step (`/resolve-issue`, TDD, or CR) by **front-loading the data and codebase context** the agent needs to act without hallucinating. The skill ends with one of two states: **ready** (the development database holds every record the assignment scenarios refer to, and every scenario is mapped to a concrete code path) or **blocked** (a gap exists — the calling skill must stop and surface the gap to the user instead of guessing). --- ## Constraints - Apply `@rules/php/core-standards.mdc` - Apply `@rules/git/general.mdc` - Apply `@rules/jira/general.mdc` when the assignment lives in JIRA - If the current project uses Laravel, also apply `@rules/laravel/laravel.mdc`, `@rules/laravel/architecture.mdc`, `@rules/laravel/filament.mdc`, and `@rules/laravel/livewire.mdc` - **Read-only for production code.** This skill never modifies production source files. It is allowed to: create temporary seeders / factories / Tinker scripts under `database/seeders/`, `database/factories/`, or a scratch directory; insert rows into the **development** database; create scratch Pest tests that reproduce the bug. It is **never** allowed to mutate the production database, run destructive migrations, drop tables, push to the remote, or modify code in `src/` / `app/` outside of seed-only fixtures. - Never invent values that are not derivable from the assignment, the codebase, or the existing dev database. When a required value (account ID,