list-phase-assumptions

To check project phase assumptions, you can use this Skill to surface KiloCode's internal expectations regarding technical approach, implementation order, scope boundaries, risks, and dependencies. It validates phase existence in your roadmap and prompts you for corrective feedback before planning begins.

Phase assumption surfacing is the process of identifying and validating internal expectations about a project phase's technical approach, implementation order, and scope. This prevents misunderstandings by allowing you to correct inaccurate assumptions before detailed planning begins.

You can list assumptions for a specific phase by asking KiloCode to parse your ROADMAP.md file. The Skill identifies the phase details and surfaces assumptions covering technical approach, scope boundaries, risk areas, and dependencies, then prompts you for feedback.

Yes, you need a ROADMAP.md file to clarify phase scope and dependencies. The Skill requires parsing this file to validate the existence of the phase and to extract details regarding technical approach, implementation order, and risk areas.

Validating technical approach assumptions before project planning prevents misunderstandings and ensures alignment. By surfacing assumptions about implementation order and scope boundaries early, you can correct inaccurate expectations and achieve more accurate planning.