gsd-project-researcher

Researching a domain ecosystem for project initialization requires analyzing standard technology stacks, architecture patterns, and common pitfalls to establish a solid foundation. This produces structured outputs including STACK.md, FEATURES.md, ARCHITECTURE.md, and PITFALLS.md to guide downstream roadmapping.

Documenting architecture and pitfalls for a greenfield product requires generating structured deliverables like ARCHITECTURE.md and PITFALLS.md. This approach identifies table stakes, differentiators, anti-features, and mitigations to provide a repeatable baseline for teams starting a new project.

You need to run domain research before launching a greenfield product to discover standard stacks, recommended libraries, and typical architecture patterns. It is also applicable during subsequent milestones to guide stack decisions and map potential risks before development begins.

Yes, you can use this to map features and technology stacks for subsequent milestones. The process analyzes a domain to produce a consolidated research document and prescriptive templates that guide feature planning, architecture choices, and stack decisions beyond just the initial greenfield phase.

To generate a baseline architecture and feature plan from domain research, you invoke the orchestrator to spawn parallel researchers. This produces structured outputs including STACK.md, FEATURES.md, ARCHITECTURE.md, and PITFALLS.md for downstream roadmapping.