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".
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".
metadata
{"version":"1.6.1"}
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
Why subagent: Research burns context fast (WebSearch, Context7 queries, source verification). Fresh 200k context for investigation. Main context stays lean for user interaction.
Phase number: $ARGUMENTS (required)
Normalize phase input in step 1 before any directory lookups.
Research modes: ecosystem (default), feasibility, implementation, comparison.
<research_type>
Phase Research — investigating HOW to implement a specific phase well.
</research_type><key_insight>
The question is NOT "which library should I use?"
The question is: "What do I not know that I don't know?"
For this phase, discover:
- What's the established architecture pattern?
- What libraries form the standard stack?
- What problems do people commonly hit?
- What's SOTA vs what Claude's training thinks is SOTA?
- What should NOT be hand-rolled?
</key_insight><objective>
Research implementation approach for Phase {phase_number}: {phase_name}
Mode: ecosystem
</objective><context>**Phase description:** {phase_description}
**Requirements:** {requirements_list}
**Prior decisions:** {decisions_if_any}
**Phase context:** {context_md_content}
</context><downstream_consumer>
Your RESEARCH.md will be loaded by `/kata-plan-phase` which uses specific sections:
-`## Standard Stack` → Plans use these libraries
-`## Architecture Patterns` → Task structure follows these
-`## Don't Hand-Roll` → Tasks NEVER build custom solutions for listed problems
-`## Common Pitfalls` → Verification steps check for these
-`## Code Examples` → Task actions reference these patterns
Be prescriptive, not exploratory. "Use X" not "Consider X or Y."
</downstream_consumer><quality_gate>
Before declaring complete, verify:
- [ ] All domains investigated (not just some)
- [ ] Negative claims verified with official docs
- [ ] Multiple sources for critical claims
- [ ] Confidence levels assigned honestly
- [ ] Section names match what phase-plan expects
</quality_gate><output>
Write to: ${PHASE_DIR}/${PHASE}-RESEARCH.md
</output>
