ship
Use when all plan tasks are done and green to review, archive planning artifacts, and ask how to finish.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- ship
- description
- Use when all plan tasks are done and green to review, archive planning artifacts, and ask how to finish.
03 SKILL.md 正文
Ship
If topology=multi-module (triage announcement or coordinator spec/plan declaration), read ../references/multi-module.md.
Gates — if any fail, stop here:
- Tests pass — or, for tasks with no automated test, their manual acceptance was performed.
- No
- [ ]remains in any relevant plan. - Staging spec reflects actual code behavior.
- README commands runnable; living docs honor North Star (atemporal ground truth, modular specs; see
../references/quality.md). - No incomplete tracked tasks in the harness task tracker (whatever the host calls it).
- For multi-module work: module plans and local acceptance are complete, and coordinator integration passes (or the change is reported as
partial-commit).
-
reviewthe whole diff. -
Update
docs/ROADMAP.md(if it exists):- Milestone completed? Mark
[x]. - Scope changed? Adjust upcoming milestone descriptions.
- Unrelated work (bugfix, refactor)? Roadmap unchanged.
- Milestone completed? Mark
-
archive— for multi-module work, archive module artifacts in their owning repositories first; archive the coordinator last. -
If user-visible, add to CHANGELOG
Unreleased. Releases move it to a version. -
Ask disposition: commit / merge / PR / keep / discard.
For a linked multi-repository implementation whose approved plan already includes linked commits: run the commit protocol (non-coordinators in dependency order, record SHAs as the revision set, coordinator last, shared change-set ID in every commit) when the user chooses commit or previously approved that path — do not re-ask whether commits are in scope. Still never push or open a PR without explicit approval.
If a linked commit fails, report partial-commit, preserve all commits and working trees, and report the exact recovery point.
-
On merge or PR: clean up worktree, delete local branch.
-
Roadmap has unchecked milestones? →
plannext.
No push or PR without explicit user approval.
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.