From kata
Surfaces Claude's assumptions on a phase's technical approach, order, scope, risks, and dependencies before planning. Validates phase from roadmap; prompts for feedback.
npx claudepluginhub gannonh/kata-orchestratorThis skill uses the workspace's default tool permissions.
<objective>
Surfaces Claude's assumptions about technical approach, implementation order, scope boundaries, risks, and dependencies for a project phase before planning.
Surfaces Claude's assumptions about a project phase's technical approach, implementation order, scope boundaries, risks, and dependencies before planning for early correction.
Share bugs, ideas, or general feedback.
Purpose: Help users see what Claude 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
<execution_context> @./references/phase-assumptions.md </execution_context>
Phase number: $ARGUMENTS (required)Load project state first: @.planning/STATE.md
Load roadmap: @.planning/ROADMAP.md
1. Validate phase number argument (error if missing or invalid) 2. Check if phase exists in roadmap 3. Follow 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<success_criteria>