Skill

gsd-list-phase-assumptions

Surface Codex's assumptions about a phase approach before planning

Trigger Phrases

No trigger phrases were parsed from this skill.

Structured Sections

Context

Phase number: $ARGUMENTS (required) Project state and roadmap are loaded in-workflow using targeted reads.

Process

1. Validate phase number argument (error if missing or invalid) 2. Check if phase exists in roadmap 3. Follow list-phase-assumptions.md workflow: - Analyze roadmap description - Surface assumptions about: technical approach, implementation order, scope, risks, dependencies - Present assumptions clearly - Prompt "What do you think?" 4. Gather feedback and offer next steps

Objective

Analyze a phase and present Codex's assumptions about technical approach, implementation order, scope boundaries, risk areas, and dependencies. Purpose: Help users see what Codex thinks BEFORE planning begins - enabling course correction early when assumptions are wrong. Output: Conversational output only (no file creation) - ends with "What do you think?" prompt