What problem does it solve?
It prevents wasted engineering by forcing thorough, evidence-backed discovery so implementations aren’t based on guesswork or outdated assumptions.
Core Features & Use Cases
- DISCOVER-first workflow: Runs a structured research process before the spec so findings directly shape what gets built.
- Deep documentation coverage: Reads full reference documentation for each sub-question instead of relying on overviews.
- Deterministic evidence rules: Uses a clear decision matrix to Adopt, Adapt, or Build-New and avoids reinventing existing solutions.
- External API rigor: Treats official API documentation as the primary source of truth and validates schemas by requiring contract artifacts and inline citations for verifiability.
- Codemap-scoped search: Optionally loads project codemaps to constrain searches to the relevant modules and paths.
Quick Start
Use the research skill to produce a spec-ready evidence package by decomposing your topic, scoping searches with project codemaps, consulting official reference docs (and real API docs when applicable), and writing conflict-aware findings with citations.