ccflow

Strict senior developer that reviews PRs for quality, conventions, bugs, and test coverage. Use after implementation for final review before PR. <example> Context: The user has completed implementing a feature and all tests pass. user: "I've finished implementing the user authentication system as outlined in step 3 of our plan" assistant: "Great work! Now let me use the code-reviewer agent to review the implementation against our plan and coding standards" <commentary>A major implementation step is complete and needs quality review before PR creation.</commentary> </example> <example> Context: The implementer agent has finished the green phase and refactoring is done. user: "Tests pass and refactoring is complete. Ready for review." assistant: "I'll delegate to the code-reviewer agent to check for bugs, convention violations, and test coverage gaps" <commentary>The implementation pipeline has reached the code review phase (Phase 7).</commentary> </example>

Analyzes codebase for duplicated code patterns, copy-paste code, and extraction opportunities. Use when checking for repeated logic across files. <example> Context: User wants to find duplicated code across their project. user: "Analyze these files for code duplication" assistant: "I'll use the duplication-analyzer agent to find repeated patterns and suggest extractions" <commentary>Duplication analysis examines code blocks, similar functions, and copy-paste patterns to suggest consolidation.</commentary> </example> <example> Context: A refactoring analysis is running and needs duplication detection. user: "Check the service layer for repeated patterns" assistant: "I'll delegate to the duplication-analyzer agent to compare code blocks across service files and identify extraction opportunities" <commentary>Targeted duplication analysis on a specific layer or module helps find consolidation opportunities.</commentary> </example>

Senior developer that implements features using TDD — writes tests first, then implementation. Use for writing code, tests, and making builds pass. <example> Context: The plan has been approved and it's time to write tests. user: "Plan is approved. Start with the tests for the new payment processing endpoint." assistant: "I'll delegate to the implementer agent to write failing tests first (red phase), then implement the code to make them pass (green phase)" <commentary>TDD workflow starts with the implementer writing tests that encode the requirements.</commentary> </example> <example> Context: Tests have been written and are failing as expected (red phase complete). user: "Tests are written and failing. Now implement the feature." assistant: "I'll delegate to the implementer agent to make the failing tests pass with the simplest correct implementation" <commentary>Moving from red to green phase — implementer writes production code.</commentary> </example> <example> Context: Security review found a critical issue that needs fixing. user: "The security reviewer found an SQL injection vulnerability in the search endpoint" assistant: "I'll delegate to the implementer agent to fix the SQL injection issue, then re-run tests to verify the fix" <commentary>Implementer handles fixes identified by review agents.</commentary> </example>

Reviews implementation sessions and extracts mistakes into lessons-learned for future prevention. Use after implementation to capture learnings. <example> Context: Implementation is complete and the PR has been created. user: "PR is up. Let's capture any lessons from this session." assistant: "I'll delegate to the lessons-collector agent to review the session for self-corrections and record them in lessons-learned.md" <commentary>End of implementation pipeline — time to extract learnings from any mistakes made during the session.</commentary> </example> <example> Context: A build failed multiple times before the root cause was found. user: "That was a tricky debugging session. We should record what went wrong." assistant: "I'll use the lessons-collector agent to document the incorrect assumptions and the root cause for future prevention" <commentary>Non-obvious failures and self-corrections are exactly what lessons-collector captures.</commentary> </example>

Senior architect that analyzes tickets and produces implementation plans. Use when planning feature work, analyzing ticket requirements, or breaking down complex tasks. <example> Context: User wants to implement a new feature from a ticket. user: "I need to implement ticket #42 — add user profile editing" assistant: "I'll delegate to the planner agent to analyze the ticket, explore the codebase, ask clarifying questions, and produce an implementation plan" <commentary>New feature work starts with the planner analyzing requirements and producing a plan.</commentary> </example> <example> Context: A complex task needs to be broken down before implementation. user: "We need to migrate the database from PostgreSQL to MySQL. Can you plan this out?" assistant: "I'll use the planner agent to analyze the codebase, identify all affected files and dependencies, and produce an implementation plan" <commentary>Complex tasks need architectural analysis and breakdown before any code is written.</commentary> </example>

Address PR review comments — fetch, evaluate, fix, reply, push, re-request review

Canonical procedure for discovering, downloading, and loading ticket attachments

Configure the ccflow workflow plugin for this project

Interactive design reasoning and .pen file creation using Pencil

Full implementation pipeline — plan, test, implement, review, PR

5 hooks across 4 events