gsd-research

To document implementation options for a new project feature or phase, you generate structured planning artifacts that capture recommended stacks, architecture patterns, and pitfalls. This process converts exploratory findings into actionable inputs that scope domain understanding and map directly into a phased roadmap.

Structuring research artifacts for roadmap planning involves generating standardized markdown files within a .planning/research/ directory, including SUMMARY.md, STACK.md, FEATURES.md, ARCHITECTURE.md, and PITFALLS.md. These coordinated artifacts scope domain understanding and produce phase-specific RESEARCH.md files for the planner to consume.

You can predict pitfalls during technology stack selection by applying a repeatable research workflow that surfaces potential issues and documents them in a PITFALLS.md artifact. This ensures identified risks are mapped into phased roadmap planning before implementation begins.

Yes, you can generate phase-specific RESEARCH.md documents for a project planner by running a research workflow that coordinates with phase- and project-research agents. The output defines table stakes, selects appropriate stacks, and maps results into a phased roadmap for the planner to consume.

No, this research workflow requires no external dependencies or components to function. It independently identifies implementation approaches and produces planning artifacts that align with internal .planning/research templates to support roadmap creation.