gsd-complete-milestone skillA
gsd-complete-milestone is agent-read markdown (skill) from coco-research/coco: Use when every phase in a milestone is complete and the user wants to archive it, tag the release, and start the next version. Archives roadmap and requirements to .planning/milestones/, updates PROJECT.md, then tags the version..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
<objective> Mark milestone $ARGUMENTS complete, archive to milestones/, and update ROADMAP.md and REQUIREMENTS.md. Purpose: Create historical record of shipped version, archive milestone artifacts (roadmap + requirements), and prepare for next milestone. Output: Milestone archived (roadmap + requirements), PROJECT.md evolved, git tagged. </objective> <execution_context> **Load these files NOW (before proceeding):** - @$HOME/.claude/get-shit-done/workflows/complete-milestone.md (main workflow) - @$HOME/.claude/get-shit-done/templates/milestone-archive.md (archive template) </execution_context> <context> **Project files:** - `.planning/ROADMAP.md` - `.planning/REQUIREMENTS.md` - `.planning/STATE.md` - `.planning/PROJECT.md` **User input:** - Version: $ARGUMENTS (e.g., "1.0", "1.1", "2.0") </context> <process> **Follow complete-milestone.md workflow:** 0. **Check for audit:** - Look for `.planning/v$ARGUMENTS-MILESTONE-AUDIT.md` - If missing or stale: recommend `/gsd-audit-milestone` first - If audit status is `gaps_found`: recommend `/gsd-plan-milestone-gaps` first - If audit status is `passed`: proceed to step 1 ```markdown ## Pre-flight Check …
Read the whole file at its exact version.
How to install
mdr add coco-research/coco/gsd-complete-milestone@git:20260914.e75f220mdr add coco-research/coco/gsd-complete-milestone@sha256:2c6e18bbc2e5ccb0Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_7p5im6q47r5vkqbh)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260914.e75f220 latest | 2026-09-14 | e75f220 | 4,657 B | A | view · diff |
| git:20260426.d53cc6c | 2026-04-26 | d53cc6c | 4,493 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4657 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
coco-research/coco · 478 stars · license NOASSERTION · pushed 2026-09-25 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7p5im6q47r5vkqbh GET https://markdownregistry.com/api/v1/resolve?ref=coco-research/coco/gsd-complete-milestone GET https://markdownregistry.com/api/v1/blob/2c6e18bbc2e5ccb07256998909c80ffc34dfdcab505e4e4e47c74f87a343e542
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.