kata-research-phase
Research how to implement a phase standalone, investigating implementation approaches before planning, or re-researching after planning is complete. Triggers include "research phase", "investigate phase", "how to implement", "research implementation", and "phase research".
npx skills add majiayu000/claude-skill-registry --skill kata-research-phase --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
<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 "balanced" if not set. **Model lookup table:** | Ag
- 0. Resolve Model Profile
- 1. Normalize and Validate Phase
- 2. Find Phase Directory and Check Existing Research
- 3. Gather Phase Context
- 3.5. Load Phase-Researcher Instructions
- 4. Spawn kata-phase-researcher Agent
- 5. Handle Agent Return
- 6. Spawn Continuation Agent
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
Universal phase discovery
for state in active pending completed; do
done
if [ -z "$PHASE_DIR" ]; thenWhat does the kata-research-phase skill do?
Research how to implement a phase standalone, investigating implementation approaches before planning, or re-researching after planning is complete. Triggers include "research phase", "investigate phase", "how to implement", "research implementation", and "phase research".
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill kata-research-phase --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
