Intent → Execution, inside the IDE.
RavenKit turns product intent into executable engineering work with repo‑first intelligence, Feature Intelligence System (FIS)‑driven artifacts, and toolchains that keep teams aligned.
Corvus: Engineer‑first coordinator
Why RavenKit?
Repo-first: Corvus reads your code and FIS before answering. FIS is the source of truth; PRDs, ERDs, and tickets are projections. No generic cloud-only chat—run Ollama locally or bring your own API keys. Built for teams that ship in the IDE.
Use cases
Turn meeting notes into a PRD
Paste notes or a transcript; Corvus generates a structured PRD. Edit in the form, revise sections in chat, and save. One source of truth, no scattered docs.
Keep features and tickets in sync
Create deliverables in System Lens, then create and sync tickets to GitHub or Linear. Status flows back so FIS and your tracker stay aligned.
Ask where things are implemented
“Where is X implemented?” Corvus searches the repo, reads files, and cites paths. No guessing—answers are grounded in your code.
The Production Line
Everything stays anchored to Feature Intelligence System (FIS). Artifacts are projections, not sources of truth.
PRD
Clarify outcomes and scope before code decisions are made.
ERD
Define the persistent contracts and data boundaries.
Micro‑features
Atomic, buildable units that map cleanly to tickets.
Tickets
Sync outward to Jira, Linear, or GitHub without losing truth.
Ship with clarity.
RavenKit keeps teams in the IDE and converts intent into action with a repo‑aware co‑pilot.