Agronod Plugins Marketplace

Which plugins should I install, and what does each one unlock? This guide maps Agronod's plugin ecosystem to the workflows they enable.

Installation

Add the marketplace and install plugins using slash commands:

/plugin marketplace add agronod/claude-plugins
/plugin install dev@agronod-plugins
/plugin install git@agronod-plugins
/plugin install steering@agronod-plugins

After installation, plugins' commands become available as slash commands and agents activate automatically when relevant.

Manage plugins anytime with /plugin.

Foundation and Composition

Install dev first—it's the foundation. It provides seven specialist agents, nineteen skills, and multi-agent team orchestration that other plugins compose against. Once dev is installed, run /dev:setup to validate your environment. See the Dev Plugin reference for the full agent roster, skill list, and activation matrix.

After dev, add git for conventional commits and structured PRs. Specialized plugins (steering, specs, infra, etc.) are installed on demand based on your workflows.

Available Plugins

Plugin	Purpose
dev	Foundation: agents, skills, team orchestration
git	Conventional commits and structured pull requests
github-admin	GitHub workflow setup and repository administration
infra	Kubernetes diagnostics, pod debugging, log analysis
jira	Track ticket status and integrate Jira with your workflow
memory	Persist project context and learnings across sessions
meta	Adversarial analysis and hypothesis testing
reporting	Generate professional monthly reports for stakeholders
specs	Spec-driven development: requirements → plan → implementation
steering	Initialize and sync project AI context for consistency
utils	Scratchpads, AI guidance, and feedback tools
analysis	Data and code analysis workflows
assistant	Conversation helpers and prompt templates

Key Workflows

Spec-Driven Development

Before you write code, capture intent with the stakeholders. When kicking off a new feature or sizing an unknown problem, /specs:prd runs a Socratic interview that captures problem statement, success criteria, scope, and constraints as a structured artifact. Subsequent phases (/specs:plan, /specs:blueprint, /specs:build) translate that spec into a plan and implementation.

/specs:prd "Feature: add user authentication"

See Spec-Driven Development for the full four-phase workflow and artifact structure.

Git Workflows

When you've finished work, encode it as a conventional commit with full context. /git:commit generates a message that captures the fix or feature and its motivation, making the git history readable. For PRs, /git:pr structures your description so reviewers understand scope and reasoning.

/git:commit "fix: resolve authentication timeout on slow networks"
/git:pr --title "Add caching layer" --body "Improves latency by 40%"

Context Management

When starting a project or after major changes, sync your AI context so Claude understands the codebase's shape and conventions. /steering:init initializes context from scratch; /steering:sync updates it when the codebase has drifted from the documented state.

/steering:init
/steering:sync

Related

• Spec-Driven Development — Four-phase workflow and artifact structure
• Plugin Component Model — Commands, Skills, and Agents architecture
• MCP Installation — Install individual MCP servers
• MCP Overview — Understand MCP protocol and tool discovery
• Troubleshooting — Solve plugin activation and command issues