dev.research

To create structured research documentation for codebase exploration, select a document type like an architecture doc or research brief, choose a topic, and apply the provided templates to generate consistent outputs capturing findings and rationale.

Available templates for standardizing architecture decisions and feature specs include Architecture Docs, Research Briefs, Flow Docs, State Docs, Service Design Docs, Feature Specs, Investigation Specs, Validation Specs, Recipes, Vendor Docs, and FAQs.

Yes, you can use these research workflows to document vendor evaluations and validation specs by applying the specific Vendor Docs and Validation Specs templates, which provide structured formats for capturing evaluations and testing guidelines.

Yes, dev.llm-session and sudocode are required dependencies to manage research artifacts and flow docs, providing the necessary environment to run the scripts and workflows that generate and organize the structured documentation.

The best way to maintain consistent documentation across multiple research projects is to use standardized templates and validation guidelines, ensuring artifacts capture decisions and recommendations uniformly for team onboarding and knowledge sharing.

A limitation of using fixed templates for investigation specs and feature specs is that while they enforce consistency, they may require appending to existing documents to accommodate unique project contexts outside the predefined structured formats.