skills.rest
rkz91
rkz91COMMUNITY
Explore all skills by this author →
GitHub

gsd-list-phase-assumptions

Analyze a project phase to surface assumptions about technical approach, implementation order, scope, risks, and dependencies.

264|11|Updated Apr 25, 2026
Search Tags:#workflow#feedback#roadmap#assumptions#analyze#risk#phase-planning
One-click install
npx skills add https://github.com/rkz91/coco --skill gsd-list-phase-assumptions-rkz91
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-list-phase-assumptions
Source: https://github.com/rkz91/coco/tree/main/systems/gsd/skills/gsd-list-phase-assumptions
Command: npx skills add https://github.com/rkz91/coco --skill gsd-list-phase-assumptions-rkz91

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Surface Claude's assumptions about a phase approach before planning, helping teams catch misalignment early.

Core Features & Use Cases

  • Surface assumptions about technical approach, implementation order, scope boundaries, risk areas, and dependencies for a given phase.
  • Align stakeholders by surfacing assumptions against roadmap and collecting feedback before proceeding.
  • Use case: Before planning Phase 2, run this skill to reveal assumptions and decisions needed.

Quick Start

Provide a phase number to see Claude's phase assumptions.

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 planning assumptions for a project phase before development starts?▼

Surfacing planning assumptions requires analyzing the project phase description to extract technical approach, implementation order, scope boundaries, risk areas, and dependencies. This structured output drives alignment and collects stakeholder feedback before development.

What is the best way to align stakeholders on technical approach and scope boundaries early?▼

Aligning stakeholders involves generating a structured five-area assumption set covering technical approach, scope, and risks. Presenting these assumptions against the roadmap prompts stakeholder feedback, catching misalignment early before planning proceeds.

How do I analyze roadmap risk areas and dependencies for upcoming implementation phases?▼

Analyzing roadmap risk areas and dependencies involves applying phase analysis to the loaded phase description. This produces a structured assumptions list highlighting specific risk areas and dependencies required for informed planning discussions.

Can I use phase planning assumptions to collect feedback and drive decision making?▼

Yes, phase planning assumptions drive decision making by providing a structured set of assumptions followed by a final feedback prompt. This explicit loop ensures technical approach and scope decisions are validated by stakeholders before moving forward.

Do I need a defined roadmap with phase descriptions to analyze implementation order and scope?▼

Yes, analyzing implementation order and scope boundaries requires a defined roadmap with the phase description loaded. Applying phase analysis directly to the existing roadmap context produces accurate planning assumptions for stakeholder discussions.

Related Skills

Explore More Product & Management Skills→
coco-researchcoco-research
264

gsd-list-phase-assumptions

Review phase assumptions for roadmap-driven software planning.

Community
Intermediate
thecomputer07thecomputer07

qsd-list-phase-assumptions

Analyze a roadmap to surface phase assumptions across five areas.

Community
Intermediate
virtenginevirtengine
17

list-phase-assumptions

Surface Copilot's phase assumptions across five planning areas with interactive corrections.

Official
Advanced
semicolon-devteamsemicolon-devteam

planner

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

Official
Basic