Cross-Reference Intelligence
The wrapup connects data across multiple sources:
- Git commits matched with note checkboxes
- Decisions linked to code changes
- Bugs correlated with files modified
- Loop state integrated with task progress
This cross-referencing creates a complete picture of your session.
Output Sections
| Section | Description | Required |
|---|---|---|
| Done | Completed work with evidence | Yes |
| Decisions | Technical decisions made this session | If any |
| Changed | Key files and code areas modified | Yes |
| Open | Unfinished work and remaining items | If any |
| Risks | Real identified risks | If any |
| Next | Specific actionable next steps | Mandatory |
The “Next” Section
This is the most important section. It must be:
- Specific: “Add refresh token logic in
src/auth.ts:45” not “Continue auth work” - Actionable: A fresh session reading only “Next” should know exactly what to do
- File-referenced: Include
file:linereferences where possible
Quality bar: “What file, what function, what’s left to do?”
Risk Detection
The Risks section flags real issues:
- Uncommitted changes that might be lost
- Blocked tasks from the task loop
- Failing tests discovered during the session
- Merge conflicts pending resolution
Generic warnings are excluded — only concrete, session-specific risks.
Auto-Replace
One wrapup per session. New /note-wrapup replaces the previous one. This keeps your notes clean — always the latest summary.
When to Use
Run /note-wrapup at the end of a work session, before:
- Switching to a different project
- Taking a break
- Handing off to a teammate
- Ending the day