gsd-list-phase-assumptions skillA
gsd-list-phase-assumptions is agent-read markdown (skill) from coco-research/coco: Use when the user wants to see what the agent assumes about a phase's approach, order, scope, risks and dependencies before planning starts, instead of running a full discuss session. Read-only; ends with a prompt for feedback..
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> Analyze a phase and present Claude's assumptions about technical approach, implementation order, scope boundaries, risk areas, and dependencies. Purpose: Help users see what Claude thinks BEFORE planning begins - enabling course correction early when assumptions are wrong. Output: Conversational output only (no file creation) - ends with "What do you think?" prompt </objective> <execution_context> @$HOME/.claude/get-shit-done/workflows/list-phase-assumptions.md </execution_context> <context> Phase number: $ARGUMENTS (required) Project state and roadmap are loaded in-workflow using targeted reads. </context> <process> 1. Validate phase number argument (error if missing or invalid) 2. Check if phase exists in roadmap 3. Follow list-phase-assumptions.md workflow: - Analyze roadmap description - Surface assumptions about: technical approach, implementation order, scope, risks, dependencies - Present assumptions clearly - Prompt "What do you think?" 4. Gather feedback and offer next steps </process> <success_criteria> - Phase validated against roadmap - Assumptions surfaced across five areas - User prompted for feedback …
Read the whole file at its exact version.
How to install
mdr add coco-research/coco/gsd-list-phase-assumptions@git:20260914.e75f220mdr add coco-research/coco/gsd-list-phase-assumptions@sha256:beb168a5a2ba7dd2Pin 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_vlkd5tkkleovelxv)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260914.e75f220 latest | 2026-09-14 | e75f220 | 1,626 B | A | view · diff |
| git:20260426.d53cc6c | 2026-04-26 | d53cc6c | 1,466 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 (1626 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_vlkd5tkkleovelxv GET https://markdownregistry.com/api/v1/resolve?ref=coco-research/coco/gsd-list-phase-assumptions GET https://markdownregistry.com/api/v1/blob/beb168a5a2ba7dd2bc6ed2ae931f53f8f31441b9f808e956fbf3fed6271fc541
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.