Concepts

Core ideas behind RavenKit and how they fit together.

Feature Intelligence System (FIS)

The canonical source of truth for product intent, deliverables, and execution state. Vision, PRDs, ERDs, and micro-features live under your repo (e.g. .features or .ravenkit/features). RavenKit and Corvus read and write these artifacts; they are projections of intent, not one-off docs.

Corvus

The in-IDE assistant (chat + tools). Corvus uses your workspace, FIS, and code to answer questions, generate PRDs from notes, revise sections, run commands, and drive toolchains. It’s repo-first: answers are grounded in your code and features. Supports Ollama (local), Anthropic, and OpenAI.

Vision

Project north star: outcomes, non-goals, and high-level direction. Usually in vision.md under your features root. Corvus and the Spec Wizard use it to keep artifacts aligned.

System Lens

The tree view in the sidebar that aggregates vision, stack resources, features, generated documents (PRDs, ERDs), and tickets. One cockpit for “what we’re building” and “where we are.” Use Select Project in a monorepo to set scope.

Artifact flow: PRD → ERD → Micro-features

Intent flows downward: PRDs clarify outcomes and scope; ERDs define contracts and data boundaries; micro-features are atomic, buildable units with deliverables and tests. Each stage is derived where possible (e.g. “Generate ERD from PRD”) so the chain stays consistent.

Ticketing (GitHub / Linear)

Create and sync tickets from deliverables so execution lives in your issue tracker while FIS remains the source of truth. Configure once, then create/sync from System Lens.

See the Glossary for terms and acronyms. Get started · Commands