joycraft-research

Codebase research without brief bias is achieved by isolating question generation from fact gathering, ensuring the research subagent only sees objective questions and returns facts about file paths, signatures, and data flows.

Generating objective research questions involves reading the feature brief, identifying relevant codebase zones, and producing 5-10 codebase-specific questions written to a temporary file without including any brief content.

Extracting code facts requires spawning a research subagent that receives only the isolated questions, forcing it to return facts exclusively about file paths, data flows, dependencies, or notes if a question remains unanswered.

Isolated subagent research supports feature investigations in complex codebases by running a phased workflow that generates questions, gathers pure facts, and writes a finalized research document to the docs directory.

Documenting codebase research findings involves writing a structured research document to docs/research/YYYY-MM-DD-feature-name.md, deleting the temporary questions file, and presenting recommended next steps.

Subagents return subjective interpretations instead of codebase facts when the original brief is not withheld, which this workflow prevents by isolating question generation so the subagent only processes objective questions.