Research Common — Shared Format and Templates

To standardize research notes into consistent implementation plans, apply a shared research template that captures the original user request and structures analysis, proposed solutions, and testing strategy into actionable artifacts for downstream pipeline steps.

Preserving original user intent across LLM operations requires starting every research document with the exact user request and routing artifacts to standardized local, domain, and codex output paths with absolute dated status fields for traceability.

Formatting research documents for automated pipeline workflow processing involves using specified research template sections, absolute dated status fields, and repo-relative file path references to ensure outputs remain actionable for subsequent steps.

A prompt structuring research template should include sections for analysis, proposed solution, infrastructure integration, roadmap, testing strategy, and references to cover feature research and draft requirement generation comprehensively.

You need standardized output paths for requirements drafting when routing feature research artifacts into consistent local, domain, and codex locations so downstream pipeline processing can reliably locate and consume draft option files.