pavilio-handoff

Creates prebaked handoff files delegating tasks for later execution via pavilio-resume.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When you want to delegate a task for execution in a fresh session without going through the full briefing and prioritization pipeline, you need a lightweight way to capture the goal, context, and coarse todos into a reusable handoff file. ## Core Features & Use Cases - Prebaked Handoff Generation: Converts a task description into a structured handoff markdown file with Goal, Context, Todo, and Session log sections. - Fixed Read Budget: Reads only the latest progress file and the active openspec change directory, turning unknowns into discover-todo items instead of deep research. - Briefing Registration: Registers the handoff in the project's BRIEFING.md under a Handoffs section, creating a minimal stub if missing. - Use Case: You have a feature idea for a project but no time to work on it now. Run the handoff command with the project name and task description, confirm the draft, and later resume execution in a fresh session with /pavilio-resume. ## Quick Start Ask the agent to hand off a task by running /pavilio-handoff with your project name and a short task description, then confirm the draft it shows you.

Frequently Asked Questions about pavilio-handoff

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

FAQPage Schema
How do I delegate a task for a later AI agent session?▼

Run /pavilio-handoff with the project name and a task description. The skill drafts a handoff file with goal, context, and coarse todos, shows it for confirmation, then writes it to the project's progress directory for later execution via /pavilio-resume.

What is the difference between pavilio-handoff and pavilio-manager?▼

pavilio-handoff skips the briefing and prioritization pipeline entirely, creating a prebaked handoff directly from your task description. Prioritization and briefing remain the responsibility of pavilio-manager and are explicit non-goals of this skill.

Does pavilio-handoff execute or research the task?▼

No, it only delegates. It uses a fixed read budget of the latest progress file and the active openspec change directory, converting unknowns into discover-todo items rather than performing deep research or executing any part of the task.

Can pavilio-handoff create Todoist tasks automatically?▼

No, it never creates Todoist tasks. It only links an existing high-level Todoist task id or URL if you mention one in the task description; otherwise the Todoist field is recorded as none.

What happens if the project BRIEFING.md file is missing?▼

The skill creates a minimal stub containing a BRIEFING heading and a Handoffs section, then registers the new handoff entry there. It never modifies the root-level BRIEFING.md file.