gsd-list-phase-assumptions

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

Updated Mar 14, 2026

Search Tags:#planning #claude #roadmap #assumptions #alignment #risk #phase

Ready to run

npx skills add https://github.com/novatech2210-cmd/ImidusApp --skill gsd-list-phase-assumptions-novatech2210-cmd

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-list-phase-assumptions
Source: https://github.com/novatech2210-cmd/ImidusApp/tree/main/.codex/skills/gsd-list-phase-assumptions
Command: npx skills add https://github.com/novatech2210-cmd/ImidusApp --skill gsd-list-phase-assumptions-novatech2210-cmd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Surface Claude's assumptions about a phase approach before planning to help teams align on approach and avoid missteps.

Core Features & Use Cases

Surface Claude's assumptions about technical approach, implementation order, scope boundaries, risks, and dependencies.
Validate phase existence in the roadmap and present clearly actionable next steps.
Facilitate early feedback and course correction before drafting a plan.

Quick Start

Ask Claude to surface phase assumptions and present them for feedback.

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 roadmap planning?▼

To surface phase assumptions, prompt Claude to identify and present its assumptions about technical approach, implementation order, scope, risks, and dependencies before you draft the full plan. It validates the phase number against the roadmap to ensure alignment.

What is the best way to align teams on technical approach during a phase review?▼

The best way to align teams is presenting Claude's phase assumptions upfront for early feedback. Exposing implementation order, scope boundaries, and dependencies facilitates course correction before committing to a drafted plan.

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

You validate the phase number by requesting a phase assumption review. The process checks the input phase against the existing roadmap to confirm existence, then outputs assumptions and recommended next steps for that specific phase.

When do I need to identify project phase assumptions?▼

You need to identify phase assumptions during roadmap reviews and phase analysis, specifically before planning begins. This exposes technical approach, implementation order, scope boundaries, risks, and dependencies to avoid missteps.

Does surfacing roadmap assumptions work without predefined dependencies?▼

Yes, surfacing roadmap assumptions works without predefined dependencies because the Skill operates independently to identify risks and dependencies. It actively reveals these factors during the phase analysis to guide your next steps.