Tip · Plan, Build
Name the files a task must not touch
Put protected files on a task's Preserve list, and Ship leaves them unchanged while it builds the task.
Every task has 3 file lists: Create, Modify, and Preserve. Create and Modify tell /ship$ship@planr-ship where the change should land. Preserve names the files it must leave alone, such as a generated file, a vendored dependency, or a contract another team owns.
Ship treats Create and Modify as the expected surface, not a fence, and adds companion files, such as a test, when correctness needs them. Preserve entries stay unchanged, and so do unrelated changes already in your working tree.
When a review keeps flagging the same file, add it to the Preserve list of the tasks that come near it.
Related prompts
Ship a small fix without a plan
For a clear, local change, ask Ship directly; missing planning files do not block it.
Ship one task, then stop
Build one task end to end and keep the change small enough to review.
Ship a task without touching protected files
Build the task while every file on its Preserve list stays unchanged.