skills.rest
zerAda
zerAdaCOMMUNITY
Explore all skills by this author →
GitHub

gsd-list-phase-assumptions

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

Updated Jan 21, 2026
Search Tags:#project management#project planning#risk mitigation#phase analysis#assumption identification
One-click install
npx skills add https://github.com/zerAda/RestaurantAgentAutomation --skill gsd-list-phase-assumptions-zerada
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-list-phase-assumptions
Source: https://github.com/zerAda/RestaurantAgentAutomation/tree/main/.agent/skills/gsd-list-phase-assumptions
Command: npx skills add https://github.com/zerAda/RestaurantAgentAutomation --skill gsd-list-phase-assumptions-zerada

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The time-consuming process of planning can be streamlined by getting insights into an agent's assumptions about a phase approach upfront.

Core Features & Use Cases

  • Assumption Identification: Quickly identify assumptions related to technical approach, implementation order, scope, risks, and dependencies.
  • Early Course Correction: Course correct early if assumptions are found to be incorrect.
  • Conversational Output: Get clear assumptions in a conversational manner to easily integrate feedback.

Quick Start

Run the 'gsd-list-phase-assumptions' skill with the phase number as the argument. Example: /gsd-list-phase-assumptions 3

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 identify project planning assumptions for a specific phase?▼

You surface project planning assumptions by analyzing a specific phase to extract technical approach, implementation order, scope, risks, and dependencies before actual planning begins.

What is phase analysis for risk mitigation in project management?▼

Phase analysis for risk mitigation is the process of evaluating a project stage to uncover hidden assumptions about scope and dependencies, allowing you to correct technical approaches early before planning.

How do I get phase assumptions using a conversational output format?▼

You get phase assumptions in a conversational output format by running the analysis skill with the phase number as an argument, which returns clear assumptions to easily integrate feedback.

Can I analyze technical approach and implementation order without external dependencies?▼

Yes, you can analyze technical approach and implementation order without external dependencies, as the skill operates independently to identify phase assumptions and scope risks.

When do I need to list phase assumptions for early course correction?▼

You need to list phase assumptions for early course correction before detailed planning begins, ensuring that incorrect technical approaches or scope dependencies are identified and adjusted proactively.

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
D0NMEGAD0NMEGA
8

gsd-list-phase-assumptions

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

Community
Intermediate
semicolon-devteamsemicolon-devteam

planner

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

Official
Basic
mlopscommunitymlopscommunity
37

brainstorming-planner

Probe project goals, scope, dependencies, and acceptance criteria into phased plans.

Official
Intermediate