How It Works Features Install GitHub
Claude Code Plugin

A self-organizing
AI workshop

You manage projects. It manages everything else—departments, dispatch, accounting, and the context to make every session productive from the first prompt.

claude — open-workshop
═══════════════════════════════════════════════════ MY WORKSHOP — Dashboard ═══════════════════════════════════════════════════ ACTIVE PROJECTS (2/5) ─────────────────────────────────────────────────── ◆ api-gateway Status: Auth middleware complete, rate limiting next Next: Implement token bucket algorithm Progress: 68% | Spend: $4.20 ─────────────────────────────────────────────────── ◆ docs-site Status: Search indexing done, deploy pending Next: Configure CDN + cache headers Progress: 90% | Spend: $1.80 BACKLOG (2 projects) ─────────────────────────────────────────────────── · design-system (last touched: 2026-02-15) · analytics-dashboard (last touched: 2026-01-28) ═══════════════════════════════════════════════════ What are we working on today? ═══════════════════════════════════════════════════

Every session starts from zero

Claude Code sessions are stateless. You pay for context recovery before you can do real work.

Cold starts

Each session begins blank. You re-explain what you're building, what's blocked, what to work on next. Every time.

Context thrashing

Switching between projects means losing all the context you just built. Good luck picking up where you left off.

Wasted tokens

Re-orienting costs tokens. Tokens cost money. You're paying to re-learn things the session already knew five minutes ago.

Four things happen automatically

Install the plugin. Start a session. Everything below fires without you asking.

01

Dashboard loads

Session starts with your project status, blockers, and next steps already in context.

02

Context persists

Milestones, briefings, and knowledge survive across sessions. No re-explaining.

03

Work dispatches

Specialized departments and external engines handle tasks with the right context and tools.

04

Costs tracked

Token spend links to milestones. You see ROI per project, not just a bill.

you: "I need an engineering department"
  → R&D researches tools and practices for your stack
  → Creates ~/.open-workshop/departments/engineering/
  → Engineering is now available for dispatch

Everything you need,
nothing you don't

Project Lifecycle

Active, backlog, archived. Shelve a project with a full briefing. Pick it back up months later without losing a beat.

Department Dispatch

Spawn sub-agents or full agent teams with department-specific knowledge and tool catalogs.

Engine Offloading

Route tasks to Codex, Gemini, or any AI CLI. Configure in YAML. Save Claude tokens for what matters.

ROI Tracking

Every task links to a milestone. Automatic token costs + manual progress = spend-per-feature visibility.

Self-Growing

Ships with only R&D. It's the stem cell — ask it to research a domain and it builds the department for you.

Setup Wizard

First run walks you through config with clear explanations. No YAML to write by hand. Change anything later.

Two commands. That's it.

Install the plugin, start a session. The wizard handles the rest.

Step 1 — Add marketplace
# Add the Open Workshop marketplace
/plugin marketplace add look-itsaxiom/open-workshop
Step 2 — Install plugin
# Install the plugin
/plugin install open-workshop@look-itsaxiom-open-workshop

# Start a new session — wizard runs automatically

Plugin is stateless.
Your work is permanent.

All your projects, departments, engine configs, and cost history live in ~/.open-workshop/. The plugin itself is read-only code from the marketplace cache.

Reinstall the plugin, update it, switch machines. Your data stays untouched.

~/.open-workshop/ ├── config.yaml # settings ├── projects/ │ ├── _manifest.yaml # active/backlog │ └── <project>/ │ ├── status.md │ ├── milestones.yaml │ ├── ledger.yaml # ROI data │ └── context/ │ └── last-briefing.md ├── departments/ # your custom ├── engines.yaml # AI CLIs └── cost-log.jsonl # auto-tracked

Built from real use,
not speculation

Open Workshop was extracted from Dream Factory, a personal multi-agent studio that manages 5+ creative projects from a single terminal. Card games, SaaS platforms, game engines, portfolio sites — all tracked, dispatched, and accounted for through one Claude Code session.

The patterns that made it productive — persistent context, department dispatch, engine offloading, milestone-linked accounting — were generalized into this distributable plugin. No opinions about your stack. No assumptions about your workflow. Just the infrastructure to be productive from prompt one.

7
Skills
4
Commands
2
Hooks
21
Total files