catalyst
Private Claude Code plugin marketplace. Hosts the Catalyst family of multi-agent SDLC and workflow plugins.
Repository layout
catalyst-agentic-sdlc/ # repo root = marketplace root
├── .claude-plugin/
│ └── marketplace.json # marketplace catalog (name: "catalyst")
└── plugins/
├── catalyst-sdlc-framework/ # plugin: Cognitive Council SDLC framework
│ ├── .claude-plugin/plugin.json
│ ├── agents/ # 7 council experts + structured-logging-architect
│ └── commands/ # /sdlc-council, /sdlc-council-quick
├── ticket-workflows/ # plugin: structured ticket workflow
│ ├── .claude-plugin/plugin.json # ships PostToolUse/PreToolUse/Stop hooks
│ ├── agents/ # dev, review, qa, coverage
│ ├── commands/ # begin, status, review, qa, tech-compare, wrapup, dev
│ └── templates/ # context, pr-description, qa-report
└── catalyst-meta/ # plugin: global commands, hooks, MCP servers
├── .claude-plugin/plugin.json # wires SessionStart/PreCompact/PreToolUse hooks
├── .mcp.json # bundled MCP server stack
├── commands/ # memory-status, init-memory, save-context, optimize
├── hooks/ # workstream-briefing, pre/post-compact, git-guard
└── docs/ # memory-architecture reference
The repo follows the multi-plugin marketplace pattern from the Claude Code plugin marketplace docs: a single marketplace.json at the root lists every plugin, each plugin lives under plugins/<name>/ with its own .claude-plugin/plugin.json and component directories (agents/, commands/, skills/, hooks/).
Install
# During development (local path)
/plugin marketplace add /Users/panda/catalyst-devspace/workspace/catalyst-sdlc-framework
# From GitHub
/plugin marketplace add TheBranchDriftCatalyst/catalyst-agentic-sdlc
/plugin install catalyst-sdlc-framework@catalyst
/plugin install ticket-workflows@catalyst
/plugin install catalyst-meta@catalyst
Installed plugins are cached at ~/.claude/plugins/cache/ — re-run /plugin marketplace update catalyst after structural changes to pull updated manifests.
Plugin: catalyst-sdlc-framework
A 6-expert Cognitive Council that decomposes epics and features into structured, sequenced SDLC task manifests through a strict 5-phase deliberation protocol. The goal is to surface dissent, prevent groupthink, and produce a manifest a delivery team can turn into tickets without further refinement.
Slash commands
| Command | Purpose |
|---|
/sdlc-council <epic> | Full council deliberation — all 5 phases, all 6 experts. Use for complex initiatives where consensus quality matters. |
/sdlc-council-quick <epic> | Single-pass decomposition for straightforward features. Faster and cheaper, no cross-critique. |
The 6 experts
| Agent | Perspective |
|---|
sdlc-systems-architect | Component boundaries, API contracts, data models, integration points |
sdlc-impl-engineer | Code-level granularity, effort, sequencing, developer experience |
sdlc-qa-strategist | Test coverage, acceptance criteria, edge cases, quality gates |
sdlc-devops-delivery | CI/CD, infrastructure, release strategy, feature flags |
sdlc-product-design | User journeys, story mapping, value delivery sequencing |
sdlc-red-team | Adversarial — challenges necessity, finds scope creep, argues for minimum viable scope |
Additional design agents
| Agent | Purpose |
|---|
structured-logging-architect | Senior observability engineer — designs structured logging for Elasticsearch/Datadog. Invoke directly when needed. |
The 5-phase protocol
