specgate-work-preparationlisted

# Preparing Work Apply the [SpecGate operating contract](../specgate/SKILL.md#operating-contract). This phase produces an approved implementation handoff; it never implements product code. ## 1. Define the contract and route Read the request, governing repository instructions, and author-selected source documents. Show the human the exact title, description, observable acceptance criteria, and non-goals. Split work that can be accepted independently. Use an `@check:<name>` binding only when the human confirms that exact deterministic check. Choose one route with the human: - **Quick work** for a small change that does not need a governed source snapshot. - **Artifact-backed work** when an existing spec, design, plan, verification document, or other source must be versioned and approved. Do not create a durable record until the human approves the displayed contract. Completion criterion: the human-approved preview names every slice's contract and route. ## 2A. Create quick work Quick work is available in Local and Full mode. Persist the approved contract with explicit criteria, then read it back: ```bash specgate work create-quick "$TITLE" --description "$DESCRIPTION" \ --ac "$CONFIRMED_CRITERION_1" --json specgate work show "$WORK_REF" --json specgate work context "$WORK_REF" --json ``` Never derive criteria from filenames, headings, numbering, or keywords. If the persisted title, description, or ordered criteria differ from the preview, stop instead of impleme