jnuyens/gsd:list-phase-assumptions
skills/list-phase-assumptions/SKILL.md
Surface Claude's assumptions about a phase approach before planning
$ install --global
skillsauthnpx skillsauth add jnuyens/gsd-plugin gsd:list-phase-assumptionsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 25, 2026, 4:20 PM11.7s1 file scanned
SKILL.md
- name:
- gsd:list-phase-assumptions
- description:
- Surface Claude's assumptions about a phase approach before planning
- argument-hint:
- [phase]
<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> @${CLAUDE_PLUGIN_ROOT}/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>
Related Skills
jnuyens/gsd:remember-access
testing
VerifiedTrustedCommunity
Capture or review how this project connects to external systems (GitHub, AWS, npm, SSH, etc.) so future sessions know the auth recipe. Auto-detection hook logs candidate captures to an inbox; this skill promotes them to permanent recipes in `.planning/AUTH-RECIPES.md` and optionally to user-global memory at `~/.claude/auth-recipes/`.
43SKILL.mdUpdated May 26, 2026
jnuyens/gsd:new-ddd
tools
VerifiedTrustedCommunity
Initialize a new project using Documentation-Driven Development. Research, then write user-facing docs (SPEC.md) as the spec, then user validates docs, then phases derive from doc sections. Best for CLIs, libraries, SDKs, APIs, plugin systems, anything with a well-defined user-facing surface.
38SKILL.mdUpdated May 25, 2026
jnuyens/gsd:mvp-phase
tools
VerifiedTrustedCommunity
Plan an MVP-mode phase — captures an "As a / I want to / So that" user story, runs SPIDR splitting, then delegates to plan-phase
21SKILL.mdUpdated May 8, 2026
jnuyens/gsd:extract-learnings
testing
VerifiedTrustedCommunity
Extract decisions, lessons, patterns, and surprises from completed phase artifacts
21SKILL.mdUpdated Apr 25, 2026