Menu
Capture session learnings before ending work. Use when user says goodbye, is done for the day, or explicitly asks to save session context.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Merge PR and move Cortex task to done
Create PR and move Cortex task to review
Start working on a task - creates branch, enters worktree and moves to progress
Start a brainstorming session to explore ideas before committing to a plan. Use when the solution isn't clear, there are multiple approaches, or you need to explore trade-offs.
Use this skill for ALL coding work. Enforces task tracking, memory usage, and proper workflow using Cortex MCP tools. MUST be used when implementing features, fixing bugs, or any development work.
Execute the 3-agent workflow (research → implement → verify) for coding tasks. Use for ALL feature implementations, bug fixes, and code changes. Spawns autonomous agents that research, implement, and verify changes.
| name | session-end |
| description | Capture session learnings before ending work. Use when user says goodbye, is done for the day, or explicitly asks to save session context. |
| argument-hint | ["optional task-id"] |
| user-invocable | true |
| allowed-tools | Bash(cx:*) |
Before ending this session, let's capture what was learned.
!cx ls -s progress 2>/dev/null | head -5
Based on the work done in this session, I'll create a diary entry:
Task: [Summary of what was worked on]
Work Done:
- [Main accomplishments]
Design Decisions:
- [Key technical decisions made]
Challenges:
- [Problems encountered]
Solutions:
- [How challenges were solved]
Lessons Learned:
- [Key takeaways for future sessions]
Preferences:
- [User preferences observed]
After filling the template, run:
echo "Task: ...
Work Done:
- ...
Design Decisions:
- ...
Lessons Learned:
- ..." | cx memory diary --task CX-N
After creating the diary:
Check if patterns are emerging:
cx memory reflect
If strong patterns exist, generate rules:
cx memory rules --min-strength pattern
For a quick capture without full template:
echo "Task: [brief summary]
Lessons Learned:
- [main takeaway]" | cx memory diary