Ryan Rozich's personal development workflow for Claude Code, now open sourced and packaged as a Claude Code plugin marketplace.
This is the workspace I use daily for AI-assisted development. It's battle-tested on real projects and optimized for efficient, context-aware AI collaboration. I'm sharing it so others can use it, fork it, and contribute ideas back.
Catalyst integrates with your development tools through both CLI-based (token-efficient) and MCP-based (richer features) approaches:
- Linear - Issue tracking, sprint planning, ticket lifecycle (CLI via Linearis)
catalyst-dev: Core research agents and workflow commandscatalyst-pm: Advanced PM workflows (cycle analysis, milestone tracking, backlog grooming)
- GitHub - Pull requests, code review, repository management (CLI via
gh)catalyst-dev: PR creation, branch management, worktree workflows
- Sentry - Production error monitoring, stack traces, root cause analysis (MCP + CLI)
catalyst-debugging: Sentry MCP integration (~20k tokens when enabled)- Supports single-project and multi-project configurations
- Railway - Deployment logs, service health, environment variables (CLI via
railway)catalyst-dev: Railway research agent for deployment investigation
- PostHog - User behavior, conversion funnels, feature analytics (MCP)
catalyst-analytics: PostHog MCP integration (~40k tokens when enabled)
- Context7 - Library documentation lookup (MCP, ~2k tokens)
catalyst-dev: Built-in, always available
- DeepWiki - GitHub repository documentation (MCP, ~1.5k tokens)
catalyst-dev: Built-in, always available
- Exa - Web research and external documentation (API)
catalyst-dev: External research agent
- HumanLayer - Persistent memory, shared context, team collaboration (CLI via
humanlayer)- All plugins: Foundation for research, plans, handoffs, and reports
Why CLI + lightweight MCP? Most development sessions don't need heavy integrations:
- Start with
catalyst-dev(~3.5k tokens): Core workflow + Linear + GitHub + Railway - Enable
catalyst-analyticswhen analyzing user behavior (~+40k tokens) - Enable
catalyst-debuggingwhen investigating production errors (~+20k tokens) - Disable when done to free context for code and conversation
This keeps your typical session lean while having powerful tools available when needed.
Catalyst is a 5-plugin system for Claude Code focused on token efficiency, session-aware MCP management, and persistent context through parallel agent research, structured handoffs, and shared memory systems.
catalyst-dev (Core - Always enabled)
- 11 research agents (codebase + infrastructure)
- 18 commands covering full dev lifecycle
- Linear integration via Linearis CLI
- Handoff system for context persistence
- ~3.5k context (lightweight MCPs: DeepWiki, Context7)
catalyst-pm (Optional - Enable for project management)
- Linear-focused project management workflows
- 5 commands: analyze-cycle, analyze-milestone, report-daily, groom-backlog, sync-prs
- Research-first architecture (Haiku for data, Sonnet for analysis)
- 5 specialized agents: linear-research, cycle-analyzer, milestone-analyzer, backlog-analyzer, github-linear-analyzer
- Cycle management and milestone tracking with target date feasibility
- Actionable insights and recommendations (not just data dumps)
catalyst-analytics (Optional - Enable when needed)
- PostHog MCP integration (~40k context)
- Product analytics and user behavior analysis
- Conversion funnels and cohort analysis
- 3 specialized analytics commands
catalyst-debugging (Optional - Enable when needed)
- Sentry MCP integration (~20k context)
- Production error monitoring and debugging
- Stack trace analysis and root cause detection
- 3 specialized debugging commands
catalyst-meta (Optional - For advanced users)
- Discover workflows from community repos
- Import and adapt patterns
- Create new workflows
Get started in 5 minutes with the unified setup script:
# Download the setup script
curl -O https://raw.githubusercontent.com/coalesce-labs/catalyst/main/setup-catalyst.sh
chmod +x setup-catalyst.sh
# Run it (requires interactive input)
./setup-catalyst.shThis script will guide you through:
- ✅ Prerequisites check and installation (HumanLayer CLI, jq, etc.)
- ✅ Thoughts repository setup (one per org, backed up to GitHub)
- ✅ Project configuration (ticket prefix, project name)
- ✅ Integration setup (Linear, Sentry, Railway, PostHog, Exa)
- ✅ Worktree directory creation
- ✅ HumanLayer thoughts initialization and syncing
Then install the plugins:
# In Claude Code:
/plugin marketplace add coalesce-labs/catalyst
/plugin install catalyst-dev
# Restart Claude CodeYou're ready! Try /research-codebase in your next session.
See QUICKSTART.md for detailed setup instructions.
Alternatively, install plugins manually via Claude Code plugin system:
# Add the marketplace repository
/plugin marketplace add coalesce-labs/catalyst
# Install core workflow (required)
/plugin install catalyst-dev
# Optional: Install PM plugin (Linear project management)
/plugin install catalyst-pm
# Optional: Install analytics plugin (if you use PostHog)
/plugin install catalyst-analytics
# Optional: Install debugging plugin (if you use Sentry)
/plugin install catalyst-debugging
# Optional: Install meta plugin (workflow discovery)
/plugin install catalyst-metaPlugins automatically load/unload MCPs when enabled/disabled:
# Enable PM tools for sprint planning and cycle reviews
/plugin enable catalyst-pm # Lightweight CLI-based, minimal context
# Enable analytics when analyzing user behavior
/plugin enable catalyst-analytics # Loads PostHog MCP (+40k context)
# Disable when done to free context
/plugin disable catalyst-analytics # Unloads PostHog MCP (-40k context)
# Enable debugging for incident response
/plugin enable catalyst-debugging # Loads Sentry MCP (+20k context)
# Can enable multiple plugins simultaneously
/plugin enable catalyst-pm catalyst-analytics catalyst-debuggingWhy this matters: Most development sessions don't need analytics or debugging MCPs. Starting
with just catalyst-dev keeps your context at ~3.5k tokens instead of ~65k, leaving more room for
code and conversation.
Keep your Catalyst plugins up to date with bug fixes and new features:
# Update the marketplace to fetch latest from GitHub
claude plugin marketplace update catalyst
# Restart Claude Code to load updated plugins
# (Exit and reopen, or start a new session)When to update:
- 🐛 Bug fixes: Patch versions (e.g., 3.0.0 → 3.0.1) - Fix issues like incorrect CLI syntax
- ✨ New features: Minor versions (e.g., 3.0.0 → 3.1.0) - New commands or capabilities
- 🔄 Breaking changes: Major versions (e.g., 3.0.0 → 4.0.0) - May require configuration updates
Important: A restart is required for plugin updates to take effect. Active sessions use the old version until you restart Claude Code.
Check your versions:
# List installed plugins and their versions
/plugin listNeed help?
- Installation & Configuration Guide - Complete setup, installation, and configuration
- Claude Code Plugin Guide - Official plugin documentation
/research-codebase → /create-plan → /implement-plan → /validate-plan → /create-pr → /merge-pr
With handoffs for context persistence:
/create-handoff → /resume-handoff
Agents proactively monitor context during implementation and will prompt you to create handoffs before running out of context, creating structured handoff documents that add to persistent memory.
Learn More:
- Agentic Workflow Guide - Complete guide showing research, planning, handoff, worktree, implementation, verify, and PR workflows
- Context Engineering - Token efficiency strategies and context management patterns
- Linear Workflow Automation - Linearis integration for ticket → branch → PR → merge lifecycle (Linearis GitHub)
- Parallel Agent Research - Multiple specialized agents research concurrently
- Context Compression - Research compressed into structured summaries
- Focused Planning - Planning agents work with compressed context
- Persistent Memory - Handoffs and thoughts system preserve context across sessions
Uses the HumanLayer thoughts system for shared persistent memory across teams and projects. The research → plan → implement → validate workflow is adapted from HumanLayer's approach.
When possible, uses CLIs instead of MCPs for token efficiency:
- Linear: Linearis CLI (1k tokens) vs Linear MCP (13k tokens) = 13x reduction
- Infrastructure research via CLIs (Railway, Sentry, GitHub)
Large Long-Term Memory and Context
- Thoughts system for persistent memory across projects
- Structured handoff documents for context preservation
- Research artifacts saved and referenceable
- Plan documents that persist implementation context
Token Efficiency
- Parallel agents compress research before synthesis
- CLI-based tools minimize token overhead
- Focused agents for specific tasks
- Context-aware handoff prompts
Secure Configuration
- Template system prevents committing secrets
.gitignoreprotection for sensitive files- No hardcoded credentials
Core Tools:
- Claude Code
- Git
- jq
CLI Integrations (optional but recommended):
linearis- Linear integration (install)gh- GitHub CLIrailway- Railway deploymentssentry-cli- Error monitoringhumanlayer- Thoughts system (install)
MCP Tools (bundled with plugins):
- Context7 & DeepWiki - Built into
catalyst-dev(~3.5k tokens) - PostHog - Built into
catalyst-analytics(~40k tokens when enabled) - Sentry - Built into
catalyst-debugging(~20k tokens when enabled)
Run the prerequisite check:
/check_prerequisitesBuilt on patterns from:
- HumanLayer - Thoughts system for shared persistent memory and research/plan/implement/validate workflow
Personal refinement over hundreds of hours on real projects.
This is my personal workflow workspace, primarily built for my own development style and preferences. That said, I'm happy to:
- Discuss ideas - Open issues with workflow suggestions or improvements
- See your forks - Adapt it to your needs and share what you built
- Fix bugs - If something's broken, let me know
- Learn together - Share your workflow patterns and approaches
Important: I may not accept PRs that change core workflows or add features I don't personally use, since this is the workspace I rely on daily. But I love seeing how others adapt these patterns to their own needs!
Best approach: Fork it, make it yours, and share what you learned. That's how we all get better!
- Full Documentation - Comprehensive guides
- Quick Start - 5-minute setup
- Usage Guide - How to use all features
- Commands - Complete command reference
- Architecture - How it's built
MIT - Use it however you want!
This is my personal workflow shared for learning and inspiration. You're welcome to use it as-is, fork it, or adapt the patterns to your own needs. Just keep in mind that it's optimized for my development style, so your mileage may vary. Some decisions are opinionated based on my preferences, and I may not accept PRs that don't align with how I work. Think of it as a starting point rather than a one-size-fits-all solution—take what works, adapt what doesn't!
Built by Ryan Rozich
Want to chat about workflows, contribute ideas, or share your fork? Open an issue or discussion!