qsd-list-phase-assumptions

Name: qsd-list-phase-assumptions
Availability: InStock
Author: thecomputer07

Analyze a roadmap to surface phase assumptions across five areas.

Updated Apr 13, 2026

Search Tags:#planning #dependencies #analysis #roadmap #risk-management #phase-assumptions

Ready to run

npx skills add https://github.com/thecomputer07/qsd --skill qsd-list-phase-assumptions

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Surface Claude's assumptions about a phase approach before planning to prevent misalignment and scope creep.

Core Features & Use Cases

Analyze the roadmap to identify key assumptions about technical approach, implementation order, scope boundaries, risks, and dependencies.
Surface and document these assumptions for early review and correction.
Enable a feedback loop to adjust plans before detailed planning or execution.

Quick Start

Provide a phase number to Claude and request the list of phase-assumptions before starting the planning phase.

Frequently Asked Questions about qsd-list-phase-assumptions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I surface phase assumptions before starting project planning?▼

To surface phase assumptions before planning, you provide a phase number to analyze the roadmap, validating phase existence and identifying structured assumptions across technical approach, scope, risks, and dependencies. This prevents misalignment and scope creep before detailed execution begins.

What are phase assumptions in a roadmap-driven workflow?▼

Phase assumptions in a roadmap-driven workflow are underlying beliefs about technical approach, implementation order, scope boundaries, risks, and dependencies. Surfacing these assumptions early ensures phase-level decisions align with stakeholder expectations and improves overall planning quality.

How do I prevent scope creep when planning project phases?▼

You prevent scope creep during project planning by validating phase existence against the roadmap and documenting structured assumptions about scope boundaries. A feedback loop allows you to adjust plans and correct misaligned expectations before detailed planning or execution starts.

Can I analyze roadmap dependencies and risks before planning a phase?▼

Yes, you can analyze roadmap dependencies and risks before planning by requesting a list of phase assumptions. The process validates the phase against the roadmap, surfaces risks and dependencies, and prompts for user feedback to guide the next steps in the workflow.

When do I need to review phase-level technical assumptions?▼

You need to review phase-level technical assumptions when early alignment on phase decisions is critical for planning quality. Applying this to roadmap-driven workflows before planning begins prevents misalignment and ensures stakeholders share a clear understanding of the technical approach.