/recap
Quick summary of the last session — commands run, files changed, and what to do next.
$ npx -y skills add sharpdeveye/maestro --skill recap --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/recap
Context preview
The summary Claude sees to decide when to auto-load this skill.
Quick summary of the last session — commands run, files changed, and what to do next.
SKILL.md
recap.SKILL.mdname: recap
description: "Quick summary of the last session — commands run, files changed, and what to do next."
argument-hint: "[optional: session file]"
category: utility
version: 2.0.0
user-invocable: true
MANDATORY PREPARATION
Invoke /agent-workflow — it contains workflow principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no workflow context exists yet, you MUST run /teach-maestro first.
---
Get back up to speed fast. Recap reads the most recent session file and recent decisions to tell you where you left off and what to do next.
Data Sources
1. **`.maestro/sessions/`** — read the most recent session file (by filename date) 2. **`.maestro/decisions.jsonl`** — read the last 5 decisions
If no session files exist, read the last 10 decisions and summarize those instead.
If no data exists at all, respond: *"No session history found. Run `/capture` at the end of your next session to start tracking."*
Output Format
┌─────────────────────────────────────┐
│ LAST SESSION RECAP │
├─────────────────────────────────────┤
│ Date: YYYY-MM-DD │
│ Commands: /diagnose → /fortify (2) │
│ Files: 3 changed, 1 created │
│ Outcome: Completed │
├─────────────────────────────────────┤
│ PICK UP HERE: │
│ 1. Run /guard — rate limiting │
│ 2. Run /evaluate — adversarial tests│
└─────────────────────────────────────┘
Recap Rules
- Be concise — this is a 30-second read, not a report
- Lead with the "PICK UP HERE" section — that's what the user needs
- If the session ended with open issues, highlight them
- Reference specific files and commands, not vague summaries
Recap Checklist
- [ ] Most recent session identified
- [ ] Commands and outcomes summarized in one line each
- [ ] "Pick up here" section has specific, actionable next steps
- [ ] Open issues from last session surfaced
Recommended Next Step
After recapping, run the first command listed in "Pick Up Here" to continue where you left off.
**NEVER**:
- Dump the entire session file — summarize it
- Recap without checking decisions.jsonl for recent activity
- Give vague next steps ("continue working") — be specific
- Assume context from the current conversation — only use persisted data
Read more
name: recap description: "Quick summary of the last session — commands run, files changed, and what to do next." argument-hint: "[optional: session file]" category: utility version: 2.0.0 user-invocable: true
MANDATORY PREPARATION
Invoke /agent-workflow — it contains workflow principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no workflow context exists yet, you MUST run /teach-maestro first.
---
Get back up to speed fast. Recap reads the most recent session file and recent decisions to tell you where you left off and what to do next.
Data Sources
1. **`.maestro/sessions/`** — read the most recent session file (by filename date) 2. **`.maestro/decisions.jsonl`** — read the last 5 decisions
If no session files exist, read the last 10 decisions and summarize those instead.
If no data exists at all, respond: *"No session history found. Run `/capture` at the end of your next session to start tracking."*
Output Format
┌─────────────────────────────────────┐ │ LAST SESSION RECAP │ ├─────────────────────────────────────┤ │ Date: YYYY-MM-DD │ │ Commands: /diagnose → /fortify (2) │ │ Files: 3 changed, 1 created │ │ Outcome: Completed │ ├─────────────────────────────────────┤ │ PICK UP HERE: │ │ 1. Run /guard — rate limiting │ │ 2. Run /evaluate — adversarial tests│ └─────────────────────────────────────┘
Recap Rules
- Be concise — this is a 30-second read, not a report
- Lead with the "PICK UP HERE" section — that's what the user needs
- If the session ended with open issues, highlight them
- Reference specific files and commands, not vague summaries
Recap Checklist
- [ ] Most recent session identified
- [ ] Commands and outcomes summarized in one line each
- [ ] "Pick up here" section has specific, actionable next steps
- [ ] Open issues from last session surfaced
Recommended Next Step
After recapping, run the first command listed in "Pick Up Here" to continue where you left off.
**NEVER**:
- Dump the entire session file — summarize it
- Recap without checking decisions.jsonl for recent activity
- Give vague next steps ("continue working") — be specific
- Assume context from the current conversation — only use persisted data
Workflow fluency for AI coding agents. 1 core skill · 25 commands · 7 domain references · memory layer · audit trail — works across Cursor, Claude Code, Gemini CLI, Copilot, and 6 more.
Repo: sharpdeveye/maestro
Other skills on maestro.
- /accelerate
Use when the workflow is too slow, too expensive, or both and needs latency, cost, or token usage optimization.
Open skill - /adapt-workflow
Use when porting a workflow to a different AI provider, deployment environment, model tier, or organizational context.
Open skill - /agent-workflow
Use when any Maestro command is invoked — provides foundational workflow design principles across prompt engineering, context management, tool orchestration, agent architecture, feedback loops, knowledge systems, and guardrails.
Open skill - /amplify
Use when the workflow works but needs to handle more complex cases or produce higher-quality output through better tools, context, prompts, or models.
Open skill - /calibrate
Use when workflow components are inconsistent, naming conventions vary, or a new team member's work needs alignment to project standards.
Open skill - /capture
Capture a session summary — what was done, what decisions were made, and what to do next.
Open skill