spec-firstlisted

# Spec-First Development Use the shared preparation contract before nontrivial implementation. Keep requirements, decisions and steps on one issue, so the executor and independent reviewer inspect the same source of truth. ## Contract Inputs: - User request, repository, existing issue/plan, and authorized delivery scope. Outputs: - Execution-ready issue or concrete planning blockers. - When implementation is authorized, implementation evidence and delivery-gate state. Creates/Modifies: - Requested preparation packet, implementation, and delivery artifacts through delegated engines within the caller's scope. External Side Effects: - Authorized tracker/repository operations only; inherit all access and host limits. Confirmation Required: - Existing implementation authorization covers preparation and execution within the same scope. Ask only for missing consequential intent or expanded authority. A preparation-only request stops after preparation. Repository merge/deployment permissions and required review/CI gates still apply. Delegates To: - `feature-intake` for requirements plus resolved implementation planning. - `prd-quality-gate` for blocking execution readiness and freshness validation. - `executing-plans` for prescribed implementation and delivery evidence. ## Workflow 1. Read the live issue and current plan when supplied. Run the `feature-intake` skill if the packet is missing or needs preparation. That coordinator uses the canonical requir