cc-setup

Run health check on Claude Code configuration — hooks, plugins, MCP servers, rules, agents

Deploy cc-setup configuration to this machine — rules, hooks, CLAUDE.md, settings, MCP configs, and register plugin

Invoke the plan skill to create a structured implementation plan for a task

Invoke the reflect skill to review and assess the quality of recent work in this session

Invoke the research skill to investigate a technical topic or question

Use this agent when you need to brainstorm software solutions, evaluate architectural approaches, or debate technical decisions before implementation. Examples: - <example> Context: User wants to add a new feature to their application user: "I want to add real-time notifications to my web app" assistant: "Let me use the brainstormer agent to explore the best approaches for implementing real-time notifications" <commentary> The user needs architectural guidance for a new feature, so use the brainstormer to evaluate options like WebSockets, Server-Sent Events, or push notifications. </commentary> </example> - <example> Context: User is considering a major refactoring decision user: "Should I migrate from REST to GraphQL for my API?" assistant: "I'll engage the brainstormer agent to analyze this architectural decision" <commentary> This requires evaluating trade-offs, considering existing codebase, and debating pros/cons - perfect for the brainstormer. </commentary> </example> - <example> Context: User has a complex technical problem to solve user: "I'm struggling with how to handle file uploads that can be several GB in size" assistant: "Let me use the brainstormer agent to explore efficient approaches for large file handling" <commentary> This requires researching best practices, considering UX/DX implications, and evaluating multiple technical approaches. </commentary> </example>

Use this agent when you need to manage technical documentation, establish implementation standards, analyze and update existing documentation based on code changes, write or update Product Development Requirements (PDRs), organize documentation for developer productivity, or produce documentation summary reports. This includes tasks like reviewing documentation structure, ensuring docs are up-to-date with codebase changes, creating new documentation for features, and maintaining consistency across all technical documentation.

Execute implementation phases from parallel plans. Handles backend (Node.js, APIs, databases), frontend (React, TypeScript), and infrastructure tasks. Designed for parallel execution with strict file ownership boundaries. Use when implementing a specific phase from `/plan --parallel` output.

Stage, commit, and push code changes with conventional commits. Use when user says "commit", "push", or finishes a feature/fix.

Use this agent when:\n- A test suite fails repeatedly despite multiple fix attempts\n- A critical bug is discovered in production or staging\n- An implementation approach proves fundamentally flawed and requires complete redesign\n- External dependencies (APIs, services, libraries) cause blocking issues\n- Performance bottlenecks are discovered that significantly impact user experience\n- Security vulnerabilities are identified\n- Database migrations fail or cause data integrity issues\n- CI/CD pipelines break unexpectedly\n- Integration conflicts arise between major system components\n- Technical debt reaches a critical threshold requiring immediate attention\n- A feature implementation takes significantly longer than estimated\n- Architectural decisions prove problematic in practice\n\nExamples:\n<example>\nContext: After implementing a new payment webhook handler, tests are failing with intermittent database connection errors.\nuser: "The Sepay webhook tests keep failing with connection timeouts. I've tried increasing the pool size and timeout values but it's still happening randomly."\nassistant: "This sounds like a significant technical difficulty that should be documented. Let me use the journal-writer agent to capture this issue with full context and emotional honesty."\n<uses Task tool to launch journal-writer agent>\n</example>\n\n<example>\nContext: A critical security vulnerability was discovered in the GitHub access management system.\nuser: "We just realized that the GitHub invitation system doesn't properly validate user permissions before granting repository access. This could allow unauthorized users to access private repos."\nassistant: "This is a critical security issue that needs immediate documentation. I'm going to use the journal-writer agent to record this vulnerability, the emotional impact, and the urgency of the situation."\n<uses Task tool to launch journal-writer agent>\n</example>\n\n<example>\nContext: A major refactoring effort failed and needs to be rolled back.\nuser: "The database schema migration we planned completely broke the order processing system. We need to roll back and rethink our approach."\nassistant: "This is a significant setback that should be documented honestly. Let me use the journal-writer agent to capture what went wrong, why it failed, and the emotional toll of this failure."\n<uses Task tool to launch journal-writer agent>\n</example>

Verify Claude Code setup — hooks, plugins, MCP servers, rules, agents

[FUTURE] Build/refresh semantic code index with Zoekt via code-index-mcp

Sync Claude Code config between ~/.claude/ and ~/cc-setup repo

Create optimized prompts for Claude-to-Claude pipelines with research, planning, and execution stages. Use when building prompts that produce outputs for other prompts to consume, or when running multi-stage workflows (research -> plan -> implement).

Create a hierarchical multi-phase project plan optimized for solo agentic development. Supports brief, roadmap, and phase-plan types. Each task is scoped for a single agent session. Saves to ./plans/YYMMDD-HHMM-slug/.