project-docs

Initialize a new feature/fix/refactor/chore branch from develop

Discover and articulate project purpose, vision, and boundaries

Extract project structure and patterns as a reusable recipe

Generate comprehensive project summary and current state

Start development work from a DEV_KICKOFF.md file. Use when opening a fresh session to begin or resume implementation — finds DEV_KICKOFF.md, reads the mission, and follows the workflow defined in the document.

Use this agent when you need to create a detailed technical development plan from a proposal, feature request, or implementation instructions. This includes transforming high-level requirements into actionable development guidance, breaking down complex features into implementable phases, or creating structured plans that developers can follow for implementation. <example> Context: User has a proposal document and needs a development plan created from it. user: "I have a proposal for adding real-time notifications to our app. Can you create a dev plan for it?" assistant: "I'll use the dev-plan-generator agent to create a comprehensive development plan from your proposal." <uses Task tool to launch dev-plan-generator agent> </example> <example> Context: User describes a feature they want implemented and needs a plan. user: "We need to implement OAuth2 authentication with support for Google and GitHub providers. Please create a development plan for this." assistant: "Let me use the dev-plan-generator agent to create a detailed technical development plan for the OAuth2 implementation." <uses Task tool to launch dev-plan-generator agent> </example> <example> Context: User has completed a proposal review and needs to move to planning phase. user: "The team approved the API versioning proposal in docs/projects/api-versioning/proposal.md. Now I need a dev plan." assistant: "I'll launch the dev-plan-generator agent to transform this approved proposal into an actionable development plan." <uses Task tool to launch dev-plan-generator agent> </example>

Use this agent to review a single document for accuracy, implementation status, and whether it needs updates or archival. Assign ONE document per agent for thorough review. The agent validates documentation against the codebase and recommends appropriate actions based on document type. Examples: <example> Context: User wants to check if a specific proposal has been implemented. user: "Can you review docs/projects/user-defined-ai-operations/proposal.md?" assistant: "I'll launch the docs-curator agent to review this proposal against the codebase." <Task tool call to launch docs-curator agent with the document path> </example> <example> Context: User completed work and wants to verify a plan is done. user: "Check if the PowerSync migration plan is complete" assistant: "I'll use the docs-curator agent to verify the plan's implementation status." <Task tool call to launch docs-curator agent> </example> <example> Context: User wants to validate architecture documentation. user: "Is the MCP server architecture doc still accurate?" assistant: "I'll launch the docs-curator agent to validate this architecture doc against current code." <Task tool call to launch docs-curator agent> </example> <example> Context: User wants batch review of multiple documents. user: "Review all the proposals in docs/projects/" assistant: "I'll launch multiple docs-curator agents in parallel, one per project proposal, for thorough review." <Multiple Task tool calls, one per document> </example>

Use this agent when you need quick, focused development tasks completed efficiently. Ideal for small code changes, fixing individual functions, updating configuration files, renaming variables, adding simple features, or making targeted modifications. Not intended for architectural decisions, complex refactoring, or tasks requiring deep analysis.\n\nExamples:\n\n<example>\nContext: User needs a small function fixed.\nuser: "The formatDate function in utils.ts is returning the wrong format, it should be YYYY-MM-DD not MM-DD-YYYY"\nassistant: "I'll use the gopher-dev agent to quickly fix that date format issue."\n<Task tool launches gopher-dev agent>\n</example>\n\n<example>\nContext: User needs a quick file modification.\nuser: "Add a loading spinner to the submit button in LoginForm.vue"\nassistant: "Let me dispatch the gopher-dev agent to add that loading state to the button."\n<Task tool launches gopher-dev agent>\n</example>\n\n<example>\nContext: User needs a simple configuration change.\nuser: "Update the timeout value in the API client from 5000 to 10000ms"\nassistant: "I'll have the gopher-dev agent make that quick config update."\n<Task tool launches gopher-dev agent>\n</example>\n\n<example>\nContext: User needs a small feature addition.\nuser: "Add a console.log at the start of the handleSubmit function to debug the form data"\nassistant: "Perfect task for the gopher-dev agent - let me dispatch it to add that debug log."\n<Task tool launches gopher-dev agent>\n</example>

