Phase Researcher

Structure phase research by defining constraints, deliverables, risks, and recommended actions. This framework generates a formal artifact capturing standard stack choices and architecture patterns, enabling faster downstream planning and coding.

A phase research artifact is a structured brief documenting user constraints, pitfalls, and confidence breakdowns for a specific project phase. You need one when a phase goal exists and rapid, structured input is required before planning or coding begins.

Generate a research brief by providing a phase ID and project constraints. The process outputs a formal markdown file containing sections for open questions, code examples, and sources to drive immediate requirements assessment.

Yes, you can capture project guardrails and constraints before coding by running a defined research phase. This produces a consumable artifact detailing a 'don't hand-roll list' and recommended actions, ensuring downstream coding starts with high confidence.

Yes, the phase research framework operates without external dependencies. It applies when a phase goal exists, using an internal structured framework to capture options and guardrails independently of external tools.

The best way to reduce manual research time is to use a repeatable, prescriptive framework that aligns phase guidance to project goals. This approach prevents fragmented research and produces a ready-to-use brief for downstream planning.