A Claude Code plugin marketplace providing production-validated protocols, specialized agents, and automation frameworks for systematic AI-assisted software development.
This marketplace contains 2 plugins with complementary capabilities:
- Modernize - Complete modernization workflow (assess → plan → execute → improve) with 6 specialized agents
- Autofix - Autonomous GitHub issue resolution with intelligent testing and quality automation
Both plugins feature continuous improvement through retrospective analysis and are universally applicable to any software project. Originally created for .NET framework migrations, these tools work with any language or platform.
/plugin add marketplace https://github.com/laird/agentsInstall modernize plugin (software modernization workflows):
/plugin install modernizeInstall autofix plugin (autonomous GitHub issue resolution):
/plugin install autofixInstall both plugins:
/plugin install modernize autofixAfter installation, commands will be available as slash commands in Claude Code:
- modernize:
/assess,/plan,/modernize,/retro,/retro-apply - autofix:
/fix-github
This repository is Antigravity-native. It includes the .agent/ directory containing all agent rules and workflows, making it compatible with the Antigravity engine out of the box. Converted but not yet tested.
To "install" these agents into another project:
- Copy the
.agent/directory from this repository to the root of your target project. - (Windows Only) Ensure you have a Bash environment (Git Bash or WSL) available for workflows that use shell commands.
- Start using the workflows immediately.
Complete modernization workflow with multi-agent orchestration.
Each command is a comprehensive protocol document (.md file) containing agent coordination, workflows, quality gates, and best practices:
-
/assess- Assessment protocol with viability evaluation (outputsASSESSMENT.md)- 8 assessment dimensions, scoring methodology, recommendation matrix
- Do this first to assess software for potential modernization
-
/plan- Planning protocol with detailed execution strategy (outputsPLAN.md)- Phase breakdown, timeline estimation, risk management, resource allocation
- Do this to propose a modernization plan
-
/modernize- Full modernization protocol with 7-phase workflow- Coordinates 6 specialist agents through Discovery → Security → Architecture → Framework → API → Performance → Documentation
- Do this to execute the plan. If there is no plan it will generate a plan and then execute it.
-
/retro- Retrospective protocol analyzing project history (outputsIMPROVEMENTS.md)- Reviews git history, user corrections, agent mistakes, protocol inefficiencies
- Do this after execution to assess how the project went and make improvement recommendations for future projects. This is optional.
-
/retro-apply- Improvement application protocol- Systematically updates commands, protocols, and automation based on retrospective findings
- Do this after
/retroif you agree with the recommendations.
-
Assess Viability
/assessEvaluates technical debt, risks, and ROI. Outputs
ASSESSMENT.md. -
Create Plan
/planDevelops detailed execution strategy with phases, timeline, and resources. Outputs
PLAN.md. -
Execute Modernization
/modernizeOrchestrates specialized agents through 7 phases:
- Discovery & Planning
- Security Assessment
- Architecture Decisions
- Framework Upgrade
- API Modernization
- Performance Optimization
- Documentation
-
Continuous Improvement (Optional)
/retroAfter project completion, analyzes history to identify process improvements. Reviews:
- User interruptions and corrections
- Agent behavioral issues (wrong tools, wasted effort)
- Protocol inefficiencies
- Automation opportunities
Outputs
IMPROVEMENTS.mdwith 3-5 evidence-based recommendations. -
Apply Improvements
/retro-applySystematically applies approved recommendations from
IMPROVEMENTS.md:- Updates command files with better agent behavior guidance
- Modifies protocols to prevent recurring issues
- Adds automation (scripts, hooks, CI/CD)
- Embeds lessons learned into workflow
The modernize plugin includes 6 specialized agents invoked by Claude Code's Task tool:
- Architect makes technology decisions and creates ADRs
- Security scans for vulnerabilities and blocks on CRITICAL/HIGH issues
- Coder implements migrations and fixes
- Tester validates with comprehensive test suites (100% pass rate required)
- Documentation generates user-facing guides and changelogs
- Migration Coordinator orchestrates multi-stage workflows
Autonomous GitHub issue resolution with intelligent testing and quality automation.
/fix-github - Autonomous issue resolution workflow that:
- Automatically prioritizes GitHub issues using P0-P3 labels
- Detects issue complexity (simple vs complex)
- Uses superpowers skills for complex problems
- Runs regression tests when no issues exist
- Creates improvement proposals when all tests pass
- Self-configures from project's
CLAUDE.md
Key Features:
- Works with any test framework (Jest, Playwright, pytest, etc.)
- Auto-creates configuration if missing
- GitHub integration for test failure tracking
- Priority-based workflow (P0 → P1 → P2 → P3)
- Continuous quality improvement
Usage:
/fix-github
First Run: Automatically adds this configuration to your CLAUDE.md:
## Automated Testing & Issue Management
### Regression Test Suite
```bash
npm run test:regressionnpm run build
**Workflow:**
1. Creates priority labels (P0-P3) if needed
2. Finds highest priority issue
3. Fixes it (uses superpowers for complex issues)
4. Runs tests to verify
5. Commits and closes issue
6. Moves to next issue
7. If no issues: runs full regression test suite
8. Creates GitHub issues from test failures
#### Configuration (Optional)
Customize the auto-generated configuration in your `CLAUDE.md`:
- Update test commands for your project
- Specify test framework details
- Configure report locations
- Define priority patterns
---
## Repository Structure
---
agents/
├── .claude-plugin/ # Plugin marketplace configuration
│ ├── marketplace.json # Marketplace metadata (2 plugins)
│ └── plugins/
│ ├── modernize/
│ │ └── plugin.json # Modernize plugin definition
│ └── autofix/
│ └── plugin.json # Autofix plugin definition
├── plugins/ # Plugin implementations
│ ├── modernize/ # Modernize plugin (5 commands, 6 agents, protocols)
│ │ ├── commands/
│ │ │ ├── assess.md # Assessment protocol
│ │ │ ├── plan.md # Planning protocol
│ │ │ ├── modernize.md # Full modernization workflow
│ │ │ ├── retro.md # Retrospective analysis
│ │ │ └── retro-apply.md # Improvement application
│ │ ├── agents/
│ │ │ ├── architect.md # Technology decisions and ADRs
│ │ │ ├── coder.md # Implementation and fixes
│ │ │ ├── documentation.md # User-facing guides
│ │ │ ├── migration-coordinator.md # Multi-stage orchestration
│ │ │ ├── security.md # Vulnerability scanning
│ │ │ └── tester.md # Comprehensive testing
│ │ └── protocols/ # Protocol documentation (10 protocols)
│ │ ├── 00-PROTOCOL-INDEX.md # Protocol index
│ │ ├── adr-lifecycle.md # ADR lifecycle protocol
│ │ ├── agent-logging.md # Agent logging protocol
│ │ ├── agents-overview.md # Agents overview
│ │ ├── documentation-plan.md # Documentation planning
│ │ ├── documentation-protocol.md # Documentation protocol
│ │ ├── incremental-documentation.md # Incremental docs
│ │ ├── protocols-overview.md # Protocols overview
│ │ ├── security-scanning-protocol.md # Security scanning
│ │ └── testing-protocol.md # Testing protocol
│ └── autofix/ # Autofix plugin (1 command, 6 agents, 1 script)
│ ├── commands/
│ │ └── fix-github.md # Autonomous issue resolution
│ ├── agents/
│ │ ├── architect.md # Technology decisions and ADRs
│ │ ├── coder.md # Implementation and fixes
│ │ ├── documentation.md # User-facing guides
│ │ ├── migration-coordinator.md # Multi-stage orchestration
│ │ ├── security.md # Vulnerability scanning
│ │ └── tester.md # Comprehensive testing
│ └── scripts/
│ └── regression-test.sh # Full test suite with GitHub integration
└── README.md
Structure Notes:
- Parallel plugin architecture: Each plugin has its own commands/, agents/, and scripts/
- Complete separation: Plugins are independent and can be installed individually
- Shared agent definitions: Both plugins include the same 6 specialized agents (architecture, coder, documentation, migration-coordinator, security, tester)
- Self-contained: Each plugin can evolve independently without affecting the other
- ✅ Proven results - Successfully guided 32/32 project migrations
- ✅ Universal applicability - Works with any software project, not just .NET
- ✅ Complete audit trail - HISTORY.md logging for all agent activities
- ✅ Quality gates - Automated validation at each stage
- ✅ Evidence-based evolution - Protocols continuously improved through retrospective analysis
- 🤖 6 specialized agents - Each with defined capabilities and responsibilities
- 🔄 Parallel execution - Multiple agents work independently on separate tasks
- 📊 Enforced quality - 100% test pass rate, security score ≥45/100
- 📝 Systematic workflows - 7-phase migration, 6-phase testing, 8-stage ADR lifecycle
- 🔍 Retrospective analysis - Analyzes git history, user corrections, agent mistakes
- 📈 Evidence-based recommendations - 3-5 specific improvements with quantified impact
- 🔧 Automated application - Updates commands, protocols, and automation
- 🎯 Learning from mistakes - Identifies wrong tool usage, wasted effort, requirement misunderstandings
- ♻️ Self-improving system - Each project makes the next one better
- ⏱️ Measurable impact - Recent improvements saved 27 hours per project
- 32/32 projects migrated successfully (100% success rate)
- 100% test pass rate (meets requirement)
- Security improvement from 0/100 → 45/100 (CRITICAL CVEs eliminated)
- Zero P0/P1 blocking issues in production
- 1,500+ lines of documentation auto-generated
Based on retrospective analysis of RawRabbit modernization, 5 evidence-based improvements were implemented:
-
Front-Load Test Environment Setup ⚡
- Phase 0 test setup now mandatory before any work begins
- Verified baseline metrics (build, tests, vulnerability scan) replace estimates
- Prevents "works on my machine" issues discovered too late
-
Spike-Driven ADR Process 🧪
- New Stage 2.5 for high-risk architectural decisions
- Requires empirical validation via spike branches before commitment
- 24-48hr stakeholder review period enforced
- Better decisions through evidence vs. desk research
-
Shift Security Validation Left 🔒
- New automated security scanning protocol
- Phase 0 baseline scan, continuous monitoring throughout project
- Security scores calculated from actual scans, never estimated
- Critical/High CVEs blocked earlier in workflow
-
Continuous Testing Strategy ✅
- Testing after EVERY stage, not delayed until Stage 4
- Tiered testing: Unit → Component → Integration → Performance
- Estimated 7 hours saved per project from early issue detection
- Issues found in Stage 1 vs Stage 4 dramatically cheaper to fix
-
Incremental Documentation 📝
- Status marker system:
⚠️ In Progress → ✅ Fixed (validated) → 📝 Documented - "Fixed" claims only after test validation passes
- Prevents aspirational documentation requiring corrective commits
- Accurate HISTORY.md audit trail
- Status marker system:
Combined Impact: 27 hours saved per project, earlier issue detection, verified (not estimated) security posture, empirical architectural decisions, and accurate documentation.
Modernization Workflow:
/assess→/plan→/modernize→/retro→/retro-apply- Monitor HISTORY.md for complete audit trail
- Review
IMPROVEMENTS.mdand apply approved changes - Next project benefits from lessons learned
Quality Gates:
- Security score ≥45 before migration starts
- Build success 100% before next stage
- Test pass rate 100% before proceeding
- All P0/P1 issues resolved before release
Autofix Workflow:
- Run
/fix-githubto start autonomous issue resolution - Customize configuration in
CLAUDE.mdas needed - Let it run continuously for ongoing quality improvement
- Framework Upgrades - .NET, Node.js, Python, Java, etc.
- Cloud Migrations - AWS, Azure, GCP platform changes
- Language Migrations - Java to Kotlin, JavaScript to TypeScript
- Database Migrations - SQL to NoSQL, version upgrades
- Legacy Modernization - Monolith to microservices, API updates
- Security Remediation - CVE scanning and vulnerability fixes
- Quality Assurance - Comprehensive testing and validation
- Documentation - Technical docs, migration guides, ADRs
| Version | Date | Changes |
|---|---|---|
| 3.0.0 | 2025-11-24 | Added autofix plugin: Autonomous GitHub issue resolution with /fix-github command. Self-configuring via CLAUDE.md, works with any test framework. Includes regression-test.sh script with GitHub integration. Marketplace now contains 2 plugins (modernize + autofix) |
| 2.6.0 | 2025-11-09 | Applied 5 evidence-based improvements from RawRabbit retrospective: front-load test setup, spike-driven ADRs, shift security left, continuous testing, incremental documentation. Impact: 27 hours saved per project |
| 2.5.0 | 2025-11-01 | Added continuous improvement workflow: /retro and /retro-apply commands for retrospective analysis and automated application of lessons learned |
| 2.4.2 | 2025-10-28 | Renamed /modernize:project to /modernize, removed agents/protocols/scripts in favor of streamlined commands |
| 2.4.1 | 2025-10-25 | Removed cost estimates, added time estimate disclaimers |
| 2.4.0 | 2025-10-25 | Added complete modernization workflow (assess → plan → execute) |
| 2.3.0 | 2025-10-25 | Added /modernize-project multi-agent orchestrator |
| 2.2.0 | 2025-10-25 | Restructured as Claude Code plugin |
| 1.0 | 2025-10-10 | Initial release with protocols and agent definitions |
- Repository: https://github.com/laird/agents
- MADR 3.0.0: https://adr.github.io/madr/ - ADR format specification
- Keep a Changelog: https://keepachangelog.com/ - CHANGELOG format
- Claude Code Docs: https://docs.claude.com/en/docs/claude-code/
MIT License - See repository for details
Status: Production-validated Applicability: Universal (all software projects) Original Context: .NET Framework Migration Maintained By: AI-assisted development community