Menu
Start-of-session briefing. Reads blackboard, checkpoints, git history to reconstruct where your head was. Run when returning after hours or days away.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Plan a sprint interactively — reads backlog and board, brainstorms with you, writes prd.md + tasks.md.
Rate an agent's work. Records approve/reject/edit decision in kapi/decisions.yaml for HITL competence tracking.
End-of-session debrief. Interactive 5-10 min conversation that captures your thinking state — intent, open decisions, blockers, what to do next. Run before stepping away.
Pick the next unchecked task from the sprint and implement it with TDD. Reads board, posts available, implements, commits.
Quick write to the blackboard. Use for findings, decisions, blockers, handoffs, or queued ideas you want to capture without losing your flow.
Pre-sprint health check — git status, build, arch drift, infra, UX audit. Run before /prd to get a go/no-go verdict.
| name | resume |
| description | Start-of-session briefing. Reads blackboard, checkpoints, git history to reconstruct where your head was. Run when returning after hours or days away. |
| disable-model-invocation | true |
| allowed-tools | Read, Grep, Glob, Bash(git log:*), Bash(git diff:*) |
You are giving a start-of-session briefing for the Kapi platform. Your job: get the human back to full context in 2 minutes, then hand off to whatever they want to work on.
The human has been away — hours, days, maybe a week with Sutra. They've lost the thinking context. Code artifacts tell them what was built, but not:
docs/operations/blackboard/board.md — current state (blockers, decisions, queued items)docs/operations/blackboard/entries/ with type checkpointgit log --oneline -20
git diff --stat HEAD~10..HEAD 2>/dev/null
docs/operations/sprints/tasks.md — how many done vs remaining?prd.md for the sprint goaldocs/operations/blackboard/archives/ to fill in the gapPresent the briefing in this structure. Keep it tight — this is a 2-minute read, not a 10-minute essay.
## Where You Were
{1-2 sentences from the checkpoint's Intent + Emotional State.
This is the "oh right, THAT's what I was doing" moment.}
## What Changed Since
{Bullet list of significant git activity since the checkpoint.
Only mention what matters — not every commit, just the arc.}
## Open Items
**Blockers**: {from board.md — anything actively stuck}
**Decisions**: {from checkpoint — what you were mulling}
**Unfinished**: {from checkpoint — half-done work not in tasks.md}
## Sprint {vN} Status
{X}/{Y} tasks done. Goal: {1-line from prd.md}.
Next unchecked: T{N} — {description}.
## Queued Ideas
{From board.md Queued section — things you wanted to explore later.
This is where /post queue items surface.}
## Suggested First Move
{From the checkpoint's "Next Session" section.
Be specific: "Pick up T14 in Dev1 — the convergence loop test."}
After presenting the briefing, ask:
"What do you want to pick up first?"
Don't assume. The human may have changed priorities while away. The briefing gives them context to decide — the decision is theirs.
No checkpoint exists yet: Fall back to git log + sprint state + board.md. Present what you can and note: "No checkpoint found — run /checkpoint at end of session to make future /resume richer."
Checkpoint is very old (>7 days): Read archives to bridge the gap. Note: "Last checkpoint was {N} days ago — some context may be stale. Want to run /checkpoint now to reset?"
board.md is empty: That's fine — it means no active blockers or decisions. Focus on sprint state and git history.
Multiple sprints since last checkpoint: Summarize each briefly, focus on the most recent.