shark-skills
Newborn Newborn Shell SH Python PY
↑ 45 ?
shark-skills tusharsrivastava/shark-skills

Running Claude Code like an engineering team: one operator, parallel lanes, audited merges.

HEALTH ? 80 / Healthy
// solo builder// hidden gem agent-orchestrationagents-mdai-agentsanthropicclaudeclaude-codeclaude-code-pluginclaude-code-skillsdebuggingdeveloper-tools ?

// readme


My Claude Code setup for building real features with a team of agents.

Using a single Claude Code session for a small fix works fine. Using it for a real feature usually turns into a mess of conflicting edits, silently dropped rules during merges, half-baked bug patches, and a giant commit at the end.

Throwing more agents at it doesn’t fix that on its own. Parallel agents with no shared plan just make code messier, faster.

shark is what I ended up with after building a production system this way.

The main session never writes code. It becomes the operator: it briefs the subagents, checks what they hand back, and talks to you. Lanes build in parallel against one shared contract. Every merge gets audited, and every bug gets a root cause before it gets a fix.

Every rule in here exists because breaking it cost me hours. Steal them. Change them. Make them stricter for your project.

See It in Action

Installation (2-minute setup)

1. Get the plugin

In Claude Code:

/plugin marketplace add tusharsrivastava/shark-skills
/plugin install shark@shark-skills

You’ll also need git, and Node.js with npx. The debugger MCP server runs through it.…