gsd-phase-researcher

To document codebase discovery and architecture planning for a new phase, compile domain knowledge and codebase context to guide decisions, producing a DISCOVERY.md file with structured recommendations and rationale for planners to act on.

Phase research in software architecture is the process of identifying objectives and scope by exploring existing implementations and standard patterns. You need it when planning new phases or refining existing ones to ensure decisions are well-documented and justified.

To structure a DISCOVERY.md for actionable planning recommendations, compile domain knowledge, explore relevant codebase patterns, identify key decisions, and document your findings with clear rationale explaining why specific architectural approaches are recommended.

Yes, you can apply phase research to refine an existing development plan by compiling updated domain knowledge and codebase context. This guides new decisions and documents findings to adjust the existing phase scope effectively and justify changes.

The best way to identify key architectural decisions before planning a phase is to research the domain for standard libraries and patterns, then explore the existing codebase to find relevant implementations that dictate necessary choices and scope.

You need a discovery document for codebase research to provide structured rationale for planners. It compiles domain knowledge and identifies key choices, ensuring phase execution is guided by documented findings rather than ad-hoc decisions.