ship-fast
Ship Fast
Keep development moving while customers use a predictable stable release. Agents own the authorized dev loop; a human chooses the stable release batch. Adapt this workflow to the project's actual branches, host, checks and permissions.
Establish the project contract
Read the project's instructions, current Git state, open PRs and deployment configuration. Identify the branch and revision actually serving customers, the development environment, required checks, and existing session owners. Preserve dirty work and active sessions; use an owned worktree when another session may share the checkout.
When adopting this workflow, write a small project policy using references/project-policy.md. Record actual branch names, environment boundaries, check commands and authorization. Existing main or master can stay stable; branch renaming is unnecessary. Installing this skill does not itself authorize merges or deployments. Apply existing authorization without repeatedly asking for the same dev actions; clarify only a missing decision that blocks concrete work.
A branch alone does not isolate production. Trace the running frontend through its backend, database, storage, jobs, queues, auth and external integrations. Give dev independent mutable state and safe integration targets where needed. A dev UI pointing at the production backend still changes production. For local agent runtimes, separate state and pin loaded code to a revision; preserve existing sessions and prevent older workers from consuming newer-generation jobs.
Implement the project's authorized branch protections, CI and deployment mapping. Make production consume only reviewed revisions merged into the stable branch. If unattended integration is requested, configure and exercise an actual CI job or coordinator. Written instructions and a platform's auto-merge toggle do not prove that a job runs or that its checks protect the correct branch. Do not introduce privileged execution of untrusted PR code.
Verify adoption with a small real dev change: checks pass, its PR merges into dev, the dev environment serves the result, and production retains its prior code identity and isolated data. Report any missing enforcement precisely.