request-to-spec-issueslisted

<!-- Generated by Agent Profile Compiler. Do not edit by hand. --> # Request To Spec Issues ## Purpose Convert a completed `grill-change` agreement record into an intent-first spec candidate and vertical TDD-ready issue briefs. Preserve product intent and decision rules so implementation choices follow the agreed direction. ## Preconditions - The grill is complete and its agreement record is approved. - That grill approval authorizes this synthesis and one bounded local persistence step; do not ask for a second product-level approval. - Relevant local specs, ADRs, docs, fixtures, and code context have been checked. - If there is no completed grill agreement, stop and run `grill-change` first. ## Synthesis Rules 1. Do not re-interview the user except on a derivation exception - a contradiction, a missing material decision, or scope expansion (see Derivation Exceptions). 2. Keep product intent, non-goals, durable terms, and hard-to-reverse decisions above implementation mechanics. 3. Preserve existing spec contracts and safety rules unless the user explicitly approved changing them. 4. Split work into vertical behavior slices, not file layers. 5. Make every issue small enough for a focused RED, GREEN, refactor loop. 6. Mark dependencies and parallel-safe work explicitly. 7. Propose architecture rescue candidates before feature slices when a change would deepen an already fragmented codebase. ## Architecture Rescue Candidates When architecture rescue is needed, propose