research-task

Codebase research involves analyzing architectural patterns, dependencies, and test coverage relevant to a new task. This process identifies potential overlaps with existing work and generates a detailed research document to inform task planning and prevent redundant implementation.

Preventing redundant work requires scanning existing task research to detect overlaps before implementation. By thoroughly exploring the codebase architecture and dependencies, you can identify existing code that can be leveraged or needs modification for the new feature.

Code exploration informs task planning by documenting architectural patterns and dependencies. For complex experiential tradeoffs, it can generate runnable prototypes alongside the research document, allowing you to evaluate different implementation approaches before committing.

Yes, codebase research includes analyzing test coverage and identifying dependencies relevant to a given task description. This analysis helps you understand how similar features are built and what libraries are used before starting implementation.

Prototypes for experiential tradeoffs are needed when implementing complex features where different approaches yield varying user or system experiences. Creating runnable prototypes during codebase research allows you to evaluate these tradeoffs before finalizing task planning.