ship-prlisted

# Ship PR Take a change from intent to a review-clean pull request. Every step has a gate; do not cross it until the criterion holds. ## Workflow ### 1. Capture intent Get what the user wants changed: a pasted description, a linked issue, or a PRD. Read the issue/plan if referenced, then explore the codebase for the relevant files and conventions. If scope is ambiguous, ask before guessing past a user-owned decision. **Done when** you can name the files to change and why. ### 2. Branch A new branch is required — never work on the current one. Ask the user which branch to base it on (offer the current branch and `main` as defaults), then create the branch from it. **Done when** you are on a fresh branch off the confirmed base. ### 3. Plan Spawn a subagent (the `Plan` agent) to produce an ordered implementation plan: steps, files touched, tests to add. Present it briefly, then proceed. **Done when** you have a plan naming every step and its files. ### 4. Implement Build the plan, matching the surrounding code's style. Add or update tests covering the new behavior and its edge cases; if the repo has no test setup, propose the minimal one rather than skip silently. **Done when** every plan step is reflected in code and tests. ### 5. Validate Detect and run the project's validation scripts; fix failures and re-run until green. Never claim green without running them. - **package.json first**: run the relevant `scripts` when present — `typecheck`, `lint`, `test`, `build