klair-legacy

Create feature branch, commit changes, and open PR

Analyzes a high-level feature request and maps it to the project roadmap, identifying dependencies, blockers, and optimal implementation sequence.

Load essential project context to begin development. Reads core documentation and shows current project status.

You are conducting efficient web research to answer the user's query with high-quality, well-sourced information.

Use this agent when: 1. A bug or issue is discovered during development, testing, or code review 2. An error occurs that needs to be tracked and investigated 3. Unexpected behavior is observed in the application 4. A user reports a problem that needs formal documentation 5. Code analysis reveals potential issues requiring investigation Examples of when to use this agent: <example> Context: A developer encounters an error during testing and wants to document it properly. user: "I'm getting a 500 error when trying to fetch financial data from the API endpoint" assistant: "Let me use the Task tool to launch the bug-documenter agent to properly document this issue." <Task tool call to bug-documenter agent with context about the 500 error> <commentary> The user has encountered a bug that needs proper documentation. The bug-documenter agent will create a structured bug report in the bugs/ directory using the templates from .claude/templates/bug-solver. </commentary> </example> <example> Context: Code review reveals a logic error that needs investigation. user: "The budget calculation in the AI budget analyzer is returning incorrect totals for certain date ranges" assistant: "This looks like a bug that needs proper documentation. Let me use the Task tool to launch the bug-documenter agent to create a formal bug report." <Task tool call to bug-documenter agent with details about the budget calculation issue> <commentary> A logic error has been identified during code review. The bug-documenter agent will create a structured documentation following the project's bug reporting templates. </commentary> </example> <example> Context: User reports unexpected behavior in production. user: "Users are reporting that the Clerk authentication redirects aren't working properly after logout" assistant: "This is a critical bug that needs immediate documentation. I'll use the Task tool to launch the bug-documenter agent to create a comprehensive bug report." <Task tool call to bug-documenter agent with authentication redirect issue details> <commentary> A production issue has been reported. The bug-documenter agent will document this with proper severity and context for investigation. </commentary> </example>

Validates generated checklist covers all spec requirements. Ensures every FR has tests and implementation tasks.

Analyzes implementation patterns with specialized focus on Result types, neverthrow error handling, validation patterns, and testing approaches

Locates relevant files and code sections for feature implementation, understanding project structure and module organization

Locates relevant files and code sections for feature implementation, understanding project structure and module organization

Compares two branch implementations of the same spec across multiple criteria (spec compliance, code quality, testing, performance). Use when analyzing competing implementations, evaluating prototype branches, or choosing between implementation approaches. Triggers on "compare prototypes", "compare branches", "compare implementations", "evaluate prototypes".

Use when user wants to explore multiple implementation approaches for a feature by creating parallel Claude Code sessions. Triggers on phrases like "competitive prototyping", "prototype in parallel", "compare implementations", "try different approaches", or "race implementations".

Generates daily standup updates from your GitHub PRs formatted for Google Chat. Use when creating standup reports, preparing daily updates, generating work summaries, or crafting team status updates.

Guides users through creating Agent Skills for Claude Code. Use when building new skills, designing skill structure, or authoring skill documentation. Triggers on "create skill", "build skill", "new agent skill", or "skill development".

Guides users through creating custom slash commands for Claude Code. Use when user wants to create, build, or develop slash commands, automate workflows, or create command shortcuts.