researching-phases

npx skills add majiayu000/claude-skill-registry --skill researching-phases --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

<user_command>/kata:research-phase</user_command> <objective> Research how to implement a phase. Spawns kata-phase-researcher agent with phase context. **Note:** This is a standalone research command. For most workflows, use `/kata:plan-phase` which integrates research automatically. **Use this command when:** - You want to research without planning yet - You want to re-research after planning is complete - You need to investigate before deciding if a phase is feasible **Orchestrator role:** Parse phase, validate against roadmap, check existing research, gather context, spawn researcher agent, present results. **Why subagent:** Research burns context fast (WebSearch, Context7 queries, source verification). Fresh 200k context for investigation. Main context stays lean for user interaction. </objective> <context> Phase number: $ARGUMENTS (required) Normalize phase input in step 1 before any directory lookups. </context> <process> ## 0. Resolve Model Profile Read model profile for agent spawning: ```bash MODEL_PROFILE=$(cat .planning/config.json 2>/dev/null | grep -o '"model_profile"[[:space:]]*:[[:space:]]*"[^"]*"' | grep -o '"[^"]*"$' | tr -d '"' || echo "balanced") ``` Default to "

Normalize phase number (8 → 08, but preserve decimals like 2.1 → 02.1)
if [[ "$ARGUMENTS" =~ ^[0-9]+$ ]]; then
elif [[ "$ARGUMENTS" =~ ^([0-9]+)\.([0-9]+)$ ]]; then
else
fi
grep -A5 "Phase ${PHASE}:" .planning/ROADMAP.md 2>/dev/null
ls .planning/phases/${PHASE}-*/RESEARCH.md 2>/dev/null
grep -A20 "Phase ${PHASE}:" .planning/ROADMAP.md
cat .planning/REQUIREMENTS.md 2>/dev/null
cat .planning/phases/${PHASE}-*/${PHASE}-CONTEXT.md 2>/dev/null