gsd-list-phase-assumptions

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

Updated Feb 18, 2026
One-click install
npx skills add https://github.com/jjchambers80/judgesdirectory --skill gsd-list-phase-assumptions-jjchambers80
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-list-phase-assumptions
Source: https://github.com/jjchambers80/judgesdirectory/tree/main/.github/skills/gsd-list-phase-assumptions
Command: npx skills add https://github.com/jjchambers80/judgesdirectory --skill gsd-list-phase-assumptions-jjchambers80

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before an agent plans a project phase, it holds implicit assumptions about the technical approach, scope, and risks that users never see. This Skill exposes those assumptions early so users can correct wrong directions before any planning work begins. ## 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. - Feedback Loop: Ends with a "What do you think?" prompt and offers next steps such as discussing context, planning the phase, or correcting assumptions. - Use Case: Before asking the agent to plan Phase 3 of a roadmap, run this Skill to review what the agent assumes about the architecture and scope, then correct any misunderstandings before planning starts. ## Quick Start Ask the agent to list its assumptions for phase 3 of the 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 agent assumptions before planning a phase?▼

Run this Skill with a phase number, such as phase 3. It reads the roadmap, analyzes the phase description, and presents assumptions about technical approach, implementation order, scope, risks, and dependencies for your review.

What assumption areas does the phase analysis cover?▼

The analysis covers five areas: technical approach, implementation order, scope boundaries, risk areas, and dependencies. Each is derived from the phase description in the project roadmap.

Does this Skill create or modify any files?▼

No, the output is conversational only. It presents assumptions in the chat and ends with a "What do you think?" prompt, without creating or modifying any files.

What happens if I provide an invalid phase number?▼

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

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

Use it when a phase is ambiguous, high-risk, or involves unfamiliar technology. Reviewing assumptions first lets you correct the agent's direction before investing effort in a full plan.