agent-stuff

Use ONLY when the user explicitly asks for it — e.g. "explain this code," "walk me through this module/feature/API," "review this for me," "/explain-code," or points at a file/function/snippet and asks what it does. Produces a short, high-level report on existing (already-committed, no-diff) code: what it does, how it's structured, non-obvious behavior, edge cases, risk flags, open questions, and where to look next. Do NOT trigger automatically just because code is present in context or was recently discussed — wait for the user to ask.

Use ONLY when the user explicitly asks for it — e.g. "practice IELTS speaking", "IELTS speaking practice", "help me with IELTS", "IELTS part 1/2/3", or similar direct requests. Do NOT trigger on general mentions of IELTS or English speaking unless the user explicitly invokes this skill by name.

Use ONLY when the user explicitly asks for it — e.g. "mock interview me", "do a mock interview", "practice interview questions", "interview me", "drill technical Q&A", or similar direct requests. Do NOT trigger on general interview-related discussion unless the user explicitly invokes this skill by name.

Use ONLY when the user explicitly asks for it — e.g. "create a product brief", "flesh this out", "turn this idea into a product brief", or similar direct requests. Do NOT trigger on general product discussions or idea sharing unless the user explicitly invokes this skill by name.

Use ONLY when the user explicitly asks for it — e.g. "document this API", "hand off this endpoint", "prepare FE integration notes", or similar direct requests. Do NOT trigger automatically when documenting or summarizing code — wait for the user to ask.

Use ONLY when the user explicitly asks to enter brainstorming mode by name (e.g. "brainstorm first", "let's brainstorm", "start a brainstorming session"). Do NOT trigger on general discussion, questions, requests for suggestions, or solution exploration unless the user explicitly invokes this skill by name.

Use ONLY when the user explicitly asks for it — e.g. "give me the change report," "summarize the changes," "what did you change," "/change-report," or similar direct requests. Produces a short, high-level report (not a line-by-line walkthrough) covering what changed, behavior differences, assumptions made, known gaps, risk areas, and what to verify manually — so the user can review quickly without reading the whole diff. Do NOT trigger this automatically after writing or editing code — wait for the user to ask.

Stage all changes, generate a Conventional Commit message from the diff, and commit. Use when the user says "commit", "commit this", "commit my changes", "commit for me", or wants a clean git commit without manual staging or message writing.

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".

<short summary>. Use when <trigger condition>.