Claude Buddy

The development lifecycle

Buddy turns a feature into a sequence of explicit steps, each its own slash command. /buddy:foundation establishes the project's principles; /buddy:spec writes the specification; /buddy:plan and /buddy:tasks break it into TDD-ordered work; /buddy:implement executes it red-green-refactor; /buddy:docs and /buddy:commit close it out with documentation and a clean conventional commit.

Twelve personas

Each step is reviewed from a named point of view — Architect, Security, Performance, Scribe, and others — so the work is pressed on for structure, risk, cost and clarity before it ships, not after.

An extensible domain system

A setup step adapts the workflow to a stack: /setup:lifeos installs the foundation, and /setup:mulesoft, /setup:salesforce and /setup:springboot layer in domain-specific conventions. New domains are a template, not a fork.

Test-driven by default

Implementation runs the red-green-refactor loop: write the failing test, make it pass, clean it up. The workflow is the discipline, wired into the tool rather than left to willpower.

Install

Add the marketplace and install the plugins from Claude Code's plugin manager:

/plugin marketplace add rsts-dev/claude-buddy-marketplace
/plugin install setup@claude-buddy-marketplace
/plugin install buddy@claude-buddy-marketplace
/plugin install sdlc@claude-buddy-marketplace

Then install the foundation with /setup:lifeos, and you're ready.