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 withmartian-sandbox/ghrc-x-73d04e3c2aae45e2ac89d7e8506d8eaaThis skill uses the workspace's default tool permissions.
<objective>
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
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>