skills.rest
gmotyl
gmotylCOMMUNITY
Explore all skills by this author →
Website𝕏@gmotylGitHub

pavilio-resume

Executes a prebaked handoff file by working its todo list and logging progress in place.

Updated Apr 19, 2026
Search Tags:#workflow#ai agent#progress tracking#handoff#task delegation#session resume#todo execution
One-click install
npx skills add https://github.com/gmotyl/pavilio --skill pavilio-resume-gmotyl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pavilio-resume
Source: https://github.com/gmotyl/pavilio/tree/main/skills/pavilio-resume
Command: npx skills add https://github.com/gmotyl/pavilio --skill pavilio-resume-gmotyl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a task is handed off between AI agent sessions, context is lost and the executing agent wastes effort re-scanning project history. This Skill lets an agent pick up a prebaked handoff file and execute it directly, reading only what the handoff points at. ## Core Features & Use Cases - Handoff execution: Reads a handoff file produced by /pavilio-manager or /pavilio-handoff and works its todo list top-down, checking items off as they complete. - In-place session logging: Appends decisions, findings, and next steps to the handoff file's Session log instead of creating separate progress files. - Completion bookkeeping: Marks the handoff done in BRIEFING.md and suggests closing the linked Todoist task when the goal is finished. - Use Case: A manager agent prebakes projects/api/progress/2026-05-01-auth-refactor.md; you run /pavilio-resume on that path and the agent executes the todos without re-planning. ## Quick Start Run /pavilio-resume with the path to a handoff file, for example projects/<proj>/progress/<date>-<slug>.md, to execute its todo list.

Frequently Asked Questions about pavilio-resume

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

FAQPage Schema
How do I resume a handed-off AI agent task?▼

Run /pavilio-resume with the handoff file path relative to the workspace repo root, such as projects/<proj>/progress/<date>-<slug>.md. The agent reads only that file and its referenced context, then works the todo list top-down.

What is the difference between /pavilio-resume and /pavilio-session-start?▼

/pavilio-resume executes a specific prebaked handoff file and requires an explicit file path. A bare "resume" or "resume work on X" belongs to /pavilio-session-start, which handles general session startup and project selection.

What happens if the handoff file path has a repeated projects segment?▼

The workspace repo root is itself named projects, so paths like projects/<proj>/... can legitimately repeat the segment. Resolve the path exactly as written and retry against the repeated-segment path before declaring the file missing.

When should I not use /pavilio-resume?▼

Do not use it without an explicit handoff file, or when a todo requires real design work. In those cases use /pavilio-session-start with pavilio-grill for collaborative design instead of expanding scope silently.

Does /pavilio-resume create separate progress files or Todoist tasks?▼

No. The handoff file itself is the session progress file; the agent appends to its Session log. It never creates Todoist tasks and only checks off its own handoff entry in BRIEFING.md.

Related Skills

Explore More Software Engineering Skills→
podcodarpodcodar
7

project-files

Manage shared PLAN, TODO, SPEC, and SESSION files for multi-agent coordination.

Official
Intermediate
KibertumKibertum
16

ship

Automate task review, testing, and commit for repository closure.

Official
Advanced
EhsaanArkEhsaanArk

plan-ceo-review

Coordinate a CEO-level review of project plans to surface risks and scope gaps.

Community
Advanced
fluxforgeaifluxforgeai
3

session-start

Load CLAUDE.md and handoff documents to initialize a new session.

Community
Advanced