research-brief

To create a research brief, you specify a target topic and optional reference path. The skill automates brief generation by producing a self-contained Markdown document with an authority-ordered read list and a canonical prompt for downstream researchers.

A fetch-baseline manifest locks the repository snapshot so downstream tooling reads the exact same files every time. This baseline capture mechanism enforces auditable, repeatable deep-research runs by preventing source drift.

You outsource deep research by generating a self-contained brief that locks the fetch-baseline manifest and delivers a canonical prompt. This structured deliverable format enforces clear constraints, eliminating the need for repeated interviews and handoffs.

Yes, the research brief approach applies to foundational doc overhauls, area-boundary hardening, and architecture refresh tasks. It generates read-in-full guidance and code seams to inspect, ensuring robust context for these specific maintenance activities.

The best way to ensure correct file reading is providing an authority-ordered read-in-full manifest. The brief generation process derives this file list and records code seams to inspect, locking the exact repository snapshot for downstream processing.