skills.rest
D0NMEGA
D0NMEGACOMMUNITY
Explore all skills by this author →
GitHub

gsd-list-phase-assumptions

Identify Claude's assumptions about a project phase before planning.

8|Updated Apr 9, 2026
Search Tags:#dependencies#roadmap#assumptions#risk-analysis#phase-planning#planning-workflow
One-click install
npx skills add https://github.com/D0NMEGA/donnyclaude --skill gsd-list-phase-assumptions-d0nmega
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-list-phase-assumptions
Source: https://github.com/D0NMEGA/donnyclaude/tree/main/packages/skills/gsd-list-phase-assumptions
Command: npx skills add https://github.com/D0NMEGA/donnyclaude --skill gsd-list-phase-assumptions-d0nmega

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claude often makes implicit assumptions during phase planning. This skill surfaces those assumptions before planning begins, enabling course correction and safer project execution.

Core Features & Use Cases

  • Assumption discovery: analyzes a named project phase to surface technical approach, implementation order, scope boundaries, risks, and dependencies.
  • Roadmap alignment: validates phase against the project roadmap and highlights misalignments.
  • Decision support: provides concise, actionable assumptions and prompts for user feedback to guide next steps.
  • Use Case: Before starting phase 2, run this skill to reveal Claude's expectations and potential gaps, then adjust the plan accordingly.

Quick Start

Ask Claude to list the phase assumptions for the current roadmap phase and review them before planning.

Frequently Asked Questions about gsd-list-phase-assumptions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I surface implicit phase assumptions before starting project planning?▼

Surfacing implicit phase assumptions involves analyzing a named roadmap phase to identify technical approaches, implementation order, scope boundaries, risks, and dependencies. This reveals potential blind spots for course correction and safer execution.

What is the best way to validate dependencies and risks against a project roadmap?▼

Validating dependencies and risks against a project roadmap requires checking a defined phase for misalignments. Producing concise, actionable assumptions prompts user feedback to guide next steps and ensures safer project execution.

Why does phase planning fail when implicit assumptions are not discovered?▼

Phase planning fails when implicit assumptions are not discovered because hidden expectations about technical approach and scope boundaries create blind spots. Surfacing these assumptions beforehand enables course correction and safer project execution.

When do I need to run an assumption analysis for a planning workflow?▼

You need to run an assumption analysis for a planning workflow before beginning a new project phase. Analyzing the phase defined in the roadmap reveals expectations and potential gaps, allowing you to adjust the plan accordingly.

Can I use dependency analysis to highlight scope boundaries for a specific roadmap phase?▼

Yes, you can use dependency analysis to highlight scope boundaries for a specific roadmap phase. The analysis validates the phase against the project roadmap and produces actionable assumptions regarding risks and implementation order.

Related Skills

Explore More Product & Management Skills→
nnexainnexai
1

gsd-list-phase-assumptions

Analyze project roadmap phases to surface implicit assumptions about technical strategy, scope, and risk.

Community
Intermediate
TruCol270TruCol270
1

gsd-list-phase-assumptions

Identify Claude's assumptions about a phase's technical approach, implementation order, scope, risks, and dependencies.

Community
Intermediate
semicolon-devteamsemicolon-devteam

planner

Automates implementation planning for software projects with milestones, dependencies, and risks.

Official
Basic
dobrinz123dobrinz123

gsd-list-phase-assumptions

Surface phase assumptions across technical approach, implementation order, scope, risks, and dependencies.

Community
Intermediate