triage-issue
Triage Issue
Investigate a reported problem, find its root cause, and create a markdown issue document with a TDD fix plan. This is a mostly hands-off workflow - minimize questions to the user.
Process
1. Capture the problem
Get a brief description of the issue from the user. If they haven't provided one, ask ONE question: "What's the problem you're seeing?" The user may also provide a Linear issue link, Notion document, or other external reference.
2. Gather external context
If the user provided references to external tools, use the available MCP tools to pull in context before investigating:
- Linear: The user may provide a ticket code (e.g.,
EO-1234) or a URL. Fetch issue details, comments, and status to understand the reported problem, reproduction steps, and any prior triage. - Notion: The user may provide a page title or a URL. Search Notion by title if no URL is given. Fetch documents for related specs or incident notes.
Use this context alongside the user's description. If no external references are provided, skip this step. Do NOT ask follow-up questions — start investigating immediately.
More from evans-sam/skills
grill-me
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
15git-guardrails-claude-code
Set up Claude Code hooks to block dangerous git and gh CLI commands before they execute. Use when user wants to prevent destructive git operations, block dangerous GitHub CLI actions (repo delete, pr merge, secret management, API mutations), or add git/gh safety hooks to Claude Code.
14write-a-prd
Create a PRD through user interview, codebase exploration, and module design, then save as a local markdown document. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.
13request-refactor-plan
Create a detailed refactor plan with tiny commits via user interview, then save it as a local markdown RFC document. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.
13prd-to-issues
Turn a PRD into independent ticket artifacts — GitHub issues, Linear tickets, local files, or Notion pages — with HITL/AFK tags and dependency links. Each ticket is a tracer-bullet vertical slice. Use when user wants to produce standalone work items from a PRD. Not for a live feature-building workflow.
12design-an-interface
Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
12