k2-dev

Check system prerequisites and project configuration

Start planning workflow to analyze requirements and create actionable beads tasks

Analyze and update a beads ticket with technical analysis and refined requirements

Start implementation workflow for one or more beads tickets

Create comprehensive test plan and test cases for a beads ticket

Analyze ready tickets and recommend the best next ticket to work on

Use this agent when implementing features, writing code based on plans from beads tasks, performing self-review against quality gates, responding to code review feedback, or executing implementation work. This is the implementation specialist who writes code following approved plans and quality standards. The Engineer completes implementation and pushes changes, then the Technical Lead creates the PR. Examples: <example>Context: /k2:start command has completed setup and is launching the Engineer for implementation. user: "The /k2:start command has set up the worktree for beads-123. Please implement the authentication feature according to the plan." assistant: "I'll use the engineer agent to implement the authentication feature following the plan in beads-123." <commentary>The Engineer is launched by the /k2:start command (which runs Technical Lead logic directly) with a prepared worktree and task context, making this the primary triggering scenario for the engineer agent.</commentary></example> <example>Context: User wants to start implementation work on a beads task that has a plan. user: "Work on beads-456 to implement the user profile feature." assistant: "I'll use the engineer agent to implement the user profile feature according to the plan in beads-456." <commentary>When a user directly requests implementation work on a beads task, the engineer agent should be invoked to handle the implementation and self-review workflow.</commentary></example> <example>Context: Reviewer has provided feedback on a PR and changes are needed. user: "The reviewer left feedback on PR #789. Can you address the comments?" assistant: "I'll use the engineer agent to address the review feedback on PR #789." <commentary>The Engineer handles review feedback iterations (up to 2 cycles) before creating follow-up tickets, making this a clear engineering responsibility.</commentary></example> <example>Context: Planning is complete and implementation is ready to begin. user: "Continue with beads-234 implementation now that the plan is approved." assistant: "I'll use the engineer agent to implement beads-234 following the approved plan." <commentary>After the planning phase is complete, the Engineer takes over to execute the implementation work.</commentary></example>

Use this agent when analyzing requirements to create implementation plans and beads tasks, designing features or changes, planning complex implementations, breaking down user stories into actionable tasks, or when the /k2:planner command is executed. The Planner transforms high-level requirements into structured, hierarchical beads tasks with proper dependencies. Examples: <example>Context: User has executed the /k2:planner command with a feature description. user: "/k2:planner Add user authentication with JWT and refresh tokens" assistant: "I'll use the planner agent to analyze the authentication requirements and create a comprehensive implementation plan with beads tasks." <commentary>The /k2:planner command explicitly triggers the Planner agent to begin the requirements analysis and planning workflow, including codebase exploration, clarification, and task creation.</commentary></example> <example>Context: User wants to plan a new feature before implementation. user: "I want to add a real-time notification system. Can you help me plan this out?" assistant: "I'll use the planner agent to analyze the notification system requirements, explore the codebase, and create a detailed implementation plan." <commentary>When a user requests planning for a feature using keywords like "plan", "design", or "add a feature", the Planner should be invoked to handle requirements analysis and structured planning.</commentary></example> <example>Context: Technical Lead requests planning for a complex feature. user: "We need to refactor the authentication system to support multiple providers. Let's plan this carefully." assistant: "I'll use the planner agent to analyze the current authentication architecture and create a comprehensive refactoring plan with tasks." <commentary>Complex features or architectural changes benefit from the Planner's systematic approach to requirements analysis, codebase exploration, and structured task breakdown.</commentary></example> <example>Context: User provides requirements that need clarification and breakdown. user: "Build a dashboard that shows analytics and has export functionality" assistant: "I'll use the planner agent to clarify the requirements and create a detailed implementation plan with task dependencies." <commentary>When requirements are somewhat vague or need exploration, the Planner uses its full codebase access to understand context and asks clarifying questions to create accurate plans.</commentary></example>

Create pull requests for completed work

Use this agent when performing code reviews on GitHub pull requests, validating code quality against AGENTS.md standards, checking for security vulnerabilities, providing actionable feedback, or approving PRs that meet quality gates. This is a read-only review specialist who validates code but does not make changes. Examples: <example>Context: Engineer has created a PR and needs code review. user: "The Engineer created PR #456 for beads-123. Can you review it?" assistant: "I'll use the reviewer agent to perform a comprehensive code review of PR #456." <commentary>The Reviewer is explicitly assigned a code review task for a PR created by the Engineer, making this the primary triggering scenario for the reviewer agent.</commentary></example> <example>Context: Technical Lead has assigned review work after implementation completes. user: "Review the pull request for beads-789 to ensure it meets our quality standards." assistant: "I'll use the reviewer agent to validate the PR against our quality gates and standards." <commentary>When a Technical Lead or user requests code review with quality validation, the Reviewer agent should be invoked to perform thorough review against project standards.</commentary></example> <example>Context: PR is ready for validation and feedback. user: "PR #234 is ready for review. Please check security and best practices." assistant: "I'll use the reviewer agent to review PR #234 with focus on security and best practices." <commentary>The Reviewer handles security validation, best practices checking, and comprehensive code review, making this a clear reviewer responsibility.</commentary></example> <example>Context: Engineer has addressed feedback and needs re-review (iteration 1 or 2). user: "I've addressed the review feedback on PR #567. Can you take another look?" assistant: "I'll use the reviewer agent to re-review PR #567 and verify the feedback has been addressed." <commentary>The Reviewer performs iterative reviews (up to 2 iterations) to validate that feedback has been properly addressed, continuing until approval or follow-up tickets are needed.</commentary></example>

