About quick-recap
Quick Recap is a skill that makes completed work and pending follow-up explicit at the end of each response. It defines a compact status block and rules for choosing its status.
Key features
- 01Append a status line after completed work
- 02Distinguish finished, pending, and blocked states
- 03Set status length and placement rules
- 04Guide installation through managed instruction files
Use cases
- 01Clarifying whether a task is complete
- 02Calling out a required follow-up step
- 03Reporting a blocker that needs user input
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/quick-recapin Claude Code to confirm it loaded.
Bundled filesREADME.md
Details
From the project READMEQuick Recap
Make completion state obvious at the end of every response.
Status Block
Every response that completes a unit of work must end with:
🟢 Actual concise status sentence
Rules:
- Keep the status line under 100 characters.
- Use
🟢when the requested work is finished. - Use
🟡when non-routine follow-up remains; name the pending item. - Use
🔴only when blocked on user input. - Put the status line at the very end of the response.
- Do not add
---, spacer lines, or any content after the status line.
Installer Behavior
This convention is only automatic when it is present in project or user
instructions. When installing this skill, prefer adding the managed
AGENTS.md / CLAUDE.md block unless the user opts out.
If you are following the convention manually, choose the status from the user's perspective: finished, pending a specific non-routine step, or blocked.
Examples
Finished work:
🟢 Updated quick recap docs with output examples
Non-routine follow-up remains:
🟡 Code updated, set PROVIDER_WEBHOOK_SECRET before testing webhooks
Blocked on user input:
🔴 Need the production API key to continue