rembric-plugin-development

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.