cc-track

Quickly add an item to the backlog without disrupting current work

Code review a pull request

Complete the current active task (Phase 2 of task completion workflow)

Update the configuration file at `.cc-track/track.config.json` based on the user's request.

---

Use this agent when you need to research technical topics, library documentation, best practices, or implementation approaches. This agent synthesizes findings from documentation, web sources, and codebases into actionable recommendations. <example> Context: Need to understand how to implement a feature using a library. user: "How should we handle authentication in Next.js App Router?" assistant: "I'll use the researcher agent to investigate authentication patterns for Next.js App Router." <Task tool invocation to launch researcher agent> </example> <example> Context: Comparing different approaches to solve a problem. user: "What's the best way to implement rate limiting in Bun?" assistant: "I'll use the researcher agent to compare rate limiting options for Bun." <Task tool invocation to launch researcher agent> </example>

Use this agent to create minimal file stubs with exported interfaces, types, and function signatures so that imports resolve before tests are written. This agent is part of the TDD orchestration system and runs as the first step in each phase. <example> Context: Starting a new phase that needs a new module. orchestrator: "Phase 2 requires a new validation module. Create stubs first." <Task tool invocation to launch stub-writer agent for Phase 2> </example> <example> Context: Tests are failing due to missing exports. orchestrator: "Test writer reports import errors. Stub writer needs to add missing exports." <Task tool invocation to launch stub-writer agent to fix exports> </example>

Use this agent when you need to generate comprehensive test suites for code that lacks tests or needs better coverage. This agent follows TDD principles with proper mocking and behavior verification. In phase-based orchestration, this agent is Step 2 of 4 in each phase: 1. Stub Writer → Creates exports so imports resolve 2. **Test Writer (this agent)** → Writes failing tests, runs them, reports output 3. Implementer → Makes tests pass 4. Validator → Verifies requirements met <example> Context: Phase-based TDD orchestration. orchestrator: "Phase 3 stubs are ready. Write tests for email validation." <Task tool invocation to launch test-generation agent for Phase 3> </example> <example> Context: New code has been written without tests. user: "We need tests for the authentication module" assistant: "I'll use the test-generation agent to create comprehensive tests for the authentication module." <Task tool invocation to launch test-generation agent> </example> <example> Context: Expanding test coverage for undertested code. user: "The validation utils have poor test coverage" assistant: "I'll use the test-generation agent to expand test coverage for the validation utilities." <Task tool invocation to launch test-generation agent> </example>

Use this agent to implement production code that makes failing tests pass. This agent is part of the TDD orchestration system and runs as the third step in each phase. In phase-based orchestration, this agent is Step 3 of 4 in each phase: 1. Stub Writer → Creates exports so imports resolve 2. Test Writer → Writes failing tests 3. **Implementer (this agent)** → Makes tests pass, runs them, reports output 4. Validator → Verifies requirements met <example> Context: Phase-based TDD orchestration. orchestrator: "Phase 3 tests are failing as expected. Implement email validation to make them pass." <Task tool invocation to launch implementer agent for Phase 3> </example> <example> Context: Tests exist but implementation is incomplete. orchestrator: "The stub for parseConfig throws 'Not implemented'. Write the actual logic." <Task tool invocation to launch implementer agent> </example>

Use this agent to verify that a phase accomplished its stated requirements. This agent has read-only access and performs verification, not implementation. It is the final step in each TDD phase. In phase-based orchestration, this agent is Step 4 of 4 in each phase: 1. Stub Writer → Creates exports so imports resolve 2. Test Writer → Writes failing tests 3. Implementer → Makes tests pass 4. **Validator (this agent)** → Verifies requirements met, reports pass/fail <example> Context: Phase-based TDD orchestration. orchestrator: "Phase 3 implementation complete. Validate that email validation meets requirements." <Task tool invocation to launch validator agent for Phase 3> </example> <example> Context: Verifying a completed phase before moving on. orchestrator: "Tests pass for user authentication. Verify the phase requirements are satisfied." <Task tool invocation to launch validator agent> </example>

Provides paths to cc-track utility scripts for validation, task completion, and git operations. Use when a cc-track command needs to run a script.

5 hooks across 5 events