cpicon-claude-plugins

Claude Code Plugins

A collection of Claude Code plugins for software development lifecycle improvement.

Quality Marketplace - Curated plugins that enhance Claude Code with specialized capabilities for code analysis, debugging, project management, and development workflow automation.

---

Vision

flowchart LR
    subgraph "Development Lifecycle"
        A["Analyze"] --> B["Debug"]
        B --> C["Plan"]
        C --> D["Track"]
        D --> E["Review"]
        E --> A
    end

    subgraph "Plugin Support"
        P1["agent-team-creator"]
        P2["Future Plugins"]
    end

    P1 -.-> A
    P1 -.-> B
    P1 -.-> C
    P1 -.-> D
    P2 -.-> E

This marketplace provides plugins that augment Claude Code throughout the software development lifecycle:

Phase	Current Support	Future Plugins
Analyze	/generate-agent-team - Create domain experts	Code metrics, dependency analysis
Debug	/generate-debugger - Orchestrated investigation	Performance profiling, log analysis
Plan	Implementation planning agents	Sprint planning, estimation
Track	/generate-jira-task - Issue creation & updates	Multi-tracker support, status sync
Sync	/update-generated-report - Jira feedback loop	Bidirectional sync
Review	Debugging reports with solutions	PR review, code quality gates

---

Available Plugins

agent-team-creator

Automatically analyze your codebase and generate a team of specialized Claude Code agents that are experts on your specific project.

flowchart TD
    subgraph "Agent Team Creator"
        CMD1["/generate-agent-team"]
        CMD2["/generate-debugger"]
        CMD3["/generate-jira-task"]
        CMD4["/update-generated-report"]
    end

    subgraph "Generated Artifacts"
        A1["Specialist Agents"]
        A2["Debugger Orchestrator"]
        A3["Jira Tasks"]
    end

    subgraph "Project Assets"
        P1[".claude/agents/"]
        P2[".claude/reports/"]
    end

    CMD1 --> A1 --> P1
    CMD2 --> A2 --> P1
    A2 -.-> P2
    CMD3 --> A3
    P2 -.-> CMD3
    CMD4 -.-> P2
    A3 -.-> CMD4

Features:

• Deep codebase analysis (tech stack, architecture, patterns)
• Dynamic team generation based on project complexity
• Project-specific debugging with orchestration patterns
• Jira integration for issue tracking
• Agents saved directly to .claude/agents/ for immediate use

Commands:

/generate-agent-team

Analyze your project and create specialized agents based on:

• Tech stack (frameworks, libraries, languages)
• Architecture patterns (monolith, microservices, etc.)
• Domain knowledge (business logic, data models)

/generate-debugger

Generate a project-specific debugger agent that:

• Discovers all existing project agents in .claude/agents/
• Creates orchestration patterns tailored to YOUR project architecture
• Coordinates investigation by delegating to specialist agents
• Produces structured reports with:
  • Root cause analysis
  • Investigation trail (which agents were consulted)
  • Side effects and warnings
  • Solutions ordered by effort (quick/proper/comprehensive)
• Saves reports to .claude/reports/debugging/ for downstream processing

/generate-jira-task

Transform debugging reports into well-structured Jira tasks, or update existing ones:

• Reads debugging reports from .claude/reports/debugging/
• Detects YAML frontmatter with jira_key to enter update mode automatically
• In update mode: posts new findings as a Jira comment (not a new issue)
• In create mode: creates a new Jira issue and writes jira_key back to the report
• Invokes implementation-planner and jira-writer agents
• Falls back to markdown draft when Atlassian MCP is unavailable

/update-generated-report

Pull Jira feedback into local debugging reports:

• Accepts a Jira key (PROJ-123), report path, or runs interactively
• Fetches Jira issue comments via Atlassian MCP
• Consults project specialist agents with the new feedback
• Appends a Timeline History session to the report
• Does NOT push to Jira — run /generate-jira-task afterward to sync back

flowchart LR
    A["Debug Issue"] --> B["Debugging Report"]
    B --> C["/generate-jira-task"]
    C --> D{"MCP Available?"}
    D -->|Yes| E["Jira Issue Created"]
    D -->|No| F["Markdown Draft"]
    E -->|"Engineer comments"| G["/update-generated-report"]
    G -->|"Updates report"| B

Core Debugger Rules:

• Coordinates, doesn't implement - delegates to specialists
• Evidence-based - requires file:line references
• Synthesizes findings across agents
• Considers system-wide impact

View plugin details

---

Plugin Roadmap

Planned plugins to extend the Quality Marketplace: