Skip to content

03-installation-and-plugin-selection-strategy.md

Latest commit

 

History

History
93 lines (62 loc) · 3.25 KB

03-installation-and-plugin-selection-strategy.md

File metadata and controls

93 lines (62 loc) · 3.25 KB
layout default
title Chapter 3: Installation and Plugin Selection Strategy
nav_order 3
parent Wshobson Agents Tutorial

Chapter 3: Installation and Plugin Selection Strategy

Welcome to Chapter 3: Installation and Plugin Selection Strategy. In this part of Wshobson Agents Tutorial: Pluginized Multi-Agent Workflows for Claude Code, you will build an intuitive mental model first, then move into concrete implementation details and practical production tradeoffs.

This chapter shows how to choose plugin portfolios by objective instead of installing everything.

Learning Goals

  • select plugins by workflow goal and team constraints
  • build phased installation plans for new teams
  • avoid context bloat from uncontrolled plugin growth
  • align plugin choices with quality and review practices

Strategy Framework

  1. Define your top three recurring workflows.
  2. Map each workflow to one or two primary plugins.
  3. Add one review/governance plugin.
  4. Expand only when command gaps are verified.

Example Portfolio Profiles

Solo Full-Stack Engineer

  • backend-development
  • frontend-mobile-development
  • unit-testing
  • code-review-ai

Platform Team

  • cloud-infrastructure
  • kubernetes-operations
  • cicd-automation
  • security-scanning

Data/LLM Team

  • llm-application-dev
  • data-engineering
  • machine-learning-ops
  • performance-testing-review

Anti-Patterns

  • installing 20+ plugins before validating any workflow
  • adding overlapping plugins without command-level rationale
  • skipping review and security plugins in production-adjacent projects

Source References

Summary

You now have a practical method for controlled plugin adoption.

Next: Chapter 4: Commands, Natural Language, and Workflow Orchestration

Source Code Walkthrough

Note: wshobson/agents stores all behavior in plugin definition files (Markdown/YAML), not compiled source code. Plugin selection strategy is encoded in the catalog and documentation rather than executable functions.

docs/plugins.md

The plugin catalog documentation is the primary reference for this chapter. It lists all available plugins by category (Backend, Frontend, Cloud, Security, etc.) and explains which workflows each plugin supports — the direct basis for the portfolio profiles described in this chapter.

docs/usage.md

The usage guide explains the phased installation approach: start minimal, add plugins when workflow gaps emerge. This documents the anti-patterns around over-installation that this chapter covers.

How These Components Connect

flowchart TD
    A[docs/plugins.md] -->|catalog by category| B[Plugin Selection]
    B -->|solo engineer profile| C[backend + frontend + review plugins]
    B -->|platform team profile| D[cloud + kubernetes + cicd plugins]
    B -->|data/LLM team profile| E[llm + data-engineering + mlops plugins]
    C --> F[controlled installation]
    D --> F
    E --> F
Loading