pavilio-compact

Distills remaining session work into a handoff markdown file for a fresh session.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/gmotyl/pavilio --skill pavilio-compact-gmotyl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pavilio-compact
Source: https://github.com/gmotyl/pavilio/tree/main/skills/pavilio-compact
Command: npx skills add https://github.com/gmotyl/pavilio --skill pavilio-compact-gmotyl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long AI coding sessions lose context when they end or hit context limits, forcing you to re-explain goals, file pointers, and next steps. This Skill packages the remaining work from the current conversation into a structured handoff file that a new session can pick up directly. ## Core Features & Use Cases - Session distillation: Extracts the goal, context file pointers, and concrete todos from the live conversation plus today's progress file, without re-scanning the repository. - Standardized handoff format: Writes a markdown handoff with Goal, Context, Todo, and Session log sections to projects/<proj>/progress/<date>-<slug>.md. - Briefing registration: Registers the handoff in the project's BRIEFING.md under a Handoffs section so pending work stays discoverable. - Use Case: You are mid-feature in a long session and want to continue tomorrow in a fresh context. Run /pavilio-compact myproject, confirm the draft, and tomorrow run /pavilio-resume on the generated file to continue exactly where you left off. ## Quick Start Ask the AI to run /pavilio-compact for your project to package the current session's remaining work into a handoff file.

Frequently Asked Questions about pavilio-compact

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

FAQPage Schema
How do I hand off an AI coding session to a new session?▼

Run /pavilio-compact with your project name to distill the remaining goal, context pointers, and todos into a handoff markdown file. Then start a fresh session and run /pavilio-resume on that file to continue the work.

What information goes into a session handoff file?▼

The handoff contains a one-paragraph goal, context file pointers for load-bearing files, a checklist of concrete next steps, and a session log section. Completed work stays in the progress file; only unfinished work is carried over.

Does pavilio-compact commit or close the session?▼

No, it only writes the handoff file and registers it in the project's BRIEFING.md. Committing progress and closing the session remain separate steps handled by /pavilio-session-end.

Where are handoff files stored in the project?▼

Handoffs are written to projects/<project>/progress/<date>-<slug>.md and listed under the Handoffs section of that project's progress/BRIEFING.md. The root BRIEFING.md is never modified.

When should I not use session compaction?▼

Skip it when the session's work is fully complete, since done work belongs in the progress file rather than a handoff. It also does not create Todoist tasks or perform prioritization, so use dedicated planning skills for that.