Discover

Find out how existing software already handles the feature, so we build on proven behaviour instead of guessing.

Process

1. Frame: restate the feature, the target user and the problem in 2-3 lines. If any of it is unclear, ask before researching.
2. Pick references: 3-6 products, open-source projects or libraries that do this well or differently. Include the best-in-class, a popular open-source one and a lightweight alternative where they exist.
3. Research behaviour, not marketing: use sub-agents with WebSearch/WebFetch (docs, changelogs, demos, issue trackers, user complaints) to learn what the software actually does: flows, states, edge cases, defaults, limits, error handling. Keep raw research out of the main context.
4. Decide per behaviour: for each notable behaviour, pick one verdict and say why:
   • Copy: proven, no reason to differ.
   • Improve: they do it, but there's a clear weakness (cite the complaint or gap).
   • Compare: references disagree; lay out the options and recommend one.
   • Skip: not relevant to our users or scope.
5. Write docs/<feature>/research.md: