skills.rest
DuySeu
DuySeuCOMMUNITY
Explore all skills by this author →
GitHub

gsd-list-phase-assumptions

Surface phase-level technical assumptions and validate them against the roadmap.

1|Updated Aug 17, 2025
Search Tags:#planning#roadmap#assumptions#stakeholder#risk-analysis#phase
One-click install
npx skills add https://github.com/DuySeu/StockMind --skill gsd-list-phase-assumptions-duyseu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-list-phase-assumptions
Source: https://github.com/DuySeu/StockMind/tree/main/.agent/skills/gsd-list-phase-assumptions
Command: npx skills add https://github.com/DuySeu/StockMind --skill gsd-list-phase-assumptions-duyseu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams surface the agent's phase-level assumptions before starting a planning phase, enabling early course correction and reducing risk.

Core Features & Use Cases

  • Surface assumptions about technical approach, implementation order, scope boundaries, risks, and dependencies.
  • Validate phase against roadmap and prompt for user feedback to guide next steps.
  • Integrate with targeted workflows to align planning with roadmap milestones.

Quick Start

Provide a phase number to start analyzing and surface the agent's 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 phase assumptions before starting project planning?▼

To surface phase assumptions before project planning, provide a phase number to the agent. It then validates the phase against your roadmap and prompts for structured feedback to guide next steps.

What is phase-level assumption validation in roadmap planning?▼

Phase-level assumption validation is the process of identifying the agent's assumptions about technical approach, implementation order, scope boundaries, risks, and dependencies for a specific roadmap phase.

How do I validate a project phase against a roadmap?▼

To validate a project phase against a roadmap, trigger the analysis with a phase number. The system surfaces multi-area assumptions and prompts for user feedback to ensure alignment with roadmap milestones.

Does this assumption analysis work for projects without multiple phases?▼

No, this assumption analysis applies specifically to roadmap-driven projects with multiple phases. It requires validating phase existence against the roadmap to surface technical and planning assumptions.

What is the best way to identify scope boundaries and risks before planning a phase?▼

The best way to identify scope boundaries and risks is to surface phase-level assumptions before planning. This enables early course correction and reduces project risk by validating technical approaches.

Why should I check agent assumptions before roadmap planning?▼

Checking agent assumptions before roadmap planning enables early course correction and reduces risk. It ensures the technical approach, implementation order, and dependencies align with stakeholder expectations.

Related Skills

Explore More Product & Management Skills→
tomascorterealtomascortereal
60

gsd-add-phase

Add sequential integer phases to project milestones and update roadmap structures.

Community
Intermediate
NUbivekNUbivek

gsd-list-phase-assumptions

Surface Claude's project phase assumptions for user feedback.

Community
Intermediate
aura-farmingaura-farming
3

deal-inspection

Analyze a single deal across risk, financial, competitive, and stakeholder aspects.

Community
Advanced
TruCol270TruCol270
1

gsd-list-phase-assumptions

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

Community
Intermediate