session-skills

Plugin session-skills from marketplace claude-toolkit in Mar5929/claude-toolkit. Commands read from the repo's manifest — 1 month ago.

Skills (11)

• braindump

  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

• explain-simply

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

• grill-me

  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 docu

• handoff

  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", "pro

• requirements-helper

  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.

• session-summary

  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

• solution-design

  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 re

• spec-check

  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 PRD file (knowledge/prds/, or prds/ with

• track-tasks

  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", "a

• unslop

  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

• work-guide

  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.

Subagents (7)

• delivery-researcher

  Research a focused delivery question using project evidence and current official sources, returning findings and uncertainties to the owning conversation without changing records.

• delivery-reviewer

  Independently review requirements, a solution design, or a delivery plan for gaps and conflicts, using the agreed scope and project or work-item variations without changing records.

• design-architect

  Write or fix one solution design option from the design preparation and Notes, the requirements, the research reports, and the existing build. Verifies community claims before using them, uses built-in mechanisms unless the owner chose otherwise, and recommends a rewrite when that serves the require

• design-critic

  Check a draft solution design against every requirement and against the plain-language writing rules, returning one verdict per requirement with evidence and a list of findings for the architect to fix. Read-only; it never edits or approves.

• design-product-analyst

  Check that a work item's requirements are complete, explicit end to end, and coherent inside the larger system before any design starts. Returns a plain ready or not-ready statement, the missing pieces, the places that are not explicit, and the wording a builder agent could misread, each with a fix.

• design-researcher

  Answer one bounded research question for a solution design using official documentation, project evidence, and community sources such as Reddit, Stack Overflow, GitHub issues, and forums. Returns findings labeled by source type without changing any record.

• handoff-verifier

  Check, without changing anything, that a drafted handoff prompt states the overarching goal and that every fact in it holds up, before the owner sees it.

Similar plugins