By AitorPo
Teaching plugin: construction-crew metaphor for Claude Code agents, skills, and workflows. Demonstrates when the main thread delegates to a specialist agent and when it handles the task itself.
The bricklayer of the crew. Use whenever the user wants to build a wall, lay a foundation, raise a structure, lay bricks, or talks about masonry. Triggers on phrases like "build a wall", "construct a structure", "lay bricks", "raise a wall", "construir un muro", "levantar pared", "hacer una pared", "obra de albañilería". Produces a WALL.md artifact in the chosen site directory describing what was built.
The electrician of the crew. Use whenever the user mentions wiring, circuits, sockets, lights, breakers, or electrical work. Triggers on phrases like "wire the circuit", "install a socket", "the lights don't work", "add a breaker", "cablear", "instalar enchufe", "el panel eléctrico", "no funcionan las luces", "tirar cable". Edits an existing PANEL.md artifact to add circuits. Cannot create new files — only edits.
The foreman of the crew. Use when the user asks for a multi-trade job that needs coordination — building a whole room, planning a renovation, deciding which trades to call in what order. Triggers on phrases like "build a whole room", "build a bathroom", "coordinate the trades", "what's the plan to build X", "plan the renovation", "foreman", "capataz", "supervisar obra", "organiza la obra". Produces a PLAN.md and then delegates to bricklayer, plumber, electrician in the right order.
The plumber of the crew. Use whenever the user mentions pipes, water supply, drains, leaks, or plumbing. Triggers on phrases like "install pipes", "fix the leak", "connect the water", "run plumbing through the wall", "instalar tubería", "arreglar fuga", "fontanería", "agua corriente", "desagüe". Produces a PIPES.md artifact describing the pipe layout, material, and pressure.
Build an entire room end-to-end: planning, walls, plumbing, wiring, and finishing paint. Orchestrates the `foreman` agent plus all three trades plus an inline paint step.
Build a wall in the chosen construction-site directory. Delegates to the `bricklayer` agent.
Delete construction-site artifacts (WALL.md, PIPES.md, PANEL.md, PLAN.md). Destructive — always asks for explicit confirmation before removing anything. Main-thread only, no agent.
Walk through a construction-site directory and produce a status report of every WALL.md, PIPES.md, PANEL.md, and PLAN.md artifact found. Read-only, main-thread only — no agent involved.
Installs the four workshop agents (bricklayer, plumber, electrician, foreman) into the current project's .claude/agents/ directory. Use when the user wants to register the construction-crew specialists in their project.
Uses power tools
Uses Bash, Write, or Edit 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 sandbox plugin for learning Claude Code agents, skills, and workflows. Not production: every "build" produces tiny Markdown artifacts (WALL.md, PIPES.md, PANEL.md, PLAN.md) so you can see what each layer of the system actually did.
Imagine Claude as a head contractor. When you ask for a job, Claude either picks a specialist from the crew (an agent) or, if no specialist matches, rolls up its sleeves and does it directly. This plugin is a sandbox to learn that mechanic.
There are four specialists in the crew — and deliberately no painter. When you say "paint this wall", the main-thread Claude does it itself using a plain skill. That asymmetry is the central lesson of the plugin.
| Trade | Agent | What you say to summon them |
|---|---|---|
| Bricklayer | bricklayer | "build a wall", "lay foundation", "raise structure", "construir un muro", "levantar pared" |
| Plumber | plumber | "install pipes", "fix the leak", "connect water", "instalar tubería", "arreglar fuga" |
| Electrician | electrician | "wire the circuit", "install sockets", "the lights don't work", "cablear", "instalar enchufe" |
| Foreman | foreman | "build a whole room", "coordinate trades", "what's the plan?", "foreman", "supervisar obra" |
| Painter | none — main thread | "paint this wall" → Claude does it directly |
Not every task needs an agent. Agents cost context and add indirection. Reserve them for:
Painting in this sandbox is a one-step skill with no specialised tooling — fall through to the main thread.
If you internalise nothing else from this plugin, internalise this: recognising which tasks don't need an agent is a senior judgement call, and the painter omission is here to make that call visible.
| Skill | Who runs it | Why |
|---|---|---|
/workshop:build-wall | invoked → bricklayer | needs the bricklayer's procedure |
/workshop:install-pipes | invoked → plumber | plumbing knowledge |
/workshop:wire-circuit | invoked → electrician | electrical knowledge |
/workshop:paint-wall | main thread directly | trivial, no specialist |
/workshop:build-room | main thread reads, then calls foreman | full workflow |
/workshop:inspect-site | main thread directly | read-only walk through |
/workshop:demolish | main thread, asks for confirmation | destructive, gates explicitly |
Public GitHub repo, no token needed.
/plugin marketplace add https://github.com/AitorPo/claude-code-plugin-sample.git
/plugin install workshop@workshop-marketplace
/workshop:install-all
Then commit:
git add .claude/rules/ .claude/agents/
git commit -m "Add workshop conventions and agents"
Once the workshop bundle is installed in Codex, run inside your project:
run workshop-install-all
Then commit:
git add AGENTS.md .codex/agents/
git commit -m "Add workshop conventions and subagents"
| Skill | Description | Usage |
|---|---|---|
install-rules | Install workshop conventions rule | /workshop:install-rules |
install-agents | Install the four crew agents | /workshop:install-agents |
install-all | Install/update all rules + agents | /workshop:install-all |
build-wall | Build a wall via bricklayer | /workshop:build-wall |
install-pipes | Run pipes via plumber | /workshop:install-pipes |
wire-circuit | Wire a circuit via electrician | /workshop:wire-circuit |
paint-wall | Paint a wall on the main thread, no agent | /workshop:paint-wall |
build-room | Full multi-trade workflow + finishing paint | /workshop:build-room |
inspect-site | Read-only site status report | /workshop:inspect-site |
demolish | Delete artifacts with explicit confirmation | /workshop:demolish |
| Agent | Description | Triggers on |
|---|---|---|
bricklayer | Bricklayer — builds walls | "build a wall", "construir un muro", "lay foundation" |
plumber | Plumber — pipes and leaks | "install pipes", "arreglar fuga", "connect water" |
electrician | Electrician — edits PANEL.md only | "wire the circuit", "the lights don't work", "cablear" |
foreman | Foreman — plans and delegates | "build a whole room", "supervisar obra", "what's the plan?" |
Work through these in order. Each one isolates one teaching point.
npx claudepluginhub aitorpo/claude-code-plugin-sample --plugin workshopComprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
A growing collection of Claude-compatible academic workflow bundles. Covers scientific figures, manuscript writing and polishing, reviewer assessment, citation retrieval, data availability, paper reading, literature search, response letters, paper-to-PPTX conversion, and evidence-grounded Chinese invention patent drafting. Rules are organized as reusable skill folders with explicit workflows and quality checks.
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
Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.