OpenParable
Skip to content
← Back to skills

gsd:ship

Development

gsd:ship is an Agent Skill for development published in the davepoon/buildwithclaude repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Create PR, run review, and prepare for merge after verification passes

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/davepoon/buildwithclaude/blob/HEAD/plugins/gsd/skills/ship/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/gsd-ship-aaf29202, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Closes the plan → execute → verify → ship loop.

<execution_context> @${CLAUDE_PLUGIN_ROOT}/workflows/ship.md </execution_context>

Execute the ship workflow from @${CLAUDE_PLUGIN_ROOT}/workflows/ship.md end-to-end.

<output_format> When the ship workflow concludes (PR created and tracked), emit a Next Up continuation block following the pattern in references/continuation-format.md:

  • Show ship status (e.g., ## ✓ Phase N / Milestone v1.x Shipped — PR #123) with the PR URL
  • Emit a ## ▶ Next Up heading with the next command (/gsd:next if there's more in the milestone, /gsd:complete-milestone if this was the last phase)
  • Use `/clear` then: before the command
  • Include a parenthetical: (/clear is safe — /gsd:resume-work restores position from HANDOFF.json if you change your mind)
  • Add an "Also available:" section with /gsd:review (cross-AI review) or PR-specific actions

PR creation is a clean boundary — review/merge happens out-of-band; the just-finished implementation conversation rarely informs the next phase. Suggesting /clear here keeps the next start small. </output_format>