gsd-list-phase-assumptions
Surface Claude s assumptions about a phase approach before planning
- Installs
- 108
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/shoootyou/get-shit-done-multi --skill gsd-list-phase-assumptions- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads gsd-list-phase-assumptions automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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> @{{PLATFORM_ROOT}}/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
- User knows next steps (discuss context, plan phase, or correct assumptions) </success_criteria>
FAQ
What does the gsd-list-phase-assumptions skill do?
Surface Claude s assumptions about a phase approach before planning
How do I install gsd-list-phase-assumptions?
Run npx skills add https://github.com/shoootyou/get-shit-done-multi --skill gsd-list-phase-assumptions in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/gsd-list-phase-assumptions/ (personal) or .claude/skills/gsd-list-phase-assumptions/ (project).
Which AI agents can use gsd-list-phase-assumptions?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is gsd-list-phase-assumptions safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains gsd-list-phase-assumptions?
It is published by shoootyou in shoootyou/get-shit-done-multi. It has 108 recorded installs.
More from shoootyou/get-shit-done-multi
get-shit-done
shoootyou/get-shit-done-multi
Structured spec-driven workflow for planning and executing software projects with Claude Code.
gsd-new-project
shoootyou/get-shit-done-multi
Initialize a new project with deep context gathering and PROJECT.md
gsd-plan-phase
shoootyou/get-shit-done-multi
Open the skill to read its SKILL.md instructions.
gsd-audit-milestone
shoootyou/get-shit-done-multi
Audit milestone completion against original intent before archiving
gsd-execute-phase
shoootyou/get-shit-done-multi
Execute all plans in a phase with wave-based parallelization
gsd-map-codebase
shoootyou/get-shit-done-multi
Open the skill to read its SKILL.md instructions.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.