What problem does it solve? Research findings shared only in chat replies get lost when conversations are compacted or sessions end. This Skill ensures every codebase search and external documentation lookup is persisted as a markdown file under the active task's research/ directory, so findings survive across sessions. ## Core Features & Use Cases - Internal Code Search: Locates files, components, and code patterns with specific file paths and line numbers. - External Research: Gathers library documentation, API references, and best practices. - Mandatory Persistence: Writes each research topic to {TASK_DIR}/research/<topic>.md in a structured format with findings, code patterns, and caveats. - Strict Write Boundaries: May only write inside the active task's research/ directory; code, specs, and config files are off-limits. - Use Case: A main agent dispatches this sub-agent to investigate how authentication is implemented; the agent searches the codebase, writes research/auth-flow.md, and replies with only the file path and a one-line summary. ## Quick Start Dispatch the trellis-research agent with an active task path and a research question, and it will write its findings to that task's research directory.
