product-team

Adds tests from a specific test file into our ongoing test plan

You will make extensive use of the following sub-agents:

Fully create a spec using sub agents, including comprehensive review and revision

You will make extensive use of the following sub-agents:

Write a spec and plan using sub agents

Your task is to check the code implementation of a plan ($1) against the plan requirements and code-rules.md. If you were given additional instructions ($2), please pay attention to them. Output a REVIEW.md of your findings and recommendations, and then offer to implement any of them that you think are most pressing (if any).

You have been given a plan document to check ($1). Your task is to fully read and understand the plan document, validate it against plan-rules.md, and suggest improvements if needed.

Validate a specification document against spec-rules.md

Create an issue based on instructions, optionally creating a spec and plan

You have been given a plan document that has been implemented ($1). Your task is to run final cleanup commands and propose a git commit message

Run Integration tests from the test plan via Playwright hitting the live UI

You have been given a plan document to implement ($1). Your task is to fully read and understand the plan document, and then write the code to implement it. If you were given additional instructions ($2), please pay attention to them.

Create a plan to implement a certain specification

Create a specification document for a task

Use this agent when you need to create new agents, update existing agents, audit agent quality, or propose improvements to the agent system. This agent is the authority on agent structure, conventions, and quality standards.\n\n<example>\nContext: User wants to create a new agent for a specific purpose.\nuser: "I need an agent that can help with database migrations and schema design"\nassistant: "I'll use the Task tool to launch the agent-maker agent to create a specialized database agent."\n<Task tool call to agent-maker agent>\n</example>\n\n<example>\nContext: User wants to update an existing agent's capabilities.\nuser: "The plan-writer agent should also check for security vulnerabilities in the proposed architecture"\nassistant: "I'll use the agent-maker agent to update the plan-writer with security audit capabilities."\n<Task tool call to agent-maker agent>\n</example>\n\n<example>\nContext: User wants to audit the quality of agents.\nuser: "Can you review all our agents and make sure they're following best practices?"\nassistant: "I'll launch the agent-maker agent to perform a comprehensive audit of all agents."\n<Task tool call to agent-maker agent>\n</example>\n\n<example>\nContext: User wants to propose new SlashCommands or processes.\nuser: "I think we need a standard process for handling database migrations"\nassistant: "Let me use the agent-maker agent to analyze our needs and propose a new process or SlashCommand."\n<Task tool call to agent-maker agent>\n</example>\n\nDo NOT use this agent for:\n- Simple code changes\n- General questions about the codebase\n- Tasks unrelated to agent creation or management

Use this agent for visual QA testing of the web application on desktop browsers. This agent verifies implemented features work correctly, debugs UI issues, and performs smoke tests. Use this agent after completing development tasks to validate changes work as expected in the live application.

Use this agent to validate implemented code against code-rules.md and the implementation plan (PLAN.md). This agent provides fast, focused feedback on code quality, pattern compliance, and completeness.

Use this agent when you have a completed PLAN.md document that needs to be implemented in code. This agent should be delegated to for ALL coding tasks to preserve context on the main thread.

Use this agent when you need to update, review, or get guidance on documentation in the `.claude/docs/` directory. This agent maintains both technical documentation (for LLMs/engineers) and user documentation (for marketing/product content). The Documentation Manager is context-intensive and reviews existing docs thoroughly.

