
This skill will be invoked when the user wants to create a PRD. You should go through the steps below. You may skip steps if you don't consider them necessary. 1. Ask the user for a long, detailed description of the problem they want to solve and any potential ideas for solutions. 2. Explore the repo to verify their assertions and understand the current state of the codebase. 3. Interview the user relentlessly about every aspect of this plan until you reach a shared understanding. Walk down e
Code review: read diffs, run checks, report findings.
Create, modify, and render D2 diagrams using the d2 CLI. Use when the user asks for diagrams, architecture visuals, ERDs, sequence diagrams, flowcharts, grid layouts, or any declarative diagramming task. Trigger phrases include "d2 diagram", "create a diagram", "architecture diagram", "sequence diagram", "ERD", "flowchart", "draw", "visualize".
# PRD to Issues Break a PRD into independently-grabbable GitHub issues using vertical slices (tracer bullets). ## Process ### 1. Locate the PRD Ask the user for the PRD GitHub issue number (or URL). Fetch it with `gh issue view <number>`. Read and internalize the full PRD content (with all comments). ### 2. Explore the codebase Read the key modules and integration layers referenced in the PRD. Identify: - The distinct integration layers the feature touches (e.g. DB/schema, API/backend, UI
--- name: refactor-pass description: Perform a refactor pass focused on simplicity after recent changes. Use when the user asks for a refactor/cleanup pass, simplification, or dead-code removal and expects build/tests to verify behavior. --- # Refactor Pass ## Workflow 1. Review the changes just made and identify simplification opportunities. 2. Apply refactors to: - Remove dead code and dead paths. - Straighten logic flows. - Remove excessive parameters. - Remove premature optimizati
Deep research before planning. Launches parallel agents to search docs, web, and codebase, then synthesizes findings into actionable context.
Extract and format Slack huddle transcripts for analysis. Use this skill when processing Slack huddle transcript files (.vtt), when user mentions huddle transcript or Slack transcript, when user uploads a VTT file from Slack, or when user asks to summarize or analyze a Slack meeting/huddle. Handles VTT format transcripts with speaker identification, timestamps, and conversation merging.
Deep-dive spec interviewer. Reads a file or requirement, analyzes it against the codebase, then conducts a rigorous 1-on-1 interview using AskUserQuestion to produce a comprehensive, opinionated specification document. Acts as a collaborative architect with active pushback.