developer

Deep-dive investigation of a feature, bug, or technical problem. Accepts tracker tickets, wiki pages, or a plain description — delegates to /grill-it for clarification until the problem is fully understood, then creates a ticket in the project's tracker capturing the spike. Use when the user says "spike it", "spike this", "investigate this", "flesh this out", "hydrate ticket", "improve ticket", "research this", "feasibility study", or wants to fully understand a problem before committing to implementation.

Turn a /spike-it output into tracker tickets ready for /plan-it or /do-it. Decomposes the spike into demo-able blocks of work, gets user approval, resolves the epic, then creates the tickets in the issue tracker. Use when the user says "task it", "create tickets", "break into tickets", "make the tickets", or wants to turn a spike or feature breakdown into tracked issues.

Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.

Resolve git merge/rebase conflicts in a file using its history and the in-progress operation as context. Simple conflicts resolve automatically; complex ones (both sides added, or a migration/refactor collided with edits) pause for the user with evidence and a justified recommendation. Then follows links to conflicted test siblings and refactor parents/children. Usage: resolve-conflicts <filepath>. Use when the user says "resolve conflicts", "fix the merge", "resolve this conflict", or hands you a conflicted file.

Critically assess code review feedback before applying fixes. Accepts feedback from AI reviewers (e.g. GitHub Copilot, CodeRabbit), human reviewers, or directly as arguments. Use when user says "resolve it", "address feedback", "resolve feedback", pastes review comments, or wants to evaluate PR suggestions. Do NOT blindly trust the reviewer — analyze validity, trade-offs, and alternatives first.