gsd-list-phase-assumptions

Surfaces assumptions about a project phase's technical approach before planning begins.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/WeWake1/BSOMS --skill gsd-list-phase-assumptions-wewake1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-list-phase-assumptions
Source: https://github.com/WeWake1/BSOMS/tree/main/.agent/skills/gsd-list-phase-assumptions
Command: npx skills add https://github.com/WeWake1/BSOMS --skill gsd-list-phase-assumptions-wewake1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before planning a project phase, hidden assumptions about technical approach, scope, and dependencies can derail execution. This Skill surfaces those assumptions upfront so you can correct course early instead of discovering misalignment mid-implementation. ## Core Features & Use Cases - Assumption Surfacing: Analyzes a phase from the project roadmap and presents assumptions across five areas: technical approach, implementation order, scope boundaries, risk areas, and dependencies. - Phase Validation: Verifies the requested phase number exists in the roadmap before analysis, with clear errors for missing or invalid arguments. - Conversational Output: Delivers findings directly in conversation without creating files, ending with a feedback prompt and clear next steps. - Use Case: Before asking an AI to plan Phase 3 of your product roadmap, run this Skill to see what it assumes about the architecture and scope, then correct any wrong assumptions before detailed planning begins. ## Quick Start Ask the assistant to list the assumptions for phase 3 of the current roadmap before planning it.

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

Run this Skill with the phase number as an argument. It validates the phase against your roadmap, then presents assumptions about technical approach, implementation order, scope, risks, and dependencies, ending with a prompt for your feedback.

What kinds of assumptions does phase analysis surface?▼

The analysis covers five areas: technical approach, implementation order, scope boundaries, risk areas, and dependencies. These are drawn from the phase description in your project roadmap.

Does this Skill create any files or plans?▼

No. Output is conversational only and no files are created. After reviewing assumptions, you can discuss context, proceed to plan the phase, or correct the assumptions first.

What happens if I provide an invalid phase number?▼

The Skill validates the phase number argument first and returns an error if it is missing or invalid. It also checks that the phase actually exists in the roadmap before running the analysis.

When should I list phase assumptions instead of planning directly?▼

Use it when a phase is ambiguous, spans multiple systems, or when prior plans drifted from expectations. Surfacing assumptions early lets you correct misunderstandings before detailed planning locks them in.