The sharding plugin: contract-first isolated development

sharding lets you develop a product as isolated “shards” that are coupled only through a frozen, versioned contract - with drift between them caught mechanically rather than by review. It’s for larger or multi-workstream projects where you want strong boundaries between the pieces.

Install

claude plugin install sharding@robworks-claude-code-plugins

What you can do

A set of commands walks the whole workflow:

/sharding:shard-init - scaffold a conductor workspace with a contract and manifest.
/sharding:shard-contract - author or amend the frozen contract, then bump its version.
/sharding:shard-new - register a new shard with its own directory and guardrails.
/sharding:shard-check - check a shard’s declared surface against the contract.
/sharding:shard-phase-check - gate a phase: every participating shard must be clean and the acceptance suite must pass.
/sharding:shard-status - show the shard graph, current phase, contract version, and blast radius.

The bundled sharding skill explains how to work inside a sharded project.

Good to know

It’s designed for a workspace or monorepo where the contract is the single coupling point between shards.
The contract is deliberately hard to change - amending it is a versioned, conductor-only action - which is what keeps shards honest.
Run status and check commands from the workspace root so paths resolve correctly.

Getting help

Repo and issues: github.com/robworks-code/sharding. Questions? Send us a message and a human will reply by email.