kcap

This skill should be used ONLY when the user explicitly asks to run a structured agent *flow* by name or definition id — e.g. "start a flow", "run the code-review flow", "run the X flow", "use flow definition X", "kick off an agent flow", or wants an iterative loop run by a separate hosted participant agent that continues until sign-off. It covers the same underlying tools as the `review-flows` skill (`start_review_flow` etc. are aliases of the generic tools documented here) — use `review-flows` for the two built-in review kinds (`spec-review`, `code-review`) and this skill for any other flow definition, or when the user names a `definition_id` explicitly. Do NOT use this skill (and do NOT call the flows MCP tools) for an ordinary request such as "review my PR", "do X for me", or "check this over" where the user just wants you to do the work yourself — perform that work directly instead.

This skill should be used when the user asks to "disable recording", "stop recording", "delete this session", "don't record this", "remove my session data", "erase this session", "turn off tracking", "stop tracking", "disable kcap", "remove session", or wants to stop the current session from being recorded. Stops the watcher, prevents future hooks, and deletes server data.

This skill should be used when the user asks to "show errors", "extract errors", "what went wrong", "find tool errors", "review errors from session", "check session errors", "list failures", "what failed in session X", "error report", "show mistakes", or wants to review tool call errors from a recorded session. Provides instructions for extracting tool errors via the kcap CLI.

Follow a kcap import that setup just started and the evals landing on it — "Follow my kcap import" (the prompt `kcap setup` hands to your agent), "watch my import", "how is my import going", "are my evals done yet". Reads the handoff file setup wrote, polls Capacitor analytics for exactly the sessions that import created, summarizes the first three completed evals, links to the results and offers the guided tour. Not for browsing evals in general — that is the analytics or guided-tour skill.

Guided tour of Kurrent Capacitor for someone who has it installed but does not yet know what it does for them — "what does capacitor do for me", "what is capacitor", "is this thing doing anything", "what can kcap do", "just installed capacitor, now what", "give me a tour", "Start kcap guided tour" (the prompt `kcap setup` tells them to type) — or when they invoke this skill directly by its listed name. Shows the team's recorded sessions, spend and errors, then offers per-use-case tutorial tours (evals, session recall, PR review, analytics). Also handles the missing pieces: offers to install kcap if it is not set up, and to import history if the user has no sessions. Not for general session recall on an established user — that is the recap skill.

This skill should be used when the user asks to "hide this session", "make this private", "hide session", "owner only", "make private", "hide from others", "set private", "don't show this session", or wants to change the current session visibility to owner-only. Sets session visibility so only the owner can see it.

This skill should be used whenever you write or read a plan, spec or design document, when you start executing a plan, and whenever a task list, todo list or checklist comes up — yours or the user's. It says how to record the plan and its tasks in Kurrent Capacitor through the `kcap mcp plans` MCP tools, so progress shows in the session view and survives context compaction.

This skill should be used ONLY when the user explicitly asks to run a structured review *flow* — e.g. "start a review flow", "submit this for review", "re-review after I address findings", or wants an iterative review loop run by a separate reviewer that continues until sign-off. Do NOT use this skill (and do NOT call the flows MCP tools) for an ordinary review request such as "review my PR", "review this diff/spec/design", or "code review" where the user just wants you to review it yourself — perform that review directly instead.

Use this skill when implementation is complete — a feature or bugfix is functionally finished, tests pass, or you are about to commit / open a PR / merge — or when a spec is finalized. At that moment, proactively OFFER an independent second-harness review even if the user did not ask, because a fresh, separate reviewer catches what the author's own model misses. It calls list_reviewer_vendors to recommend a reviewer that will actually run for this repo, offers a spec-review or code-review flow, and hands off to the review-flows skill only after the user accepts — it never starts a flow itself. Do NOT use it when the user asks you to review something yourself ("review this", "code review this", "look over my spec"), or mid-task before the work is finished.

This skill should be used when the user asks to "validate plan", "verify plan", "check plan completion", "did I finish everything", "is the plan done", "what's left to do", "validate my work", or wants to verify that all planned items were completed.

This skill should be used when you are planning or discovering the SHAPE of a work item — that it breaks into sub-tasks (a parent and its parts), or that one piece must land before another (a blocks / blocked-by dependency) — and you want that structure recorded so it shows up in Kurrent Capacitor's Home "Blockers & dependencies" view and progress figures. Also use it the moment you decide to defer a piece of work, to record it as a loose end in the user's next-work ledger, and whenever the user asks what to work on next or you are about to propose new work, to read the ranked next-work feed first. Use the `kcap mcp workitems` MCP tools to DECLARE the breakdown, the relations and the loose ends, and to read the feed. Do NOT declare STRUCTURE for ordinary "attach this session to issue X" correlation alone (a single `declare_work_item` call, no structure), or for a single indivisible task with no parts and no dependencies — a loose end is worth declaring in either case.