cf-researchlisted

# $cf-research Research in depth: **$ARGUMENTS** ## Purpose Deep research on a topic (repo, library, architecture, technology). Save structured markdown to `docs/research/` so later skills (e.g. `$cf-plan`) can reference it. Unlike `$cf-plan`, this skill does **not** plan or implement — it only researches and documents findings. ## Folder Output: `{docsDir}/research/YYYY-MM-DD-<slug>/` (default `docs/research/`). `<slug>` is kebab-case from the topic (e.g. `2026-07-05-react-server-components`); use today's date. Check `.coding-friend/config.json` for a custom `docsDir`. ## Workflow ### Step 0: Custom Guide ```! bash "${PLUGIN_ROOT}/lib/load-custom-guide.sh" cf-research ``` If the block above printed anything, apply only the `## Before`, `## Rules`, and `## After` sections; if it shows the raw command instead of output, re-run that exact `load-custom-guide.sh` fence now. ### Step 0.5: Context Budget Check Research is token-heavy (web fetches + parallel subagents): - Context > 50%: limit Step 4 parts to 2–3 - Pass file paths to subagents; do not embed full content - Context > 70%: warn the user and suggest a fresh session ### Choose Mode Confirm with the user: | Mode | Goal | Entry | Output | | ----------------------- | -------------------------------------------- | ----------- | ------------------------------------------- | | **Deep Research** | Comprehens