session-skills

Play back a pasted brain dump in very simple language and confirm the understanding before doing any work. Use when the owner types /braindump after or alongside a loose spoken-style dump of what they want, or says "play that back", "tell me what you heard", "make sure you understood that before you start", or "here's a brain dump" followed by a request to confirm understanding first.

Re-explain the last answer, a plan, or a named document as short bullets a non-technical reader gets in one pass, keeping every number, name and file path. Use when the owner types /explain-simply, or says "explain that like I'm five", "explain it like I'm 5 years old", "put that in plain bullets", "simpler", or asks for the short bulleted version of something you just said.

Interview the user relentlessly about a plan, design, or topic while checkpointing every answer to a brainstorm file so nothing is lost. Use when the user wants to stress-test a plan, get grilled on a design, run a brainstorm or discovery session, extract what is in their head into a persistent document, or says "grill me".

Save a temporary session handoff and write a checked, self-contained prompt for a fresh session to carry on from. Use when the owner says "write a handoff", "hand this off", "handoff prompt", "I'm going to clear context", "start a new session", "this session is getting long", "carry this over", "prompt for a new chat", or runs /handoff. Use the check on its own, with "/handoff check", when the owner has a handoff prompt from somewhere else and wants it verified. Update any active work tracker first, then run the installed knowledge-save or legacy remember review. Preserve the checked continuation under Session handoffs in current working memory when that system is configured.

Write or refine plain-language PRDs and work-item requirements in the project's chosen record through a guided, one-question-at-a-time conversation. Use to clarify a problem, capture required behavior, handle changed answers, or resume a requirements interview.

Summarize this chat session as a table of the main things the user asked for and where each one stands, followed by anything that still needs the user. Use this whenever the user asks to summarize, recap, or catch up on the session or conversation, asks "what did I ask for", "what did we do", "where do things stand", "status of my requests", "session summary", "recap this chat", or runs /session-summary. Also use it when a session is wrapping up or being handed off and the user wants the requests-and-status view rather than a story of the work. Prefer this over writing a narrative summary of your own actions, even when the user's wording is casual.

Design a solution for approved requirements as a process flow. The main conversation checks the requirements are complete and explicit end to end, agrees the way of working with the owner, recommends a team of agents sized to the item, then runs research, design, and a critique loop against every requirement until all are satisfied. Produces one or more plain-language design options a junior intern could build from. Use when a work item has approved requirements and needs a design, when the owner wants design options, or says "design this", "solution this", or "how should we build this".

Check the specification an agent is about to build from or design a solution from, flag anything that could skew the work, and propose fixes before any building starts. Use when the owner types /spec-check, when a session is about to build or solution from a knowledge/prds/ file or a ticket body, or when the owner says "check the spec", "is this spec clean", or "make sure the spec hasn't drifted".

Build or refresh the running list of every topic still open in this chat session, using Claude Code's built-in task list, then print it. Use when the owner runs /track-tasks, or says "what is still open", "where are we", "what are we tracking", "list the open topics", "what have we not finished", "add that to the list", "park that one", or "close that one". Also use when a session has drifted across several unrelated topics and no list exists yet. Do not use for work that outlives this session: a ticket belongs in the project's work tracker, and unfinished state being carried to a fresh session belongs in a handoff prompt.

Strip the patterns that make writing read as machine-written from a file, pasted text, or the last answer, then hand back a version with a human voice. Use when the owner types /unslop, or says "this reads like AI wrote it", "unslop this", "take the AI out of this", "make this sound human", "remove the AI tells", or asks for a draft to be cleaned up rather than rewritten from scratch. Runs only when asked, never on its own.

Guide delivery in the main conversation, maintaining the chosen work item's adaptable plan and coordinating specialist help. Use when organizing project work, planning milestones or parallel items, switching context, or asking what should happen next.