Use this agent when you need to conduct structured technical research, evaluate options, debug complex problems, or reduce uncertainty. This includes technology evaluation, library/framework comparisons, migration feasibility, root cause analysis, architecture research, system archaeology, performance debugging, security analysis, or any situation requiring systematic evidence gathering and documented findings. Examples: <example> Context: The user wants to evaluate technology options. user: "What state management library should we use for our new React project?" assistant: "I'll use the investigator agent to evaluate state management options and recommend the best fit for your project." <Task tool call to investigator> </example> <example> Context: The user needs to debug a complex issue. user: "Our API response times have increased from 200ms to 2 seconds over the past week. Can you investigate?" assistant: "I'll launch the investigator agent to systematically investigate this performance regression." <Task tool call to investigator> </example> <example> Context: The user wants to understand migration implications. user: "We're considering moving from MongoDB to PostgreSQL. Can you investigate what that would involve?" assistant: "I'll use the investigator agent to analyze the migration path, effort, and risks." <Task tool call to investigator> </example> <example> Context: The user needs to understand an unfamiliar system. user: "I need to understand how our authentication system works - can you research it?" assistant: "I'll launch the investigator agent to conduct a thorough analysis of the authentication system." <Task tool call to investigator> </example> <example> Context: Proactive use - uncertainty identified during development. user: "Let's add real-time notifications to the app." assistant: "Before implementing, there are several approaches (WebSockets, SSE, polling) with different tradeoffs. Let me use the investigator agent to evaluate the options." <Task tool call to investigator> </example>

Use this agent when the user needs to create a formal proposal document from investigation findings, research notes, or other input materials. This agent should be triggered when translating discovered information into actionable, structured proposals. Examples: <example> Context: User has completed an investigation and wants to formalize findings into a proposal. user: "I've finished investigating the authentication refactor. Can you help me create a proposal for it?" assistant: "I'll use the proposal-writer agent to create a formal proposal from your investigation findings." <commentary> Since the user has completed an investigation and wants to create a proposal, use the Task tool to launch the proposal-writer agent to read the investigation document and generate a properly structured proposal. </commentary> </example> <example> Context: User provides raw information and wants it turned into a proposal. user: "I have some notes about implementing a caching layer. Here's what I'm thinking: [details]. Can you write this up as a proposal?" assistant: "I'll use the proposal-writer agent to transform your notes into a formal proposal document." <commentary> Since the user wants to convert informal notes into a formal proposal, use the proposal-writer agent to structure the information according to the proposal template and create the documentation. </commentary> </example> <example> Context: User references an existing investigation file. user: "Please create a proposal based on the investigation in docs/investigations/database-migration.md" assistant: "I'll use the proposal-writer agent to read the investigation and generate a project folder with a proposal." <commentary> Since the user is asking to create a proposal from an existing investigation document, use the proposal-writer agent to analyze the investigation, create a project folder, and produce a well-structured proposal. </commentary> </example>

Review backlog items and organize them into project groupings with parallelism analysis. This skill should be used when the user asks to "organize the backlog", "group backlog items into projects", "review backlog for project planning", "what projects should we create from the backlog", "prioritize backlog items", or when the backlog has accumulated enough items that grouping and project creation would be valuable.

Create a structured investigation document from a rough idea, voice note, or freeform thoughts. Use when the user has an unstructured question or concern they want to explore — transforms conversational input into a formal investigation in docs/investigations/. Triggers when user says "investigate this", "I've been thinking about", "should we look into", "start an investigation", or provides rough voice-to-text or bullet-point input that needs structuring.

Create a new project folder with proposal scaffold in docs/projects/. Use when work needs a project home — whether starting from an investigation, writing a new proposal, or beginning any feature that warrants structured tracking. This is a prerequisite for generate-dev-plan, generate-design- resolution, and generate-test-plan. Triggers when user says "let's create a project", "start a proposal", "we should work on this", "let's build this", or when transitioning from an investigation to actionable work. Also use when generate-proposal needs a project folder to write into.

Pre-planning technical discovery for complex features. Orchestrates explorers to gather codebase context, validates architecture docs, and prepares comprehensive input for the dev-plan-generator. Use when the user has a proposal or feature idea that needs codebase analysis before planning — maps existing patterns, validates assumptions, and surfaces constraints. Triggers when user says "explore the codebase for this feature", "do technical discovery", "what does the codebase look like for this", "analyze the code before we plan", or wants pre-planning research documented as a discovery artifact.

Orchestrate the full proposal-to-implementation process, either via a git worktree (isolated branch) or directly in the main repo. Use when the user has a finalized proposal and is ready to begin development — creates a branch or worktree, writes a DEV_KICKOFF.md handoff document, optionally runs dev-discovery and generates the development plan. Triggers when user says "kick off dev", "start implementation", "ready to implement", "let's build this", or references a proposal that needs implementation. Replaces parallel-worktree-dev.