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".
Compose a new UI component following shadcn/ui authoring patterns — composable, modular, multi-export React components with Tailwind styling hooks. Use when the user wants to create a new React component, abstract an existing one, or build a composable component family (e.g., SwipeCard + SwipeCardHeader + SwipeCardItem). Triggers on "compose a component", "create a component", "abstract this into a component", "make this composable", "new UI component", "/compose-component", or when a user wants to follow shadcn/ui component patterns for a custom component.
Generate a agent-loop-prompt.md file at the project root that defines an agent loop — the repeatable task cycle an autonomous agent follows: study the plan, pick the next task, implement, validate, update progress, and commit. Also known as "Ralph" — trigger when the user says "Ralph", "the Ralph process", "set up Ralph", "create an agent loop", "generate a agent-loop-prompt.md", "set up the agent loop", or "/create:agent-loop-prompt".
Generate a structured, file-based implementation plan from a spec or PRD. Use when the user asks to turn a spec, PRD, or requirements document into an ordered set of implementation tasks, or requests an "implementation plan." Triggers on "/generate:plan".
Triage a raw, ad-hoc markdown file of mixed issues, bugs, fixes, and feature requests into discrete, well-specified tasks written to a PRD.md file. Use when the user has a hastily written notes file containing scattered work items across multiple topics (UI fixes, backend changes, new features, bugs, etc.) and wants them organized into standalone, implementable task specs. Triggers on "/ingest:issues" or when the user asks to "triage issues", "turn notes into tasks", "organize my backlog", or "create a PRD from my notes".
Generate or update an ARCHITECTURE.md file for a codebase. Use when the user asks to create, write, update, or improve an ARCHITECTURE.md, or asks for a high-level architectural overview document of their project.
Write a detailed component specification extracted from an architectural document. Use when the user asks to create a spec, write a specification, detail a component, or define requirements for a component within a larger system. Triggers when the user references an architecture doc (ARCHITECTURE.md or similar) and wants to drill into a specific component's requirements, interfaces, behavior, and validation criteria. Also use when the user says "spec out", "write a spec for", or "/component-spec".
Kick off autonomous feature development. Creates a git worktree, generates an implementation plan from a spec, configures the agent-loop prompt, and launches the agent loop in a new tmux pane. Use when starting work on a new feature. Triggers on "/workflow:build-spec".