wrap-up

Create session journeys, consolidate notes, and evolve SKILL.md definitions.

4|2|Updated Oct 26, 2025
One-click install
npx skills add https://github.com/nomos-guild/cgov --skill wrap-up
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wrap-up
Source: https://github.com/nomos-guild/cgov/tree/main/.claude/skills/wrap-up
Command: npx skills add https://github.com/nomos-guild/cgov --skill wrap-up

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates end-of-session tasks by creating a journey, consolidating notes, and evolving related skills.

Core Features & Use Cases

  • Automatically creates a journey at .claude/journeys/{date}-{slug}.md documenting the session's changes and learnings.
  • Consolidates inline learning notes into a cohesive narrative, preserving patterns and decisions.
  • Triggers skill evolution updates by comparing journey learnings against existing SKILL.md definitions.
  • Supports cross-pollination of patterns by updating shared pattern repositories and docs.
  • Prunes stale content to keep the knowledge base fresh and relevant.

Quick Start

Use the wrap-up command to summarize a session and generate its journey. Example: /wrap-up Page Margins Feature

Frequently Asked Questions about wrap-up

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate end-of-session notes consolidation and skill evolution?

Automate end-of-session tasks by using a wrap-up command that creates a journey document at .claude/journeys/{date}-{slug}.md, consolidates inline learning notes into a cohesive narrative, and triggers skill evolution updates by comparing learnings against existing SKILL.md definitions.

What is the best way to document session changes and learning moments automatically?

The best way to document session changes automatically is by generating a journey file at .claude/journeys/{date}-{slug}.md that captures changes and learnings, prunes stale content, and cross-pollinates patterns by updating shared pattern repositories.

Do I need frontmatter-driven SKILL.md definitions to trigger skill evolution updates?

Yes, triggering skill evolution updates relies on frontmatter-driven SKILL.md definitions to compare journey learnings against existing skill definitions and document evolutions accurately during the session wrap-up.

How do I consolidate inline learning notes into a cohesive narrative?

You consolidate inline learning notes into a cohesive narrative by running the wrap-up automation, which extracts in-session outputs, preserves patterns and decisions, and prunes stale content to keep the knowledge base fresh.

Can I use wrap-up automation for sessions without any code changes?

Wrap-up automation scope specifically covers sessions with changes and learning moments, so sessions without changes may not generate meaningful journey files or trigger skill evolution updates effectively.

How does wrap-up automation keep the knowledge base fresh and relevant?

Wrap-up automation keeps the knowledge base fresh by pruning stale content, updating shared pattern repositories, cross-pollinating patterns across docs, and consolidating new learning notes into journey files.