gsd-list-phase-assumptions

Extract implicit phase assumptions from ROADMAP content into a structured list.

Updated Aug 23, 2026

Search Tags:#planning #verification #roadmap #assumptions #risk #phase

Ready to run

npx skills add https://github.com/optivent/gsd-kimi-cli --skill gsd-list-phase-assumptions

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify implicit phase assumptions from ROADMAP descriptions to improve planning and reduce misalignment.

Core Features & Use Cases

Extracts and lists implicit assumptions from phase descriptions and ROADMAP references.
Generates a concise, checkable CONTEXT-like summary to guide planning discussions.
Use Case: Before planning, verify alignment on architecture, tech choices, and scope for a given phase.

Quick Start

Run the gsd-list-phase-assumptions skill by specifying a phase number to inspect its ROADMAP.

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 identify implicit assumptions in a project roadmap to improve planning?▼

To identify implicit assumptions in a project roadmap, you extract phase descriptions and technology constraints from the roadmap content. This process surfaces hidden architecture and scope assumptions, producing a structured list to verify planning alignment.

What is the best way to validate phase assumptions before starting project planning?▼

Validating phase assumptions involves inspecting specific roadmap phases to generate a concise, checkable summary of architecture hints and technology constraints. This structured output guides planning discussions and reduces misalignment across the project.

How do I extract technology constraints and architecture hints from a roadmap phase?▼

You extract technology constraints and architecture hints by analyzing the roadmap content for a specified phase. The process identifies implicit assumptions and outputs a structured, checkable summary to guide technical planning and scope verification.

Can I check a specific roadmap phase for hidden planning risks and scope misalignment?▼

Yes, you can check a specific roadmap phase for hidden planning risks by specifying the phase number. The analysis identifies implicit assumptions regarding architecture and technology choices, outputting a list to mitigate scope misalignment before planning.

Do I need existing roadmap content to list phase assumptions for my project?▼

Yes, you need existing roadmap content and defined phase descriptions to list phase assumptions. The process requires access to this roadmap data to extract implicit architecture and technology constraints for generating a structured planning summary.