wrap-session
Scannednpx machina-cli add skill product-on-purpose/pm-skills/wrap-session --openclawSession Wrap-Up Workflow
Execute this workflow when ending a working session to maintain project continuity.
Execution Steps
1. Identify Project Root
Locate the project root containing README.md and CHANGELOG.md. If uncertain, ask the user.
2. Update README.md
Update the project description and status to reflect current state. Keep changes minimal — only update what has meaningfully changed.
3. Update CHANGELOG.md
Append changes to the [Unreleased] section using Keep a Changelog format. See references/changelog-format.md for format details.
Change categories:
Added— New features/filesChanged— Modified functionalityFixed— Bug fixesDeprecated— Soon-to-be removedRemoved— Deleted featuresSecurity— Vulnerability fixes
If CHANGELOG.md doesn't exist, create it using assets/CHANGELOG.template.md.
4. Update Agent Context Files
Create/update files in AGENTS/<model>/ (e.g., AGENTS/claude-opus-4.5/):
| File | Purpose | When to Update |
|---|---|---|
CONTEXT.md | Current project state | Always |
TODO.md | Task tracking | When tasks change |
DECISIONS.md | Technical decisions | When decisions are made |
If AGENTS folder doesn't exist: Create the full structure:
AGENTS/
└── claude-opus-4.5/
├── CONTEXT.md
├── TODO.md
├── DECISIONS.md
├── SESSION-LOG/
└── PLANNING/
See references/context-files.md for file formats.
4b. Save Planning Artifacts (When Applicable)
If the session involved planning, review, or analysis work that produced artifacts requiring review, save them to AGENTS/<model>/PLANNING/:
When to create PLANNING documents:
- Architecture proposals or design documents
- Code review summaries and recommendations
- Investigation reports and research findings
- Implementation plans and roadmaps
File naming:
- Use descriptive, kebab-case names:
auth-system-design.md,api-migration-plan.md - Prefix with date for time-sensitive docs:
2025-01-14_performance-analysis.md
Required front matter:
---
created: YYYY-MM-DD
updated: YYYY-MM-DD
sessions:
- SESSION-LOG/YYYY-MM-DD_HH-MM_session.md
status: draft | in-review | approved | superseded
tags: [planning, review, analysis]
---
5. Create Session Log
Create AGENTS/<model>/SESSION-LOG/YYYY-MM-DD_HH-MM_session-<4-6 word summary separated by hypens>.md with:
- Summary (2-3 sentences)
- Key accomplishments
- Decisions made
- Issues encountered
- Next session recommendations
- Next session prompt (copy-paste ready prompt for continuing work)
- Session highlights (key prompts/responses, not full transcript)
See references/session-log-format.md for template.
6. Confirm Completion
Report to user:
- Files updated/created
- Key changes documented
- Recommended pickup point for next session
Directory Structure
project-root/
├── README.md
├── CHANGELOG.md
└── AGENTS/
└── claude-opus-4.5/
├── CONTEXT.md
├── TODO.md
├── DECISIONS.md
├── SESSION-LOG/
│ └── YYYY-MM-DD_HH-MM_session.md
└── PLANNING/
└── <descriptive-name>.md
When NOT to Run
- No meaningful work was done
- User explicitly declines documentation
- Project is temporary/throwaway
Source
git clone https://github.com/product-on-purpose/pm-skills/blob/main/.claude/skills/wrap-session/SKILL.mdView on GitHub Overview
Wrap up a working session by updating key project docs, agent context files, and creating a session log. This maintains continuity, enables handoffs, and captures progress for future work.
How This Skill Works
When invoked, the workflow locates the project root, refreshes README.md and CHANGELOG.md with meaningful state changes, and creates/updates agent context files under AGENTS/<model>/ (CONTEXT.md, TODO.md, DECISIONS.md). If planning artifacts exist, it saves them to PLANNING/, and always generates a SESSION-LOG with a structured summary. It ends by reporting what was updated and what to tackle next.
When to Use It
- Wrapping up a working session to preserve progress
- Documenting session progress for teammates or stakeholders
- Preparing handoff documentation to another agent or human
- Saving planning artifacts and decisions after analysis
- User explicitly asking to wrap up, end session, or document progress
Quick Start
- Step 1: Identify project root; confirm README.md and CHANGELOG.md locations
- Step 2: Update README.md with current state; keep changes minimal and meaningful
- Step 3: Create or update AGENTS/<model>/ files; generate SESSION-LOG and save planning artifacts if applicable
Best Practices
- Identify the project root early; ask the user if unsure
- Keep README updates minimal and meaningful, reflecting actual changes
- Append to CHANGELOG.md using Keep a Changelog format and proper categories
- Create the AGENTS/<model>/ structure if it doesn’t exist and populate CONTEXT.md, TODO.md, DECISIONS.md
- Use descriptive, kebab-case names for planning artifacts and include front matter
Example Use Cases
- A developer finishes a feature and runs wrap-session to update the project README, append CHANGELOG with a Added feature, and generate a SESSION-LOG capturing implementation notes
- A researcher ends a design sprint; wrap-session saves architecture notes to PLANNING and creates a session log for handoff
- An engineer documents refactor progress, updates CONTEXT.md, and records decisions in DECISIONS.md for the next engineer
- A debugging session concludes; wrap-session records issues encountered and next steps in SESSION-LOG
- A team lead wraps up a review session and shares handoff prompts for the next contributor