Creates a detailed summary of the conversation chunk for continuing work in future sessions.
Creates detailed conversation summaries with technical context for seamless session continuation.
/plugin marketplace add DeevsDeevs/agent-system/plugin install chain-system@deevs-agent-systemCreates a detailed summary of the conversation chunk for continuing work in future sessions.
Chain name: $ARGUMENTS
If no chain name provided, ask the user for one.
Create a thorough summary capturing technical details, code patterns, architectural decisions, unresolved bugs, and solutions attempted. This enables seamless continuation without losing context.
Before your final summary, wrap analysis in <analysis> tags to organize thoughts. Chronologically analyze each message, identifying:
Your summary should include:
Create a slug (e.g., implement-auth-handler) and readable summary (e.g., "Implement Auth Handler")
# Readable Summary
<analysis>
[Your thorough chronological analysis for organizing thoughts - not saved to file]
</analysis>
<plan>
# Chain Link Summary
## 1. Primary Request and Intent
[Detailed description of all user requests]
## 2. Key Technical Concepts
- [Technology/framework/pattern 1]
- [Technology/framework/pattern 2]
## 3. Work Completed
- [Completed item 1] - status: working/tested
- [Completed item 2] - status: working/tested
## 4. Decisions and Rationale
- **Decision**: [What was chosen]
- **Rationale**: [Why this approach over alternatives]
## 5. Files and Code Changes
### Created: [Full/Path/To/NewFile.ext]
- **Purpose**: [Why created]
- **Code**:
```language
[Complete file content]
[Before/after snippets]
[Complete error message/stack trace]
[Skip if no unresolved issues]
[What was in progress, with files and code]
[Immediate next action] </plan>
## Final Step
Create directory and save file:
1. Create directory: `mkdir -p .claude/chains/[chain-name]` (substitute actual chain name)
2. Generate timestamp using local time: `date '+%Y-%m-%d-%H%M'` (e.g., `2025-11-24-0230`)
3. Write to: `.claude/chains/[chain-name]/[timestamp]-[slug].md`
4. Save only the content inside `<plan>` tags to the file
5. Inform user: file path and how to load with `/chain-load [chain-name]`