Use this agent when the user needs high-level project coordination, task delegation, or management of the development workflow. This agent orchestrates work across multiple specialized agents and manages the project lifecycle from planning through execution.\n\n**Examples of when to use this agent:**\n\n<example>\nContext: User wants to initiate planning for tasks marked as ready in Notion.\nuser: "Can you check Notion for any tasks that are ready for planning and get them started?"\nassistant: "I'll use the Task tool to launch the engineering-manager agent to check Notion for 'Ready for Plan' tasks and initiate the planning process."\n<commentary>\nThe engineering-manager agent will query Notion for tasks with "Ready for Plan" status, create SPEC.md files in ./tasks/**/ directories, and spawn plan-writer subagents for each one.\n</commentary>\n</example>\n\n<example>\nContext: User has completed a feature and wants comprehensive testing.\nuser: "I just finished implementing the project deletion feature. Can you test it?"\nassistant: "I'll use the Task tool to launch the engineering-manager agent to coordinate testing of the project deletion feature."\n<commentary>\nThe engineering-manager will delegate to the browser-tester agent to perform visual QA on the feature, ensuring the redirect behavior and side nav refresh work correctly.\n</commentary>\n</example>\n\n<example>\nContext: User wants to create a new task in Notion for a bug they discovered.\nuser: "I found a bug where the side nav doesn't refresh after deleting a project. Can you create a task for this?"\nassistant: "I'll use the Task tool to launch the engineering-manager agent to create a new task in Notion for this bug."\n<commentary>\nThe engineering-manager will use the Notion MCP tool to create a new project with appropriate properties (title, status, priority, description) based on the bug details provided.\n</commentary>\n</example>\n\n<example>\nContext: User wants to turn a SPEC.md into a detailed implementation plan.\nuser: "I have a SPEC.md file in ./tasks/project-deletion-fix/. Can you create a plan for it?"\nassistant: "I'll use the Task tool to launch the engineering-manager agent to create an implementation plan from the SPEC.md file."\n<commentary>\nThe engineering-manager will spawn a plan-writer subagent to convert the SPEC.md into a detailed PLAN.md document with implementation steps.\n</commentary>\n</example>\n\n<example>\nContext: Proactive check - the manager notices unplanned tasks.\nassistant: "I notice there are several tasks in Notion marked as 'Ready for Plan'. Let me use the Task tool to launch the engineering-manager agent to initiate planning for these tasks."\n<commentary>\nThe engineering-manager proactively identifies work that needs planning and initiates the process without being explicitly asked.\n</commentary>\n</example>

Use this agent to validate implementation plans (PLAN.md) against plan-rules.md. This agent provides fast, focused feedback on plan quality, completeness, feasibility, and adherence to standards.\n\n**Examples:**\n\n<example> Context: User has created a PLAN.md and wants validation before implementation. user: "Can you check if my plan at ./tasks/pdf-export/PLAN.md is ready for implementation?" assistant: "I'll use the plan-checker agent to validate your plan against plan-rules.md." <uses Task tool to launch plan-checker agent with plan file path> </example>\n\n<example> Context: Plan-writer agent requests plan validation. assistant (as plan-writer): "Let me validate this plan before finalizing it." <uses Task tool to launch plan-checker agent> </example>\n\n<example> Context: User wants to ensure plan follows standards. user: "Does the plan in ./tasks/realtime-collab/PLAN.md follow all our planning rules?" assistant: "Let me use the plan-checker agent to verify compliance with plan-rules.md." <uses Task tool to launch plan-checker agent> </example>

Use this agent when you have a specification (SPEC.md) that needs to be transformed into a detailed implementation plan (PLAN.md). This agent creates comprehensive, actionable plans that can be executed by the code-writer agent. Examples:\n\n<example> Context: User provides a new feature specification for the application. user: "I need to add a feature that allows users to export their achievements as a PDF resume" assistant: "I'm going to use the plan-writer agent to create a detailed implementation plan for this PDF export feature." <Task tool call to plan-writer agent> </example>\n\n<example> Context: User describes a complex technical requirement. user: "We need to implement real-time collaboration on achievement documents, similar to Google Docs" assistant: "This is a complex specification that requires careful planning. Let me use the plan-writer agent to break this down into a comprehensive implementation plan." <Task tool call to plan-writer agent> </example>\n\n<example> Context: User asks for help implementing a feature from the TODO.md or feature documentation. user: "Can you help me implement the achievement tagging system mentioned in the roadmap?" assistant: "I'll use the plan-writer agent to create a detailed plan for implementing the achievement tagging system." <Task tool call to plan-writer agent> </example>\n\nDo NOT use this agent for: - Simple bug fixes or minor code changes - Questions about existing code - General discussions about the codebase - Code reviews

