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

Sync Claude Code config between ~/.claude/ and ~/cc-setup repo — backup, restore, diff, install

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>

Manage MCP (Model Context Protocol) server integrations - discover tools/prompts/resources, analyze relevance for tasks, and execute MCP capabilities. Use when need to work with MCP servers, discover available MCP tools, filter MCP capabilities for specific tasks, execute MCP tools programmatically, or implement MCP client functionality. Keeps main context clean by handling MCP discovery in subagent context.

Use this agent when you need to validate a plan before executing it. Checks for testable acceptance criteria, realistic scope, a functional validation phase, and the absence of mock/test/stub steps. <example>Context: A planner agent has just produced a plan file and execution is about to begin. user: "The plan is ready at plans/260320-1200-auth-flow/plan.md" assistant: "I'll run the plan-checker agent against that plan before we start executing to catch any gaps in acceptance criteria or missing validation phases." <commentary>Plans should be validated before execution begins. Use the plan-checker to confirm the plan is sound so issues are caught before code is written, not after.</commentary></example> <example>Context: A multi-phase plan has been drafted and a phase gate is about to be crossed. user: "Phase 1 plan is complete, moving to execution." assistant: "Let me use the plan-checker agent to review the phase 1 plan for realistic scope and functional validation checkpoints before we proceed." <commentary>Gate transitions are the right moment to validate plan quality. Use the plan-checker agent to catch under-specified phases before they cause rework.</commentary></example> <example>Context: A user has written a plan that includes unit test steps. user: "Here is my plan: step 3 is to write unit tests for the service layer." assistant: "I'll invoke the plan-checker agent — the functional validation mandate prohibits test-writing steps, and this plan needs to be corrected before execution." <commentary>Plans must not include mock, stub, or test-writing steps per project rules. Use the plan-checker agent to flag violations before they are executed.</commentary></example>

Use this agent when you need comprehensive project oversight and coordination. Examples: <example>Context: User has completed a major feature implementation and needs to track progress against the implementation plan. user: 'I just finished implementing the WebSocket terminal communication feature. Can you check our progress and update the plan?' assistant: 'I'll use the project-manager agent to analyze the implementation against our plan, track progress, and provide a comprehensive status report.' <commentary>Since the user needs project oversight and progress tracking against implementation plans, use the project-manager agent to analyze completeness and update plans.</commentary></example> <example>Context: Multiple agents have completed various tasks and the user needs a consolidated view of project status. user: 'The backend-developer and tester agents have finished their work. What's our overall project status?' assistant: 'Let me use the project-manager agent to collect all implementation reports, analyze task completeness, and provide a detailed summary of achievements and next steps.' <commentary>Since multiple agents have completed work and comprehensive project analysis is needed, use the project-manager agent to consolidate reports and track progress.</commentary></example>

Use this agent when you need to conduct comprehensive research on software development topics, including investigating new technologies, finding documentation, exploring best practices, or gathering information about plugins, packages, and open source projects. This agent excels at synthesizing information from multiple sources including searches, website content, YouTube videos, and technical documentation to produce detailed research reports. <example>Context: The user needs to research a new technology stack for their project. user: "I need to understand the latest developments in React Server Components and best practices for implementation" assistant: "I'll use the researcher agent to conduct comprehensive research on React Server Components, including latest updates, best practices, and implementation guides." <commentary>Since the user needs in-depth research on a technical topic, use the Task tool to launch the researcher agent to gather information from multiple sources and create a detailed report.</commentary></example> <example>Context: The user wants to find the best authentication libraries for their Flutter app. user: "Research the top authentication solutions for Flutter apps with biometric support" assistant: "Let me deploy the researcher agent to investigate authentication libraries for Flutter with biometric capabilities." <commentary>The user needs research on specific technical requirements, so use the researcher agent to search for relevant packages, documentation, and implementation examples.</commentary></example> <example>Context: The user needs to understand security best practices for API development. user: "What are the current best practices for securing REST APIs in 2024?" assistant: "I'll engage the researcher agent to research current API security best practices and compile a comprehensive report." <commentary>This requires thorough research on security practices, so use the researcher agent to gather information from authoritative sources and create a detailed summary.</commentary></example>

Use this agent when you need to validate code quality through testing, including running unit and integration tests, analyzing test coverage, validating error handling, checking performance requirements, or verifying build processes. This agent should be called after implementing new features or making significant code changes to ensure everything works as expected. Examples:\n\n<example>\nContext: The user has just finished implementing a new API endpoint and wants to ensure it works correctly.\nuser: "I've implemented the new user authentication endpoint"\nassistant: "Great! Now let me use the tester agent to run the test suite and validate the implementation"\n<commentary>\nSince new code has been written, use the Task tool to launch the tester agent to run tests and ensure everything works properly.\n</commentary>\n</example>\n\n<example>\nContext: The user wants to check test coverage after adding new features.\nuser: "Can you check if our test coverage is still above 80%?"\nassistant: "I'll use the tester agent to analyze the current test coverage and provide a detailed report"\n<commentary>\nThe user is asking about test coverage metrics, so use the tester agent to run coverage analysis.\n</commentary>\n</example>\n\n<example>\nContext: After fixing a bug, ensuring the fix doesn't break existing functionality.\nuser: "I've fixed the database connection issue in the auth module"\nassistant: "Let me use the tester agent to run the test suite and ensure the fix doesn't introduce any regressions"\n<commentary>\nAfter bug fixes, use the tester agent to validate that existing tests still pass.\n</commentary>\n</example>

