forge-research

Automating feature scoping requires exploring the codebase to gather context and resolving unknowns. This Skill automates that research phase by analyzing code and interviewing users to produce a grounded research document before planning begins.

Identifying unknowns in the Forge pipeline involves systematically exploring existing code and asking targeted user interview questions. This Skill handles both steps, grilling users for missing context and documenting findings to reduce ambiguity before development.

Creating a grounded research document requires extracting context from the codebase first and conducting user interviews second. This Skill combines both sources to write comprehensive research findings that capture everything needed for feature planning.

Yes, codebase access is required to run the initial research phase. The Skill explores the code directly to answer everything the code can before moving on to user interviews for questions that code alone cannot resolve.

No, user interviews are a core component of the research process. After exploring the code, the Skill grills the user with targeted questions to resolve remaining unknowns, ensuring no open questions exist before the planning phase starts.

Yes, the Forge research process handles extensive codebase exploration by automating context gathering. It systematically explores the code to answer technical questions, then supplements with user interviews for domain-specific unknowns.