researchlisted
Install: claude install-skill gitgitWi/council-flow
# flow:research — Pre-plan investigation
Research exists to make the plan better. The output is not for shipping; it is a working document that the plan skill consumes. Optimize for *useful pointers, decision-relevant facts, and explicit options*, not for thoroughness.
## When to run
- Task size is **L** (always)
- Task size is **M** and any of:
- The user is unsure how the existing code is structured
- The change depends on a library/API behavior the user has not verified
- There is an existing similar pattern elsewhere in the repo or org that should be matched
- Task size is **S** — usually skip. The plan can be drafted directly from the file under change.
If you are not sure whether to research: **time-box it.** Spend 5–10 minutes scanning the most-likely-relevant files, then write a short `research.md` and move on. The plan-review step can flag if more research is needed.
## What to produce
`<worktree>/.planning/<date>-<task>/research.md`, with the standard frontmatter (full schema in `../../references/frontmatter.md`):
```markdown
---
title: "Research — <task>"
type: research
task: <kebab task name>
task_date: <YYYY-MM-DD>
created: <today>
last_updated: <today>
status: active # this doc rarely changes status
size: <S|M|L>
parent: ./prepare.md
related:
- ./plan.md (will consume these findings)
time_box: 10m # 5m | 10m | 20m | 60m
used_external_llm: false # set true if Gemini/OpenCode produced raw output under artifacts/
---
# Research