kata-research-phase

You can document standard stacks and architecture patterns for a project phase by generating a structured RESEARCH.md file that captures technical decisions, pitfalls, and evidence gathered from official docs to guide planning.

Standalone phase research investigates how to implement a specific project phase without committing to a full planning cycle, producing a dedicated research artifact that outlines standard stacks and potential pitfalls.

You perform re-research after initial project planning by triggering a standalone investigation phase that re-evaluates architecture patterns and pitfalls, updating the RESEARCH.md artifact with new evidence from official documentation.

Yes, phase research respects existing constraints in CONTEXT.md by enforcing those decisions during the investigation to narrow scope and ensure the generated RESEARCH.md aligns with prior architectural choices.

The best way to gather technical evidence for a RESEARCH.md file is to orchestrate a researcher agent that queries Context7, official documentation, and WebSearch, compiling the findings into a structured artifact.

You should not use standalone phase research if your project phase lacks existing CONTEXT.md decisions to constrain scope, or if the phase requires immediate implementation rather than preliminary investigation into architecture patterns.