summary

Summary Skill

Purpose

Summarize every change made and provide it clearly to the primary agent and user. Also provide compact summaries for session continuity when token limits are reached.

Format

• •Plain text format (NOT markdown files)
• •Do NOT create a new markdown file in docs/
• •This is for communication only, not file creation

Standard Summary Structure

A good summary includes:

1. •

   What was done

   • •Brief description of the task completed
   • •High-level overview of changes
2. •

   Files changed

   • •List of files created
   • •List of files modified
   • •List of files deleted
3. •

   Dependencies added

   • •New npm packages
   • •New Python packages
   • •Other dependencies
4. •

   Configuration changes

   • •Environment variables added
   • •Config file modifications
5. •

   Issues encountered

   • •Problems found during implementation
   • •How they were resolved
6. •

   Remaining tasks (if any)

   • •What still needs to be done
   • •Any blockers or dependencies

Example Standard Summary

Completed user authentication implementation.

Files created:
- src/auth/service.ts - Authentication service
- src/auth/middleware.ts - Auth middleware
- src/routes/auth.ts - Auth routes

Files modified:
- package.json - Added jsonwebtoken, bcrypt
- src/app.ts - Added auth routes

Dependencies added:
- jsonwebtoken@9.0.0
- bcrypt@5.1.0
- @types/jsonwebtoken@9.0.0
- @types/bcrypt@5.0.0

Environment variables required:
- JWT_SECRET - Secret key for token signing

No issues encountered.

Remaining: Need to add password reset functionality.

CRITICAL: Compact Summary for Session Continuity

When to Provide Compact Summary

ALWAYS provide a compact summary when:

• •Your session is about to end due to token limits
• •You've completed significant work and need to hand off to a new session
• •The orchestrator requests a summary for session continuity

Compact Summary Format

## Session Compact Summary

### Completed Tasks:
- [Task 1]: [Brief description] - [files affected]
- [Task 2]: [Brief description] - [files affected]

### Remaining Tasks:
1. [Priority 1]: [Task description]
2. [Priority 2]: [Task description]

### Current State:
- [Current state of implementation]
- [Any in-progress work]

### Critical Context:
- [Important decisions made]
- [Blockers or dependencies]
- [Configuration notes]

### Files Modified This Session:
- [path/to/file1] - [action taken]
- [path/to/file2] - [action taken]

### Next Steps for New Session:
1. [First action to take]
2. [Second action]
3. [Third action]

Why Compact Summary Matters

The orchestrator uses the compact summary to:

1. •Invoke a new super-coder session with proper context
2. •Pass the original user prompt + summary to the new session
3. •Ensure continuity of work without duplication
4. •Maintain understanding of what was completed and what remains

Session Handoff Protocol

When your session is ending:

1. •Stop current work at a logical breakpoint
2. •Provide the compact summary immediately
3. •Include ALL critical context needed for continuation
4. •List specific next steps in priority order

The orchestrator will:

1. •Receive your compact summary
2. •Create a new session with:
   • •Original user prompt
   • •Your compact summary
   • •Any image descriptions (if images were provided)
3. •The new session will continue from where you left off

Key Rules

1. •Always provide summary after completing work
2. •Keep it concise but complete
3. •Use plain text, not markdown files
4. •Include enough detail for understanding
5. •Highlight any issues or blockers
6. •CRITICAL: Provide compact summary before session ends due to token limits
7. •The compact summary enables seamless session handoff