.dotfiles

Creative brainstorming partner who explores ideas, suggests alternatives, and challenges assumptions. Use when ideating, exploring possibilities, or generating multiple approaches to a problem.

Information gathering specialist that researches and summarizes codebase details. Use when you need to understand how something is used, find patterns, or investigate specific concepts in the project. Trigger when users say things like "tell me about", "how is X used", "show me examples of", "where is X defined", or "inspect the usage of".

Create and manage Jira tickets with pre-configured OFW organization context. Handles ticket creation with proper field mappings, team assignments, sprints, and epic linking.

Maps out complete code execution paths through a feature or workflow. Traces from entry point through all layers (controller → service → repository → etc.) and creates a navigable quickfix list in neovim. Use when users ask "how does X work", "trace the path for X", "map out the X workflow", or "show me the X code flow".

Strategic planning partner who gathers context, asks clarifying questions, and creates detailed implementation plans without making code changes. Use when the user wants to plan out how to implement a feature, understand the scope of a task, break down complex work, or get a roadmap before coding. Trigger when users say things like "let's plan this out", "how should we approach this", "create a plan for", "what's the best way to implement", or "help me understand what needs to be done".

Thoroughly review pull request changes between current branch and origin/main (or specified base branch). Analyzes code patterns, best practices, test coverage, security, performance, and maintainability. Use when the user wants a comprehensive code review of their changes.

Analyze git changes and generate succinct PR summaries with three sections - why changes were made, what was changed, and notes for reviewers. Use when the user wants to create or summarize pull request content.

Helps you code by opening files in tmux/neovim and providing guidance - you write the code

Implements code following the spec exactly - writes tests or implementation for a specific chunk

Creates detailed TDD specifications through interactive planning - clarifies requirements, explores codebase, writes actionable specs

Critically reviews implementation against spec - checks security, bugs, edge cases, and spec compliance

Orchestrates full spec-driven development workflow from specification to implementation

DEPRECATED - Use spec-planner instead (now combined into one skill)

Generate test files for a specific function by finding endpoints or Kafka topics that trigger it. Creates HTTP files for REST endpoints or JSON payloads with Kafka config for message consumers.