From 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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/developer:spike-itThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This is the PRD skill. It produces the specification that feeds `/task-it`.
This is the PRD skill. It produces the specification that feeds /task-it.
Build a complete understanding of a problem, then create a ticket in the project's tracker that captures it.
Tracker: "the project's tracker" means whatever issue system the repo's CLAUDE.md declares — a GitHub issue via
gh, a Jira ticket via the Atlassian MCP, etc. Read it to learn which tracker is in use and how to create and reference tickets. Default to GitHub issues viaghif nothing is declared.
$ARGUMENTS may contain any combination of:
/look-upIf $ARGUMENTS is empty, use AskUserQuestion:
What are we spiking? Give me a ticket reference, documentation link, description, or any combination.
Gather everything provided. For each ticket, fetch its content via /look-up. For each documentation page, fetch the content. Summarise all gathered context back to the user in bullet points.
Invoke /grill-it to fully understand the problem before producing anything. Pass it the gathered context from Step 1 and these spike-specific areas to probe (skip what's already clear):
All questions must be resolved before proceeding. If /grill-it surfaces questions that cannot
be answered in-session, flag them as blockers and ask the user how to resolve them — do not carry
unresolved questions into the output.
Based on the clarified understanding, do the research needed to fill gaps. This may include:
Summarise key findings to the user before writing. Ask if anything is missing.
Compose the ticket body using the issue template as a starting structure but adapt it to the investigation:
> blockquote for one-line section summaries---) between major sections#N for GitHub, ENG-123 for Jira, …)Create the ticket in the project's tracker (per the repo's CLAUDE.md — gh issue create for GitHub,
the Atlassian MCP for Jira, etc.) using a spike: title prefix.
Show the ticket URL/key and a brief summary of what the spike covers.
Ask the user which (if any) they want:
/task-it/plan-itnpx claudepluginhub xxkeefer/skills --plugin developerCreates bite-sized, testable implementation plans from specs or requirements, with file structure and task decomposition. Activates before coding multi-step tasks.