specs

Manage versioned normative rules and operational specifications for AI agent governance.

6|2|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/filipexyz/ravi --skill specs-filipexyz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: specs
Source: https://github.com/filipexyz/ravi/tree/main/src/plugins/internal/ravi-system/skills/specs
Command: npx skills add https://github.com/filipexyz/ravi --skill specs-filipexyz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of agent drift and inconsistent behavior by providing a centralized, versioned memory for rules, runbooks, and invariants that agents must consult before executing tasks.

Core Features & Use Cases

  • Durable Rule Management: Create, query, and sync normative rules (MUST/MUST NOT/SHOULD) across domains, capabilities, and features.
  • Contextual Retrieval: Retrieve specific operational modes like runbooks, checks, or decision history to ensure agents act with full context.
  • Use Case: Before modifying a core system component, an agent uses this skill to retrieve the relevant architectural constraints and validation checks to prevent regressions.

Quick Start

Use the specs skill to retrieve the current rules for the channels presence lifecycle feature.

Frequently Asked Questions about specs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent AI agent drift and inconsistent behavior across different tasks?

Agent governance uses normative rules, operational specifications, and validation checks indexed in a versioned repository. This mechanism enforces system invariants and ensures agents act with full operational context before executing modifications.

What's the best way to manage durable rules and specs for AI agents?

To set up agent specs, establish a structured Markdown directory hierarchy as the source of truth and use SQLite for indexing. This allows you to retrieve specific operational modes like runbooks, checks, or decision history for governance.

Do I need SQLite to manage versioned rules and specifications for AI agents?

Yes, SQLite is required to index the structured Markdown directory hierarchy. This setup enables efficient contextual retrieval of domain-specific constraints, runbooks, and validation checks that maintain the source of truth for system invariants.

Can I retrieve specific operational modes like runbooks and checks for AI agent governance?

Yes, contextual retrieval allows you to pull specific operational modes like runbooks, checks, and decision history. This ensures agents act with full context and prevents regressions when modifying core system components.

When do I need a centralized repository for normative rules and operational specifications?

You need a centralized repository when agents must consult system invariants before executing tasks to prevent drift. It provides the versioned memory required for maintaining consistent decision-making across domains, capabilities, and features.