rembric-plugin-development

Enforce spec-aligned Rembric plugin development with OpenSpec-first change management and unified cross-client versioning.

9|1|Updated May 13, 2026
One-click install
npx skills add https://github.com/susomejias/rembric --skill rembric-plugin-development
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rembric-plugin-development
Source: https://github.com/susomejias/rembric/tree/main/.agents/skills/rembric-plugin-development
Command: npx skills add https://github.com/susomejias/rembric --skill rembric-plugin-development

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Building Rembric agent plugins without strict, standardized workflows leads to spec drift, cross-client incompatibilities, broken multi-process memory flows, and invalid release tracks that break user deployments.

Core Features & Use Cases

  • OpenSpec-first change management: Enforces proposing and amending OpenSpec changes before any plugin work to eliminate spec drift, since plugin modifications always touch multiple specs and files.
  • Unified cross-client release tracking: Manages a single unified plugin version for all four supported clients (Claude Code, Codex CLI, Hermes Agent, opencode) to prevent version divergence and phantom release PRs.
  • End-to-end validation guardrails: Provides step-by-step e2e validation instructions against the local Rembric dev Docker stack to catch non-obvious bugs in the multi-process agent → bridge → MCP → HTTP → SQLite flow.
  • Per-client best practices: Documents hard-won platform-specific gotchas for each supported client to avoid silent failures and broken functionality.
  • Use Case: When adding a new MCP handler for the opencode client, this skill guides you through the required cwd spike, local dev stack validation, and lockstep version updates for all four client plugins.

Quick Start

Use the rembric-plugin-development skill to implement a new session.created MCP handler for the opencode Rembric plugin, validate it against the local dev Docker stack, and update all client plugin manifests to the new unified version.

Frequently Asked Questions about rembric-plugin-development

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

FAQPage Schema
How do I prevent cross-client incompatibilities when developing Rembric agent plugins?

Preventing cross-client incompatibilities in Rembric agent plugins requires enforcing spec-aligned workflows with OpenSpec-first change management and unified cross-client versioning to eliminate spec drift across all four supported clients.

What is the best way to manage release tracks for MCP handlers across multiple agent clients?

Managing release tracks for MCP handlers across multiple agent clients is best handled by maintaining a single unified plugin version to prevent version divergence and phantom release PRs across all four supported Rembric clients.

How do I validate a Rembric plugin against the multi-process agent to SQLite flow?

Validating a Rembric plugin against the multi-process agent to SQLite flow requires running step-by-step end-to-end validation against the local Rembric dev Docker stack to catch non-obvious bugs in the bridge and MCP HTTP pipeline.

Does Rembric plugin development require OpenSpec change proposals before implementing MCP handlers?

Yes, Rembric plugin development requires proposing and amending OpenSpec changes before implementing MCP handlers or updating manifests, because plugin modifications always touch multiple specs and files to prevent spec drift.

Why do multi-process memory flows break when onboarding new Rembric clients?

Multi-process memory flows break during new Rembric client onboarding due to silent platform-specific failures and spec drift, which requires per-client best practices and local dev stack validation to prevent broken functionality.