By bryonjacob
AI organization orchestrator — define agents, assign tasks, and run them as coordinated teams inside Claude Code
Manage NanoClip agents — add, list, show, or edit agents in the organization
Display a comprehensive NanoClip dashboard with org chart, task summary, and recent activity
Initialize a NanoClip organization in the current directory
Display the NanoClip organization chart as a tree
Run the NanoClip organization — spin up an agent team to work through tasks
Delegation, team coordination, and hiring patterns for management agents. Use when you need to break down work into subtasks, assign work to reports, hire new agents, review team progress, or unblock stuck agents. Only applicable to agents with the management flag.
Persistent memory across work cycles using files. Use when you need to remember decisions, context, or state between cycles. Agents don't have session persistence — this file-based memory system is how you maintain continuity.
Core NanoClip work cycle protocol and task management. Use when you need to check assignments, update task status, create subtasks, post comments, or coordinate with other agents. Do NOT use for the actual domain work itself (writing code, research, etc.) — only for NanoClip coordination.
Runs pre-commands
Contains inline bash commands via ! syntax
Bash prerequisite issue
Uses bash pre-commands but Bash not in allowed tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A Claude Code plugin that orchestrates AI organizations. Define agents with rich profiles, assign tasks, and run them as coordinated agent teams — all from within Claude Code.
Inspired by PaperClip.
NanoClip models an organization as a directory on disk. Agents are JSON files. Tasks are JSON files. The directory structure IS the database. No server, no UI, no external dependencies beyond Claude Code and jq.
claude plugin marketplace add https://github.com/bryonjacob/nanoclip
claude plugin install nanoclip@nanoclip
That's it — all /nanoclip:* commands are now available in any Claude Code session.
Create a new directory and initialize NanoClip inside it:
mkdir my-org && cd my-org && git init
Then from Claude Code:
/nanoclip:init --name "My Team" --goal "Build a web app"
/nanoclip:agent add --name "Lead" --title "Tech Lead" \
--capabilities "Architecture, planning" --management
/nanoclip:agent add --name "Alice" --title "Backend Engineer" \
--capabilities "Python, APIs" --reports-to lead
/nanoclip:agent add --name "Bob" --title "Frontend Engineer" \
--capabilities "React, CSS" --reports-to lead
/nanoclip:task create --title "Build the landing page" \
--assignee lead --priority high
/nanoclip:run
That's it. The lead agent will break down the task, delegate to Alice and Bob, and they'll coordinate to get it done.
Use /nanoclip:dashboard at any time to see progress.
| Command | Description |
|---|---|
/nanoclip:init | Initialize a NanoClip organization in the current directory |
/nanoclip:agent | Manage agents — add, list, show, edit |
/nanoclip:task | Manage tasks — create, list, show, update, comment |
/nanoclip:orgchart | Display the reporting hierarchy as a tree |
/nanoclip:dashboard | Full dashboard: org chart, tasks, progress, recent runs |
/nanoclip:status | Quick status overview |
/nanoclip:run | Launch agents as a coordinated team to work through tasks |
my-org/
├── .nanoclip/
│ ├── org.json # Organization metadata (name, goal)
│ ├── agents/
│ │ ├── director.json # Agent definitions with rich profiles
│ │ ├── alice.json
│ │ └── bob.json
│ ├── tasks/
│ │ ├── 001.json # Tasks with full history & comments
│ │ └── 002.json
│ ├── runs/ # Run logs
│ └── counter.txt # Auto-incrementing task ID
└── workspace/ # Where agents do actual work
└── .memory/ # Agent memory persists across cycles
Agents have rich profiles that shape how they work:
{
"id": "alice",
"displayName": "Alice",
"title": "Backend Engineer",
"model": "claude-sonnet-4-6",
"capabilities": ["Python", "APIs", "databases"],
"expertise": "5 years backend, distributed systems",
"jobDescription": "Owns backend implementation...",
"reportsTo": "director",
"management": false,
"status": "idle",
"createdAt": "2024-01-15T10:30:00Z"
}
title — free-form, any role you want (not limited to CEO/engineer)capabilities — array of skills, used for task assignmentexpertise — background and experiencejobDescription — detailed responsibilitiesmanagement — enables delegation and hiring abilitiesreportsTo — builds the org hierarchyAgents flagged as management: true (or any agent with reports) get the delegation skill. They break down large tasks into subtasks, assign work to their reports, review progress, unblock stuck agents, and can hire new agents when capabilities are missing.
Non-management agents do the actual implementation work: writing code, creating files, running tests in the workspace/ directory.
/nanoclip:run uses Claude Code's agent teams feature for parallel execution. The top-level manager becomes the team lead, other agents become teammates. They coordinate through the shared task list and messaging, while persisting all state changes to .nanoclip/.
If agent teams aren't available, it falls back to running agents sequentially.
Agents save working context to workspace/.memory/<agent-id>/ before finishing a cycle. This is automatically loaded into their next cycle, providing continuity across runs.
NanoClip is inspired by PaperClip, reimagined as a Claude Code plugin.
npx claudepluginhub bryonjacob/nanoclip --plugin nanoclipJustfile standard interface management - maturity model, assessment, installation, and refactoring
Core development workflows and tooling standards. Stack configuration (Python/JS/Java), documentation (CLAUDE.md/MkDocs), workflow automation (justfile), CI/CD (GitHub Actions), and issue management.
AI-enhancement capabilities: session management, concise prompt writing (hemingwayesque), autonomous command execution (automate), and workflow orchestration.
Web development with Next.js 15+, React 19, static sites, Tailwind CSS v4 + CVA, and Formspree forms. Modern web UI patterns and deployment.
FFFlow — a complete development lifecycle (plan, work, audit) in one Claude Code plugin. Scales from informal prose specs (L0) to full spec-driven development with mutation testing and RID traceability (L3). Same workflow at every level.
Comprehensive UI/UX design plugin for mobile (iOS, Android, React Native) and web applications with design systems, accessibility, and modern patterns
Standalone image generation plugin using Nano Banana MCP server. Generates and edits images, icons, diagrams, patterns, and visual assets via Gemini image models. No Gemini CLI dependency required.
Multi-model consensus engine integrating OpenAI Codex CLI, Gemini CLI, and Claude CLI for collaborative code review and problem-solving.
Write feature specs, plan roadmaps, and synthesize user research faster. Keep stakeholders updated and stay ahead of the competitive landscape.
Harness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses