skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
product-on-purpose/pm-skills60 installs

wrap-session

End-of-session documentation workflow that updates README, CHANGELOG, agent context files, and creates session logs. Use when wrapping up a working session, when asked to document session progress, when preparing handoff documentation, or when the user says "wrap up", "end session", "document progress", or "save session".

How do I install this agent skill?

npx skills add https://github.com/product-on-purpose/pm-skills --skill wrap-session
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The wrap-session skill automates project documentation and session logging by updating files like README.md and CHANGELOG.md and creating agent context summaries. While the skill is intended for productivity and contains no malicious code or network operations, it possesses a vulnerability to indirect prompt injection. This occurs because the skill summarizes conversation history and project files—which are untrusted sources—into session logs and future prompts. A malicious actor could inject hidden instructions into these sources that the agent might unknowingly follow in subsequent sessions.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

  • Runlayerpass

    5 files scanned · No issues

  • ZeroLeakspass

    Score: 93/100 · 2 sections analyzed

What does this agent skill do?

Session 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/files
  • Changed — Modified functionality
  • Fixed — Bug fixes
  • Deprecated — Soon-to-be removed
  • Removed — Deleted features
  • Security — 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/):

FilePurposeWhen to Update
CONTEXT.mdCurrent project stateAlways
TODO.mdTask trackingWhen tasks change
DECISIONS.mdTechnical decisionsWhen decisions are made

If AGENTS folder doesn't exist: Create the full structure:

AGENTS/
└── claude/
    ├── 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:

  1. Summary (2-3 sentences)
  2. Key accomplishments
  3. Decisions made
  4. Issues encountered
  5. Next session recommendations
  6. Next session prompt (copy-paste ready prompt for continuing work)
  7. 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/
        ├── 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

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/product-on-purpose/pm-skills/wrap-session">View wrap-session on skillZs</a>