https://futurewithml.netlify.app
|
This is a web feed, also known as an Atom feed. Subscribe by copying the URL from the address bar into your newsreader. Visit About Feeds to learn more and get started. It's free.
Visit website
Recent posts
Updated on $DATE
date
Productivity
Future With ML - Productivity
Machine Learning Design Patterns, MLOps, and AI Engineering insights by Christian Picon Calderon
Zola2026-01-06T10:00:00+00:00https://futurewithml.netlify.app/tags/productivity/atom.xml
Claude Code Plugin Journey Part 0: Agent Team Creator
2026-01-06T10:00:00+00:00
2026-01-06T10:00:00+00:00
Christian Picon Calderon
https://futurewithml.netlify.app/posts/claude-code-plugin-journey-part0/
<h1 id="claude-code-plugin-journey-part-0-agent-team-creator">Claude Code Plugin Journey Part 0: Agent Team Creator</h1>
<p>What if you could point an AI at your project and have it generate specialists who actually understand your stack? Not generic assistants—agents that know your architecture, your patterns, your conventions.</p>
<p>That’s what <code>agent-team-creator</code> does. Let me show you the workflow.</p>
<span id="continue-reading"></span>
<hr />
<h2 id="scenario-1-generate-your-agent-team">Scenario 1: Generate Your Agent Team</h2>
<p>You start a new project—or join an existing one. The codebase is unfamiliar. You need help, but generic AI advice isn’t cutting it.</p>
<p><strong>Step 1: Generate your agent team</strong></p>
<pre class="z-code"><code><span class="z-text z-plain">/generate-agent-team
</span></code></pre>
<p>Watch as the plugin analyzes your project:</p>
<pre class="z-code"><code><span class="z-text z-plain">Analyzing codebase...
</span><span class="z-text z-plain">├── Languages: Python (75%), TypeScript (20%), SQL (5%)
</span><span class="z-text z-plain">├── Frameworks: FastAPI, React, SQLAlchemy
</span><span class="z-text z-plain">├── Architecture: Monorepo with backend/frontend split
</span><span class="z-text z-plain">├── Patterns: Repository pattern, dependency injection
</span><span class="z-text z-plain">
</span><span class="z-text z-plain">Generating specialized agents...
</span><span class="z-text z-plain">
</span><span class="z-text z-plain">✓ fastapi-expert
</span><span class="z-text z-plain"> Knows: Your endpoint patterns, Pydantic models, middleware stack
</span><span class="z-text z-plain">
</span><span class="z-text z-plain">✓ react-specialist
</span><span class="z-text z-plain"> Knows: Your component library, state management, hook patterns
</span><span class="z-text z-plain">
</span><span class="z-text z-plain">✓ database-architect
</span><span class="z-text z-plain"> Knows: Your SQLAlchemy models, migration patterns, query conventions
</span><span class="z-text z-plain">
</span><span class="z-text z-plain">✓ test-strategist
</span><span class="z-text z-plain"> Knows: Your pytest fixtures, mocking patterns, test utilities
</span><span class="z-text z-plain">
</span><span class="z-text z-plain">Team saved to .claude/agents/
</span></code></pre>
<p><strong>Step 2: Use your agents immediately</strong></p>
<p>Now you have project-aware specialists. Here’s how to use them:</p>
<p><strong>Ask about architecture:</strong></p>
<pre class="z-code"><code><span class="z-text z-plain">Use the fastapi-expert agent to explain how authentication
</span><span class="z-text z-plain">works in this project
</span></code></pre>
<p><strong>Implement a feature:</strong></p>
<pre class="z-code"><code><span class="z-text z-plain">Use the react-specialist agent to help me add a new dashboard
</span><span class="z-text z-plain">component following our existing patterns
</span></code></pre>
<p><strong>Debug an issue:</strong></p>
<pre class="z-code"><code><span class="z-text z-plain">Use the database-architect agent to help me understand why
</span><span class="z-text z-plain">this query is slow - check src/repositories/user_repo.py
</span></code></pre>
<p><strong>Write tests:</strong></p>
<pre class="z-code"><code><span class="z-text z-plain">Use the test-strategist agent to write integration tests for
</span><span class="z-text z-plain">the new payment endpoint following our test conventions
</span></code></pre>
<p><strong>The difference?</strong> These agents don’t give generic advice. They reference <em>your</em> files, <em>your</em> patterns, <em>your</em> conventions.</p>
<hr />
<h2 id="scenario-2-advanced-debugging-workflow">Scenario 2: Advanced Debugging Workflow</h2>
<p>After you’ve generated your agent team, you can create a <strong>Project Debugger</strong>—an orchestrator that coordinates your specialists to diagnose complex issues.</p>
<p><strong>Step 1: Generate the Project Debugger</strong></p>
<pre class="z-code"><code><span class="z-text z-plain">/generate-debugger
</span></code></pre>
<pre class="z-code"><code><span class="z-text z-plain">Discovering project agents...
</span><span class="z-text z-plain">├── Found: fastapi-expert, react-specialist, database-architect, test-strategist
</span><span class="z-text z-plain">
</span><span class="z-text z-plain">Analyzing project architecture...
</span><span class="z-text z-plain">├── Entry points identified
</span><span class="z-text z-plain">├── Error handling patterns mapped
</span><span class="z-text z-plain">├── Logging conventions detected
</span><span class="z-text z-plain">
</span><span class="z-text z-plain">Generating project-debugger.md...
</span><span class="z-text z-plain">
</span><span class="z-text z-plain">✓ Created: .claude/agents/project-debugger.md
</span><span class="z-text z-plain"> - Orchestrates your 4 specialist agents
</span><span class="z-text z-plain"> - Produces structured debugging reports
</span><span class="z-text z-plain"> - Identifies root causes with file:line references
</span></code></pre>
<p><strong>Step 2: Use the Debugger to investigate</strong></p>
<p>When you hit a bug, invoke the project debugger:</p>
<pre class="z-code"><code><span class="z-text z-plain">Use the project-debugger agent to investigate: Users are
</span><span class="z-text z-plain">getting 500 errors when submitting the checkout form
</span></code></pre>
<p>The debugger orchestrates your specialists:</p>
<pre class="z-code"><code><span class="z-text z-plain">Consulting fastapi-expert...
</span><span class="z-text z-plain">├── Traced request flow through api/routes/checkout.py
</span><span class="z-text z-plain">├── Found: PaymentService.process() raises unhandled exception
</span><span class="z-text z-plain">
</span><span class="z-text z-plain">Consulting database-architect...
</span><span class="z-text z-plain">├── Checked transaction handling in repositories/order_repo.py
</span><span class="z-text z-plain">├── Found: Missing rollback on payment failure
</span><span class="z-text z-plain">
</span><span class="z-text z-plain">Consulting test-strategist...
</span><span class="z-text z-plain">├── Reviewed test coverage for checkout flow
</span><span class="z-text z-plain">├── Found: No test for payment failure scenario
</span><span class="z-text z-plain">
</span><span class="z-text z-plain">Generating debugging report...
</span></code></pre>
<p><strong>Step 3: Generate a debugging report</strong></p>
<p>The debugger produces a structured report saved to <code>.claude/reports/debugging/</code> :</p>
<pre data-lang="markdown" class="language-markdown z-code"><code class="language-markdown" data-lang="markdown"><span class="z-text z-html z-markdown"><span class="z-meta z-block-level z-markdown"><span class="z-markup z-heading z-1 z-markdown"><span class="z-punctuation z-definition z-heading z-begin z-markdown">#</span> </span><span class="z-markup z-heading z-1 z-markdown"><span class="z-entity z-name z-section z-markdown">Debugging Report: Checkout 500 Errors</span><span class="z-meta z-whitespace z-newline z-markdown">
</span></span></span></span><span class="z-text z-html z-markdown">
</span><span class="z-text z-html z-markdown"><span class="z-meta z-block-level z-markdown"><span class="z-markup z-heading z-2 z-markdown"><span class="z-punctuation z-definition z-heading z-begin z-markdown">##</span> </span><span class="z-markup z-heading z-2 z-markdown"><span class="z-entity z-name z-section z-markdown">Root Cause</span><span class="z-meta z-whitespace z-newline z-markdown">
</span></span></span></span><span class="z-text z-html z-markdown"><span class="z-meta z-paragraph z-markdown">Missing exception handling in PaymentService.process()
</span></span><span class="z-text z-html z-markdown"><span class="z-meta z-paragraph z-markdown">(src/services/payment.py:45) combined with missing
</span></span><span class="z-text z-html z-markdown"><span class="z-meta z-paragraph z-markdown">transaction rollback (src/repositories/order_repo.py:78)
</span></span><span class="z-text z-html z-markdown"><span class="z-meta z-paragraph z-markdown">
</span></span><span class="z-text z-html z-markdown"><span class="z-meta z-block-level z-markdown"><span class="z-markup z-heading z-2 z-markdown"><span class="z-punctuation z-definition z-heading z-begin z-markdown">##</span> </span><span class="z-markup z-heading z-2 z-markdown"><span class="z-entity z-name z-section z-markdown">Evidence</span><span class="z-meta z-whitespace z-newline z-markdown">
</span></span></span></span><span class="z-text z-html z-markdown"><span class="z-markup z-list z-unnumbered z-bullet z-markdown"><span class="z-punctuation z-definition z-list_item z-markdown">-</span></span><span class="z-markup z-list z-unnumbered z-markdown"> <span class="z-meta z-paragraph z-list z-markdown">File: src/services/payment.py:45-52
</span></span></span><span class="z-text z-html z-markdown"><span class="z-markup z-list z-unnumbered z-markdown"><span class="z-meta z-paragraph z-list z-markdown"></span></span><span class="z-markup z-list z-unnumbered z-bullet z-markdown"><span class="z-punctuation z-definition z-list_item z-markdown">-</span></span><span class="z-markup z-list z-unnumbered z-markdown"><span class="z-meta z-paragraph z-list z-markdown"> File: src/repositories/order_repo.py:78-85
</span></span></span><span class="z-text z-html z-markdown"><span class="z-markup z-list z-unnumbered z-markdown"><span class="z-meta z-paragraph z-list z-markdown"></span></span><span class="z-markup z-list z-unnumbered z-bullet z-markdown"><span class="z-punctuation z-definition z-list_item z-markdown">-</span></span><span class="z-markup z-list z-unnumbered z-markdown"><span class="z-meta z-paragraph z-list z-markdown"> Missing test: tests/integration/test_checkout.py
</span></span></span><span class="z-text z-html z-markdown"><span class="z-markup z-list z-unnumbered z-markdown"><span class="z-meta z-paragraph z-list z-markdown"></span></span><span class="z-markup z-list z-unnumbered z-markdown">
</span></span><span class="z-text z-html z-markdown"><span class="z-markup z-list z-unnumbered z-markdown"></span><span class="z-meta z-block-level z-markdown"><span class="z-markup z-heading z-2 z-markdown"><span class="z-punctuation z-definition z-heading z-begin z-markdown">##</span> </span><span class="z-markup z-heading z-2 z-markdown"><span class="z-entity z-name z-section z-markdown">Recommended Fix</span><span class="z-meta z-whitespace z-newline z-markdown">
</span></span></span></span><span class="z-text z-html z-markdown"><span class="z-markup z-list z-numbered z-bullet z-markdown">1<span class="z-punctuation z-definition z-list_item z-markdown">.</span></span><span class="z-markup z-list z-numbered z-markdown"> <span class="z-meta z-paragraph z-list z-markdown">Add try/except in payment.py:45
</span></span></span><span class="z-text z-html z-markdown"><span class="z-markup z-list z-numbered z-markdown"><span class="z-meta z-paragraph z-list z-markdown"></span></span><span class="z-markup z-list z-numbered z-bullet z-markdown">2<span class="z-punctuation z-definition z-list_item z-markdown">.</span></span><span class="z-markup z-list z-numbered z-markdown"><span class="z-meta z-paragraph z-list z-markdown"> Implement rollback in order_repo.py:78
</span></span></span><span class="z-text z-html z-markdown"><span class="z-markup z-list z-numbered z-markdown"><span class="z-meta z-paragraph z-list z-markdown"></span></span><span class="z-markup z-list z-numbered z-bullet z-markdown">3<span class="z-punctuation z-definition z-list_item z-markdown">.</span></span><span class="z-markup z-list z-numbered z-markdown"><span class="z-meta z-paragraph z-list z-markdown"> Add failure scenario test
</span></span></span><span class="z-text z-html z-markdown"><span class="z-markup z-list z-numbered z-markdown"><span class="z-meta z-paragraph z-list z-markdown"></span></span><span class="z-markup z-list z-numbered z-markdown">
</span></span><span class="z-text z-html z-markdown"><span class="z-markup z-list z-numbered z-markdown"></span><span class="z-meta z-block-level z-markdown"><span class="z-markup z-heading z-2 z-markdown"><span class="z-punctuation z-definition z-heading z-begin z-markdown">##</span> </span><span class="z-markup z-heading z-2 z-markdown"><span class="z-entity z-name z-section z-markdown">Side Effects</span><span class="z-meta z-whitespace z-newline z-markdown">
</span></span></span></span><span class="z-text z-html z-markdown"><span class="z-markup z-list z-unnumbered z-bullet z-markdown"><span class="z-punctuation z-definition z-list_item z-markdown">-</span></span><span class="z-markup z-list z-unnumbered z-markdown"> <span class="z-meta z-paragraph z-list z-markdown">Orders may be in inconsistent state (needs migration)
</span></span></span></code></pre>
<p><strong>Step 4: Create a Jira ticket from the report</strong></p>
<p>Now turn that report into a Jira task. The command automatically finds the most recent debugging report:</p>
<pre class="z-code"><code><span class="z-text z-plain">/generate-jira-task
</span></code></pre>
<pre class="z-code"><code><span class="z-text z-plain">Finding latest debugging report...
</span><span class="z-text z-plain">├── Found: .claude/reports/debugging/report-2026-01-06-1430.md
</span><span class="z-text z-plain">
</span><span class="z-text z-plain">Loading debugging report...
</span><span class="z-text z-plain">
</span><span class="z-text z-plain">Checking for similar issues...
</span><span class="z-text z-plain">├── Searching: "checkout payment exception rollback"
</span><span class="z-text z-plain">├── Found 2 potentially related issues:
</span><span class="z-text z-plain">
</span><span class="z-text z-plain"> PROJ-234: "Payment processing timeout errors"
</span><span class="z-text z-plain"> Status: In Progress
</span><span class="z-text z-plain">
</span><span class="z-text z-plain"> PROJ-189: "Checkout form validation issues"
</span><span class="z-text z-plain"> Status: Done
</span><span class="z-text z-plain">
</span><span class="z-text z-plain">How would you like to proceed?
</span><span class="z-text z-plain">> Create new task anyway
</span><span class="z-text z-plain">> Abort - I'll update an existing issue
</span></code></pre>
<p>If you choose to create a new task:</p>
<pre class="z-code"><code><span class="z-text z-plain">Creating Jira issue...
</span><span class="z-text z-plain">✓ Created: PROJ-456 "Fix checkout 500 errors: missing exception handling"
</span><span class="z-text z-plain"> https://yourcompany.atlassian.net/browse/PROJ-456
</span></code></pre>
<p>The duplicate check prevents cluttering your backlog with related issues. If the bug is a variant of an existing issue, you can update that ticket instead of creating a new one.</p>
<p><strong>No Jira configured?</strong> The command gracefully falls back to generating a ready-to-paste markdown file in <code>.claude/reports/jira-drafts/</code>.</p>
<hr />
<h2 id="scenario-3-repeatable-workflow-for-multiple-bugs">Scenario 3: Repeatable Workflow for Multiple Bugs</h2>
<p>Each bug investigation creates its own debugging report, which leads to its own Jira ticket. Here’s how the workflow scales across multiple issues:</p>
<p><strong>Monday: API performance issue</strong></p>
<pre class="z-code"><code><span class="z-text z-plain">Use the project-debugger agent to investigate: Why are
</span><span class="z-text z-plain">API response times spiking during peak hours?
</span></code></pre>
<p>Report saved: <code>.claude/reports/debugging/report-2026-01-06-0900.md</code></p>
<pre class="z-code"><code><span class="z-text z-plain">/generate-jira-task
</span></code></pre>
<p>Created: <code>PROJ-457 "Optimize database connection pooling for peak load"</code></p>
<hr />
<p><strong>Tuesday: Frontend rendering bug</strong></p>
<pre class="z-code"><code><span class="z-text z-plain">Use the project-debugger agent to investigate: The dashboard
</span><span class="z-text z-plain">chart isn't updating when new data arrives
</span></code></pre>
<p>Report saved: <code>.claude/reports/debugging/report-2026-01-07-1100.md</code></p>
<pre class="z-code"><code><span class="z-text z-plain">/generate-jira-task
</span></code></pre>
<p>Created: <code>PROJ-458 "Fix React state synchronization in DashboardChart component"</code></p>
<hr />
<p><strong>Wednesday: Authentication edge case</strong></p>
<pre class="z-code"><code><span class="z-text z-plain">Use the project-debugger agent to investigate: Users are
</span><span class="z-text z-plain">being logged out randomly after password changes
</span></code></pre>
<p>Report saved: <code>.claude/reports/debugging/report-2026-01-08-1400.md</code></p>
<pre class="z-code"><code><span class="z-text z-plain">/generate-jira-task
</span></code></pre>
<p>Created: <code>PROJ-459 "Handle session invalidation on password change correctly"</code></p>
<hr />
<p>Each investigation is independent. The debugger creates timestamped reports, and <code>/generate-jira-task</code> always picks up the most recent one. Your debugging history accumulates in <code>.claude/reports/debugging/</code>, giving you a searchable archive of past investigations.</p>
<hr />
<h2 id="the-complete-workflow">The Complete Workflow</h2>
<div class="workflow-container" id="workflow">
<canvas class="workflow-canvas" aria-label="Workflow visualization"></canvas>
</div>
<script>
(function() {
const containerId = 'workflow';
// Decode HTML entities (Tera encodes / as /)
function decodeHTML(str) {
const textarea = document.createElement('textarea');
textarea.innerHTML = str;
return textarea.value;
}
const stepsData = [
{ title: decodeHTML('/generate-agent-team'), desc: decodeHTML('Creates specialist agents') },
{ title: decodeHTML('Use agents daily'), desc: decodeHTML('fastapi-expert react-specialist') },
{ title: decodeHTML('/generate-debugger'), desc: decodeHTML('Creates project-debugger') },
{ title: decodeHTML('Debug issues'), desc: decodeHTML('Saves to .claude/reports/') },
{ title: decodeHTML('/generate-jira-task'), desc: decodeHTML('Creates Jira ticket') }
];
function initWorkflow() {
const container = document.getElementById(containerId);
if (!container) return;
const canvas = container.querySelector('.workflow-canvas');
const ctx = canvas.getContext('2d');
let particles = [];
let time = 0;
const colors = {
primary: '#00d4ff',
secondary: '#8b5cf6',
accent: '#00ff88',
particle: '#00ff88',
connection: 'rgba(0, 212, 255, 0.4)',
text: '#e0e0e4',
subtext: '#8888a0'
};
function resize() {
const rect = container.getBoundingClientRect();
canvas.width = rect.width;
canvas.height = Math.max(550, stepsData.length * 130 + 100);
container.style.height = canvas.height + 'px';
}
resize();
window.addEventListener('resize', resize);
function getStepPositions() {
const centerX = canvas.width / 2;
const startY = 70;
const stepHeight = 120;
return stepsData.map((step, i) => ({
...step,
x: centerX,
y: startY + i * stepHeight,
width: Math.min(450, canvas.width * 0.85),
height: 90,
color: i % 2 === 0 ? colors.primary : colors.secondary
}));
}
function createParticle(from, to) {
return {
fromX: from.x,
fromY: from.y + from.height / 2,
toX: to.x,
toY: to.y - to.height / 2,
progress: Math.random(),
speed: 0.008 + Math.random() * 0.004
};
}
function draw() {
ctx.clearRect(0, 0, canvas.width, canvas.height);
const positions = getStepPositions();
// Draw connections
ctx.strokeStyle = colors.connection;
ctx.lineWidth = 3;
for (let i = 0; i < positions.length - 1; i++) {
const from = positions[i];
const to = positions[i + 1];
ctx.beginPath();
ctx.moveTo(from.x, from.y + from.height / 2);
ctx.lineTo(to.x, to.y - to.height / 2);
ctx.stroke();
// Arrow
const midY = (from.y + from.height / 2 + to.y - to.height / 2) / 2;
ctx.fillStyle = colors.connection;
ctx.beginPath();
ctx.moveTo(from.x - 6, midY - 4);
ctx.lineTo(from.x, midY + 6);
ctx.lineTo(from.x + 6, midY - 4);
ctx.closePath();
ctx.fill();
}
// Draw step boxes
positions.forEach((pos, i) => {
const x = pos.x - pos.width / 2;
const y = pos.y - pos.height / 2;
// Glow
ctx.shadowColor = pos.color;
ctx.shadowBlur = 20;
// Box with rounded corners
ctx.fillStyle = pos.color;
ctx.beginPath();
const radius = 8;
ctx.moveTo(x + radius, y);
ctx.lineTo(x + pos.width - radius, y);
ctx.quadraticCurveTo(x + pos.width, y, x + pos.width, y + radius);
ctx.lineTo(x + pos.width, y + pos.height - radius);
ctx.quadraticCurveTo(x + pos.width, y + pos.height, x + pos.width - radius, y + pos.height);
ctx.lineTo(x + radius, y + pos.height);
ctx.quadraticCurveTo(x, y + pos.height, x, y + pos.height - radius);
ctx.lineTo(x, y + radius);
ctx.quadraticCurveTo(x, y, x + radius, y);
ctx.closePath();
ctx.fill();
ctx.shadowBlur = 0;
// Border
ctx.strokeStyle = colors.accent;
ctx.lineWidth = 2;
ctx.stroke();
// Step number
ctx.fillStyle = '#0a0a0f';
ctx.font = 'bold 18px JetBrains Mono, monospace';
ctx.textAlign = 'left';
ctx.textBaseline = 'middle';
ctx.fillText((i + 1) + '.', x + 16, pos.y);
// Title
ctx.fillStyle = '#0a0a0f';
ctx.font = 'bold 16px JetBrains Mono, monospace';
ctx.textAlign = 'center';
ctx.fillText(pos.title, pos.x + 12, pos.y - 10);
// Description (if exists)
if (pos.desc) {
ctx.fillStyle = 'rgba(10, 10, 15, 0.8)';
ctx.font = '14px JetBrains Mono, monospace';
ctx.fillText(pos.desc, pos.x + 12, pos.y + 16);
}
});
// Update and draw particles
particles.forEach(p => {
p.progress += p.speed;
if (p.progress >= 1) {
p.progress = 0;
}
const ease = p.progress * p.progress * (3 - 2 * p.progress);
const x = p.fromX + (p.toX - p.fromX) * ease;
const y = p.fromY + (p.toY - p.fromY) * ease;
ctx.fillStyle = colors.particle;
ctx.shadowColor = colors.particle;
ctx.shadowBlur = 12;
ctx.beginPath();
ctx.arc(x, y, 4, 0, Math.PI * 2);
ctx.fill();
ctx.shadowBlur = 0;
});
time++;
requestAnimationFrame(draw);
}
// Initialize particles
const positions = getStepPositions();
for (let i = 0; i < positions.length - 1; i++) {
const p = createParticle(positions[i], positions[i + 1]);
p.progress = i * 0.3;
particles.push(p);
}
if (!window.matchMedia('(prefers-reduced-motion: reduce)').matches) {
draw();
} else {
// Static version
const positions = getStepPositions();
positions.forEach((pos, i) => {
const x = pos.x - pos.width / 2;
const y = pos.y - pos.height / 2;
ctx.fillStyle = pos.color;
ctx.beginPath();
ctx.roundRect(x, y, pos.width, pos.height, 8);
ctx.fill();
ctx.fillStyle = '#0a0a0f';
ctx.font = 'bold 16px JetBrains Mono';
ctx.textAlign = 'center';
ctx.fillText(pos.title, pos.x, pos.y);
});
}
}
if (document.readyState === 'loading') {
document.addEventListener('DOMContentLoaded', initWorkflow);
} else {
initWorkflow();
}
})();
</script>
<style>
.workflow-container {
background: var(--bg-0);
border: 1px solid var(--divider-color);
border-radius: 12px;
padding: 1rem;
margin: 1.5rem 0;
position: relative;
min-height: 550px;
}
.workflow-canvas {
width: 100%;
display: block;
}
@media (max-width: 768px) {
.workflow-container {
padding: 0.5rem;
}
}
</style>
<hr />
<h2 id="quick-start">Quick Start</h2>
<h3 id="installation">Installation</h3>
<p>Install directly from the GitHub marketplace—no cloning required:</p>
<pre data-lang="bash" class="language-bash z-code"><code class="language-bash" data-lang="bash"><span class="z-source z-shell z-bash"><span class="z-comment z-line z-number-sign z-shell"><span class="z-punctuation z-definition z-comment z-begin z-shell">#</span></span><span class="z-comment z-line z-number-sign z-shell"> Add the marketplace (one-time setup)</span><span class="z-comment z-line z-number-sign z-shell">
</span></span><span class="z-source z-shell z-bash"><span class="z-meta z-function-call z-shell"><span class="z-variable z-function z-shell">/plugin</span></span><span class="z-meta z-function-call z-arguments z-shell"> marketplace add Cpicon/claude-code-plugins</span>
</span><span class="z-source z-shell z-bash">
</span><span class="z-source z-shell z-bash"><span class="z-comment z-line z-number-sign z-shell"><span class="z-punctuation z-definition z-comment z-begin z-shell">#</span></span><span class="z-comment z-line z-number-sign z-shell"> Install the plugin</span><span class="z-comment z-line z-number-sign z-shell">
</span></span><span class="z-source z-shell z-bash"><span class="z-meta z-function-call z-shell"><span class="z-variable z-function z-shell">/plugin</span></span><span class="z-meta z-function-call z-arguments z-shell"> install agent-team-creator</span>
</span></code></pre>
<p>That’s it. The plugin is ready to use immediately.</p>
<h3 id="first-commands">First Commands</h3>
<ol>
<li>Navigate to your project</li>
<li>Run <code>/generate-agent-team</code> to create your specialist agents</li>
<li>Start using your specialists: <code>Use the [agent-name] agent to...</code></li>
<li>Run <code>/generate-debugger</code> to create your project debugger</li>
<li>Use the debugger to investigate bugs: <code>Use the project-debugger agent to investigate...</code></li>
<li>Run <code>/generate-jira-task</code> to convert the debugging report to a ticket</li>
</ol>
<hr />
<h2 id="what-you-get">What You Get</h2>
<table><thead><tr><th>Command</th><th>Output</th><th>Value</th></tr></thead><tbody>
<tr><td><code>/generate-agent-team</code></td><td>3-6 specialist agents</td><td>Project-aware help for features, questions, debugging</td></tr>
<tr><td><code>/generate-debugger</code></td><td>Orchestrator agent</td><td>Coordinates specialists for complex investigations</td></tr>
<tr><td><code>/generate-jira-task</code></td><td>Jira ticket or markdown</td><td>Auto-finds latest report, creates actionable ticket</td></tr>
</tbody></table>
<h3 id="time-savings">Time Savings</h3>
<table><thead><tr><th>Task</th><th>Before</th><th>After</th></tr></thead><tbody>
<tr><td>Get project-aware help</td><td>N/A (generic only)</td><td>Immediate</td></tr>
<tr><td>Debug complex issues</td><td>Hours of investigation</td><td>Structured reports</td></tr>
<tr><td>Write Jira tickets</td><td>15-30 min</td><td>2-5 min</td></tr>
</tbody></table>
<hr />
<h2 id="try-it-yourself">Try It Yourself</h2>
<p>The plugin is open source and available on GitHub: <a href="https://github.com/Cpicon/claude-code-plugins">Cpicon/claude-code-plugins</a></p>
<p>Install it with two commands, run <code>/generate-agent-team</code>, and see what specialists emerge for your project.</p>
<h3 id="contributing-feedback">Contributing & Feedback</h3>
<p>Have ideas for improvements? Found a bug? The <a href="https://github.com/Cpicon/claude-code-plugins/issues">GitHub Issues</a> tab is where you can:</p>
<ul>
<li><strong>Request features</strong> — Suggest new capabilities or enhancements</li>
<li><strong>Report bugs</strong> — Help improve reliability by reporting issues you encounter</li>
<li><strong>Discuss improvements</strong> — Share ideas for plugin maintenance and development</li>
</ul>
<p>Your feedback shapes the plugin’s roadmap.</p>
<p>In <a href="/posts/claude-code-plugin-journey-part1/">Part 1</a>, I’ll show you how I built this plugin—the bugs I hit, the patterns I discovered, and why the architecture works the way it does.</p>
<hr />
<p><strong>Series Navigation:</strong></p>
<ul>
<li><strong>Part 0</strong> (You are here): What the plugin does and how to use it</li>
<li><strong>Part 1</strong>: <a href="/posts/claude-code-plugin-journey-part1/">The Hybrid Architecture Pattern</a> — Building the plugin</li>
<li><strong>Part 2</strong>: <a href="/posts/claude-code-plugin-journey-part2/">The Inheritance Paradox</a> — Research insights</li>
</ul>
Claude Code Plugin Journey Part 0: Agent Team Creator
What if you could point an AI at your project and have it generate specialists who actually understand your stack? Not generic assistants—agents that know your architecture, your patterns, your conventions.
That’s what agent-team-creator does. Let me show you the workflow.
…