gsd-list-phase-assumptions

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

1|Updated Apr 4, 2026

Search Tags:#workflow #planning #project management #roadmap #assumptions #risk assessment

Ready to run

npx skills add https://github.com/nnexai/git-stacks --skill gsd-list-phase-assumptions-nnexai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-list-phase-assumptions
Source: https://github.com/nnexai/git-stacks/tree/main/.github/skills/gsd-list-phase-assumptions
Command: npx skills add https://github.com/nnexai/git-stacks --skill gsd-list-phase-assumptions-nnexai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents project misalignment by forcing the agent to explicitly state its underlying assumptions about a phase before any planning or execution begins.

Core Features & Use Cases

Assumption Surfacing: Identifies technical approach, implementation order, scope boundaries, risks, and dependencies.
Early Course Correction: Allows users to validate the agent's logic and correct misunderstandings before time is invested in detailed planning.
Use Case: Before starting a complex refactor phase, use this skill to ensure the agent understands the risk areas and technical constraints you are concerned about.

Quick Start

Ask the agent to list the assumptions for phase 3 of the current project.

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 project assumptions before starting a roadmap phase?▼

To surface project assumptions, analyze roadmap phases to identify implicit technical strategy, scope, and risks before planning begins. This prevents misalignment by forcing explicit validation of implementation order and dependencies early.

What is assumption surfacing in project management workflows?▼

Assumption surfacing in project workflows is the process of identifying implicit technical approaches, scope boundaries, and dependencies within roadmap phases. It provides transparency into reasoning to enable early course correction.

When do I need to list phase assumptions for a software project?▼

You need to list phase assumptions before starting complex tasks like a major refactor, ensuring the agent understands risk areas and technical constraints. This prevents investing time in detailed planning based on misunderstandings.

Can I validate technical strategy and scope boundaries using project state files?▼

Yes, you can validate technical strategy by analyzing project state files and roadmap documentation. This generates phase-specific insights into implementation order, scope boundaries, and risk assessment.

What's the best way to prevent misalignment during complex project refactoring?▼

The best way to prevent misalignment is forcing the explicit statement of underlying assumptions regarding technical strategy and risk before any phase execution begins. This allows early course correction of misunderstandings.

Do I need roadmap documentation to assess project phase risks?▼

Yes, you need access to roadmap documentation and project state files to generate accurate, phase-specific risk assessments. This documentation provides the context required for transparent assumption surfacing.