skills.rest
hadpadrahul
hadpadrahulCOMMUNITY
Explore all skills by this author →
GitHub

gsd-list-phase-assumptions

Analyze roadmap and phase descriptions to surface agent assumptions.

Updated Apr 22, 2026
Search Tags:#assumptions#risk-assessment#dependency-analysis#team-alignment#phase-planning#planning-workflow#roadmap-analysis
One-click install
npx skills add https://github.com/hadpadrahul/school-erp --skill gsd-list-phase-assumptions-hadpadrahul
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-list-phase-assumptions
Source: https://github.com/hadpadrahul/school-erp/tree/main/.codex/skills/gsd-list-phase-assumptions
Command: npx skills add https://github.com/hadpadrahul/school-erp --skill gsd-list-phase-assumptions-hadpadrahul

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams surface the agent's assumptions about a phase-based approach before planning, reducing misalignment and rework.

Core Features & Use Cases

  • Surface assumptions about technical approach, implementation order, scope boundaries, risks, and dependencies for a given phase.
  • Validate phase against the project roadmap and prompt for user feedback to adjust the plan before detailed planning begins.
  • Use during roadmap reviews to align stakeholders and accelerate planning cycles.

Quick Start

Provide phase number to surface the agent's assumptions before planning.

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

To surface planning assumptions, provide the phase number to analyze the roadmap and project context. This reveals upfront assumptions about technical approach, scope boundaries, risks, and dependencies for review.

What is the best way to identify technical assumptions and implementation risks in a roadmap?▼

Analyzing the roadmap and phase descriptions identifies technical assumptions and implementation risks. This process validates implementation order and scope boundaries, prompting user feedback to align stakeholders and reduce rework.

Can I use phase planning workflows to align my team on dependency analysis?▼

Yes, you can use phase planning workflows to align your team on dependency analysis. The workflow validates the phase against the project roadmap, explicitly outlining dependencies and prompting feedback to accelerate planning cycles.

How do I validate phase scope boundaries against the overall project roadmap?▼

You validate phase scope boundaries by analyzing the roadmap and project context to surface explicit assumptions. This ensures the scope aligns with the overall plan and prompts user adjustments before detailed planning starts.

When do I need to analyze upfront assumptions during roadmap reviews?▼

You need to analyze upfront assumptions during roadmap reviews to prevent misalignment and rework. Surfacing these assumptions ensures stakeholders review technical approaches, implementation order, and risks before committing to detailed planning.

Related Skills

Explore More Product & Management Skills→
novatech2210-cmdnovatech2210-cmd

gsd-list-phase-assumptions

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

Community
Intermediate
daffy0208daffy0208
34

customer-feedback-analyzer

Synthesize customer feedback from multiple channels into prioritized roadmap items.

Community
Basic
fcastrillofcastrillo

rai-epic-design

Frame strategic objectives into bounded epic scopes with ADRs and feature candidates.

Community
Advanced
zerAdazerAda

gsd-list-phase-assumptions

Analyze a phase to present assumptions about technical approach, implementation order, scope, risks, and dependencies.

Community
Advanced