Use this agent for technical architecture analysis, system design, architectural review, code analysis, technical debt assessment, and ticket refinement with engineering depth. Examples: <example>Context: User needs architecture review for a new feature. user: "Review the proposed auth system design" assistant: "I'll use the technical-lead agent to analyze the architecture and provide design feedback."</example> <example>Context: User wants to understand codebase architecture. user: "How is the data layer structured?" assistant: "I'll use the technical-lead agent to explore and explain the system architecture."</example> <example>Context: User needs ticket refined with technical details. user: "Refine beads-123 with implementation approach" assistant: "I'll use the technical-lead agent to analyze and update the ticket with technical analysis."</example> <example>Context: User wants code reviewed for architectural soundness. user: "Review this PR for design patterns" assistant: "I'll use the technical-lead agent to assess architectural quality and design adherence."</example>

Use this agent when creating comprehensive test plans, defining test cases and coverage strategies, validating test completeness, analyzing ticket requirements for testing needs, or documenting test strategies in beads tasks. This is the test planning and validation specialist who ensures thorough test coverage without necessarily implementing tests. Examples: <example>Context: User has executed the /k2:test command with a ticket ID. user: "/k2:test beads-123" assistant: "I'll use the tester agent to create a comprehensive test plan for beads-123." <commentary>The /k2:test command explicitly triggers the Tester agent to analyze the ticket and create a detailed test plan with test strategy, specific test cases, and coverage analysis.</commentary></example> <example>Context: Technical Lead needs test validation for a completed implementation. user: "Can you create a test plan for beads-456 to ensure we have comprehensive coverage?" assistant: "I'll use the tester agent to analyze beads-456 and create a comprehensive test plan." <commentary>When comprehensive test planning is requested, the Tester agent should be invoked to create test strategy, define test cases, and document coverage requirements.</commentary></example> <example>Context: Engineer has completed implementation and needs test guidance. user: "The implementation for beads-789 is done. What tests should we write?" assistant: "I'll use the tester agent to analyze the implementation and create a test plan with specific test cases." <commentary>The Tester provides test guidance by creating detailed test plans that the Engineer can use to implement tests, ensuring comprehensive coverage.</commentary></example> <example>Context: User wants to validate test coverage before review. user: "Validate the test coverage for beads-234 and create any missing test cases." assistant: "I'll use the tester agent to review the existing tests and identify coverage gaps." <commentary>The Tester validates test completeness by analyzing existing tests against requirements and identifying gaps in coverage.</commentary></example>

This skill should be used when the user asks to "work with beads tasks", "create a beads ticket", "update beads status", "read task comments", "manage dependencies", "sync beads", "use bd commands", or needs guidance on beads task management workflows. Provides comprehensive beads CLI usage and workflow patterns.

This skill should be used when the user asks to "review code", "perform code review", "check code quality", "review PR", "provide code feedback", or needs guidance on code review best practices and standards in k2-dev workflows.

This skill should be used when the user asks to "create a worktree", "manage git worktrees", "work on multiple branches simultaneously", "isolate task work", "use bd worktree", or needs guidance on git worktree patterns for task isolation in k2-dev workflows.

This skill should be used when the user needs to plan features, break down requirements, create implementation tasks, or design software architecture. Use this skill for comprehensive requirements analysis, technical planning, and creating structured task hierarchies with dependencies. The skill executes in the main conversation context.

Quick PR creation reference

This skill should be used when the user asks to "check quality gates", "validate against standards", "read AGENTS.md", "enforce project patterns", "follow constitution.md", "validate code quality", or needs guidance on quality standards enforcement in k2-dev workflows.

This skill should be used when you need to generate a comprehensive status report for a beads ticket, including summary, progress, dependencies, PR status, and next steps. Use this after workflow completion or when the user requests a ticket status report.

This skill should be used when the user asks to "create a test plan", "write test cases", "plan testing strategy", "define test coverage", "create test scenarios", or needs guidance on comprehensive test planning in k2-dev workflows.

This skill should be used when the user needs to create comprehensive test plans, define test cases and coverage strategies, validate test completeness, analyze ticket requirements for testing needs, or document test strategies. The skill executes in the main conversation context and provides thorough test planning guidance without implementing tests.