Help us improve
Share bugs, ideas, or general feedback.
From shavakan-commands
Save conversation context before compaction (context.md, tasks.md)
npx claudepluginhub shavakan/claude-marketplace --plugin shavakan-commandsHow this command is triggered — by the user, by Claude, or both
Slash command
/shavakan-commands:docs-save-contextThe summary Claude sees in its command listing — used to decide when to auto-load this command
# Save Context - Pre-Compaction State Preservation Preserve current conversation state and decisions before approaching token limit or natural break point. ## Additional Instructions $ARGUMENTS --- ## Objective Preserve conversation state before compaction or natural break points. Extract decisions made, document current progress, update context files for continuity. **Use when:** - Approaching token limit (compaction warning) - Natural break point in complex work - Before switching contexts - After important architectural decisions --- ## Execution ### Phase 1: Analyze Current St...
/dev-docs-updateUpdates dev documentation before context compaction: task status, session context, unfinished work, handoff notes for seamless continuation.
/context-compactGenerates structured task summary with completed work, next steps, key files, branch, issue refs, and notes for context compaction near token limits.
/context-saveCompacts session or saves full handoff to .handoff/ file with progress summary, git state, and next steps when context pressure detected.
Share bugs, ideas, or general feedback.
Preserve current conversation state and decisions before approaching token limit or natural break point.
$ARGUMENTS
Preserve conversation state before compaction or natural break points. Extract decisions made, document current progress, update context files for continuity.
Use when:
Extract from conversation:
Decisions made - What was decided and why, trade-offs considered, alternatives rejected, rationale for approach
Current progress - What's completed, partially done, blocked (and why)
Next steps - Immediate next actions, dependencies to resolve, open questions
Check if feature context already exists in features/[task-name]/ directory.
Gate: Present summary of extracted state to user.
Present options based on whether context files exist:
Save context state?
□ Update existing - Append to features/[task-name]/ files
□ Create new - Start fresh context directory
□ Review first - Show extracted state before saving
□ Cancel
If creating new, ask for task name (kebab-case format).
Gate: User must confirm approach and provide task name if needed.
If updating existing:
If creating new:
features/[task-name]/ directoryNote: plan.md not needed for context saves (only for feature-plan command).
Gate: All files updated or created successfully.
Summarize what was saved: location of files, key decisions captured, tasks marked complete, next steps documented for resuming work
# [Feature Name] - Context
**Last Updated:** [timestamp]
## Current State
[Where we are in implementation - 2-3 sentences]
## Recent Decisions
### [Decision Title]
**What:** What was decided
**Why:** Rationale and trade-offs
**When:** [timestamp]
**Impact:** What this affects
## Key Files
- `path/to/file.ts` - Purpose and current state
- `path/to/another.ts` - What was changed
## Next Steps
[When resuming work, start here - specific actionable items]
## Open Questions
- Question that needs resolution
- Blocker or dependency
# [Feature Name] - Tasks
**Last Updated:** [timestamp]
## Completed
- [x] Task that was finished
- [x] Another completed task
## In Progress
- [ ] Task currently being worked on (50% done)
## Blocked
- [ ] Task blocked by X dependency
## Todo
- [ ] Next task to do
- [ ] Subsequent task
/shavakan-commands:docs-feature-plan - Create comprehensive feature plan from scratch/shavakan-commands:docs-update - Update existing context files