agentleFS
Sign inStart free
ChianWChianW/C31/skills/utils/gsd-ship/SKILL.md

gsd-ship

Skill1 starsChanged 3 months agoMITView on GitHub

Output language: Respond automatically in the user's conversation language. Finalize a completed phase or entire project. Confirm acceptance, generate deliverable summary, update project state, and archive. Walk through each deliverable with user: If user selects [no] or [hold], stop. Update STATE.md with reason. Create memory/.planning/phases/XX-SUMMARY.md: Mark phase as ✅ shipped. If all phases shipped, mark milestone as ✅. If project complete: 1. Write memory/.planning/MILESTONES.md entry: If invoked with --quick or user says "quick ship": - Skip detailed checklist (trust user)…

5 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use gsd-next and gsd-onboard.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • open-gsdSkill

    gsd-next

    Smart entry — detect project state and route to the right next GSD action.

    Also in 3 projects that use this

  • open-gsdSkill

    gsd-onboard

    Guide existing codebase onboarding through mapping, doc ingest, and planning setup

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    All verification (C31-review or C31-review) has passed

    line 27
  2. Distinctive:

    No unresolved blockers in STATE.md

    line 28
  3. Distinctive:

    If user selects [no] or [hold], stop.

    line 67
  4. Very specific:

    If invoked with --quick or user says "quick ship":

    line 133

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Multilingual Triggers

LanguageTrigger phrases
ENgsd-ship
ZH收尾, 交付, 上线
JAリリース, 完成, デプロイ

Output language: Respond automatically in the user's conversation language.

gsd-ship — Deliver & Close

Finalize a completed phase or entire project. Confirm acceptance, generate deliverable summary, update project state, and archive.

Preconditions

  • All verification (C31-review or C31-review) has passed
  • No unresolved blockers in STATE.md
  • User confirms readiness to ship

Workflow

Phase 1: Load & Assess

  1. Read memory/.planning/STATE.md
  2. Read memory/.planning/ROADMAP.md
  3. Identify:
    • Current phase number and name
    • Phase status (must be "verified" or later)
    • List of deliverables produced
    • Blocker status (must be empty or resolved)

Phase 2: Acceptance Checklist

Walk through each deliverable with user:

Ship Checklist for Phase XX — <phase_name>

Deliverables:
  [ ] <deliverable_1> — <brief_description>
  [ ] <deliverable_2> — <brief_description>
  ...

Verification:
  [ ] All tests passing (or UAT signed off)
  [ ] Code reviewed (C31-review completed)
  [ ] Documentation updated
  [ ] No regressions identified

Blockers:
  (none or list resolved status)

Ship? [yes] [no] [hold]

If user selects [no] or [hold], stop. Update STATE.md with reason.

Phase 3: Generate Summary

Create memory/.planning/phases/XX-SUMMARY.md:

# Phase XX Summary — <phase_name>

## What Was Done
- <achievement_1>
- <achievement_2>

## Key Decisions
- D-01: <decision> (from CONTEXT.md)
- D-02: <decision>

## Deliverables
- <file/link_1>
- <file/link_2>

## Verification
- Reviewer: <reviewer_name>
- Result: PASS / PARTIAL / FAIL (with notes)

## Time
- Started: <date>
- Shipped: <date>

Phase 4: Update STATE.md

Current Position → Next phase (or "COMPLETE" if last phase)
Phase XX status: shipped

Phase 5: Update ROADMAP.md

Mark phase as ✅ shipped. If all phases shipped, mark milestone as ✅.

Phase 6: Archive (optional)

If project complete:

  1. Write memory/.planning/MILESTONES.md entry:
    ## Milestone X.Y — <name> — <date>
- Duration: N days
- Phases completed: N
- Key outcomes: ...
  2. Optionally tag/zip .planning/ as archive

Success Output

✅ Phase XX shipped

Summary: memory/.planning/phases/XX-SUMMARY.md
State: updated → Phase YY (or COMPLETE)
Roadmap: phase marked ✅
Next: <suggested_next_action>

Quick Ship (lightweight)

If invoked with --quick or user says "quick ship":

  • Skip detailed checklist (trust user)
  • Still update STATE.md and ROADMAP.md
  • Generate lightweight 3-line summary

Auto-Invoke

<auto_invoke> <trigger_phrases>

  • "ship"
  • "ship it"
  • "done"
  • "finish"
  • "收尾"
  • "交付"
  • "完成了"
  • "上线"
  • "publish"
  • "release" </trigger_phrases> </auto_invoke>

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free