Use this agent when you need to monitor, analyze, or optimize the processes, workflows, and team documentation used by the development team. This agent has authority to modify team definitions, processes, SlashCommands, and agent specifications.\n\n<example>\nContext: An agent submits an after-action report indicating a recurring issue with the planning workflow.\nuser: "The plan-writer agent keeps forgetting to check for existing similar features before planning new ones"\nassistant: "I'll use the Task tool to launch the process-manager agent to review this after-action report and update the plan-writer's workflow."\n<Task tool call to process-manager agent>\n</example>\n\n<example>\nContext: User wants to improve how agents coordinate with each other.\nuser: "I've noticed our agents aren't communicating well about task handoffs. Can you improve the delegation patterns?"\nassistant: "I'll use the process-manager agent to analyze the delegation patterns and update team.md and relevant agent definitions."\n<Task tool call to process-manager agent>\n</example>\n\n<example>\nContext: User wants to verify agent definitions match team documentation.\nuser: "Can you check if all our agent files are consistent with what's described in team.md?"\nassistant: "I'll launch the process-manager agent to audit agent-team alignment and update any inconsistencies."\n<Task tool call to process-manager agent>\n</example>\n\n<example>\nContext: A SlashCommand workflow could be improved based on usage patterns.\nuser: "The /write-code command is taking too long because it's not checking for similar implementations first"\nassistant: "Let me use the process-manager agent to analyze the /write-code command and propose improvements."\n<Task tool call to process-manager agent>\n</example>\n\nDo NOT use this agent for:\n- Actual feature implementation (use code-writer or engineer agents)\n- Creating new agents from scratch (use agent-maker agent)\n- Testing the application (use browser-tester agent)\n- General coding tasks

Use this agent to validate specification documents (SPEC.md) against spec-rules.md. This agent provides fast, focused feedback on specification quality, completeness, and adherence to standards.\n\n**Examples:**\n\n<example> Context: User has created a SPEC.md and wants validation before planning. user: "Can you check if my specification at ./tasks/pdf-export/SPEC.md is complete?" assistant: "I'll use the spec-checker agent to validate your specification against spec-rules.md." <uses Task tool to launch spec-checker agent with spec file path> </example>\n\n<example> Context: Plan-writer agent requests spec validation. assistant (as plan-writer): "Before creating the plan, let me validate the specification." <uses Task tool to launch spec-checker agent> </example>\n\n<example> Context: User wants to ensure spec follows standards. user: "Does the spec in ./tasks/realtime-collab/SPEC.md follow all our rules?" assistant: "Let me use the spec-checker agent to verify compliance with spec-rules.md." <uses Task tool to launch spec-checker agent> </example>

Use this agent to create specification documents (SPEC.md) from user requirements, feature requests, or high-level descriptions. This agent gathers necessary details and produces structured specification documents that can be turned into implementation plans.\n\n**Examples:**\n\n<example> Context: User has a new feature idea but hasn't documented it yet. user: "I want to add a feature that lets users export their achievements as a PDF resume" assistant: "Let me use the spec-writer agent to create a specification document for this PDF export feature." <uses Task tool to launch spec-writer agent with topic> </example>\n\n<example> Context: User describes a complex requirement that needs to be structured. user: "We need to implement real-time collaboration on achievement documents, similar to Google Docs" assistant: "This is a complex feature that needs a detailed specification. I'll use the spec-writer agent to create a comprehensive SPEC.md document." <uses Task tool to launch spec-writer agent> </example>\n\n<example> Context: User mentions a feature from the roadmap that needs specification. user: "Can you create a spec for the achievement tagging system mentioned in TODO.md?" assistant: "I'll use the spec-writer agent to create a specification document for the achievement tagging system." <uses Task tool to launch spec-writer agent> </example>

Manage task documentation by syncing between local task directories and GitHub issues