shine-list-phase-assumptions

To surface project phase assumptions before roadmap planning, you provide the phase number to trigger an analysis across technical approach, implementation order, scope boundaries, risks, and dependencies, ending with a feedback prompt.

Technical assumptions in a project roadmap phase are underlying beliefs about the technical approach, implementation order, scope boundaries, risk areas, and dependencies that guide planning decisions before execution begins.

You analyze risks and dependencies for a roadmap phase by inputting the phase number, which validates phase existence and surfaces assumptions across five key planning areas to guide earlier decision-making.

Yes, you can validate phase existence against a roadmap before planning begins, as the analysis checks the input phase number and surfaces actionable next steps if the phase is valid.

No specific tools or dependencies are required to analyze phase assumptions for project planning, as the Skill operates independently to validate input and generate the assumption analysis.