Use this agent when the user needs UI/UX design work including interface designs, wireframes, design systems, user research, responsive layouts, animations, or design documentation. Examples:\n\n<example>\nContext: User wants to create a new landing page design\nuser: "I need a modern landing page design for our SaaS product with a hero section, features, and pricing"\nassistant: "I'll use the Task tool to launch the ui-ux-designer agent to create a comprehensive landing page design with wireframes and implementation."\n<commentary>The user is requesting UI/UX design work, so delegate to the ui-ux-designer agent to handle the complete design process including research, wireframing, and implementation.</commentary>\n</example>\n\n<example>\nContext: User has implemented a new feature and wants design review\nuser: "I've added a new dashboard widget, can you review the design?"\nassistant: "Let me first capture the current UI and then use the ui-ux-designer agent to analyze and provide design recommendations."\n<commentary>Use screenshot tool to capture current state, then delegate to ui-ux-designer for expert design analysis and suggestions.</commentary>\n</example>\n\n<example>\nContext: User mentions design inconsistencies\nuser: "The buttons across different pages look inconsistent"\nassistant: "I'll use the ui-ux-designer agent to audit the design system and create consistent button components."\n<commentary>Design system work requires the ui-ux-designer agent to analyze, document, and implement consistent design patterns.</commentary>\n</example>\n\n<example>\nContext: Proactive design optimization opportunity\nuser: "Here's the new signup form I just built"\nassistant: "Great! Let me use the ui-ux-designer agent to review the form design for accessibility, user experience, and mobile responsiveness."\n<commentary>Even without explicit request, proactively use ui-ux-designer to ensure design quality and best practices.</commentary>\n</example>

Use this agent when you need to verify that a task has been genuinely completed with fresh, concrete evidence — not just claimed complete. Runs builds, tests, and checks. Rejects vague or assumed success. <example>Context: An executor agent has just finished implementing a feature and claims it is done. user: "The pagination feature has been implemented." assistant: "I'll use the verifier agent to confirm the implementation with fresh build output and functional evidence before marking this complete." <commentary>Completion claims require evidence. Use the verifier agent to run the build, check for errors, and confirm the feature works — not just that code was written.</commentary></example> <example>Context: A gate condition must be passed before moving to the next phase. user: "All phase 1 tasks are complete, ready to proceed." assistant: "Let me launch the verifier agent to validate each phase 1 task with concrete evidence before marking the gate as passed." <commentary>Phase gates must not be waved through. Use the verifier agent to independently confirm each exit criterion is satisfied.</commentary></example> <example>Context: A build-fixer claims all type errors are resolved. user: "Type errors have been fixed." assistant: "I'll deploy the verifier agent to run tsc and confirm zero errors before accepting the fix." <commentary>Type-error fixes must be confirmed with fresh compiler output, not assumed. Use the verifier agent to run the real check.</commentary></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/.

Multi-perspective review using specialized judges with debate and consensus building. Triggers on "critique", "review", "multi-perspective review", "challenge this".

Execute complex tasks through sequential sub-agent orchestration, passing results forward at each step with model-routed agents and per-step verification.

End-to-end functional validation through real user interfaces. Triggers on "e2e", "end to end", "validate end to end", "browser test". Never write test files or mocks. Validate via browser (Playwright), CLI terminal, or API (curl).

Enforces end-user perspective validation through real system execution. Triggers on "validate", "functional test", "prove it works", "evidence". Never write mocks or test files. Validate via simulator, browser, CLI, or cURL with PASS/FAIL verdict.

Enforces evidence-based validation before marking any task, gate, or milestone complete. Triggers on "gate", "validate completion", "evidence check", "mark complete". Rejects vague claims. Requires specific file paths, command output, or line numbers as proof.

Curates insights from reflections into CLAUDE.md as durable, actionable guidance. Triggers on "memorize", "save learning", "remember this pattern".

Break complex tasks into discrete subtasks and coordinate specialized agents with parallel dispatch and progress tracking.

Create a structured implementation plan with risk assessment, phased steps, and validation gates. Saves plan to ./plans/ directory. Waits for user confirmation before any implementation begins.

Self-refinement framework for iterative quality improvement. Triggers on "reflect", "review my work", "check quality", "self-review".

Multi-source research on technical topics. Produces a structured findings summary with sources and recommendations. Supports three subtypes: technical (how to implement), options (compare alternatives), feasibility (can we do this).

Reviews recently changed code for simplification opportunities and applies fixes directly. Triggers on "simplify", "clean up code", "reduce complexity", "refactor".

Audit all skills and commands across installed plugins for quality. Supports Quick Scan (changed skills only) and Full Stocktake modes with per-skill pass/fail verdicts.

Analyze the current session and produce a handoff document so a fresh Claude context can resume exactly where this left off.