task-plan

Create standardized plan.md handoff documents for multi-step tasks.

Updated Mar 2, 2026
One-click install
npx skills add https://github.com/maestria-co/ai-playbook --skill task-plan-maestria-co
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-plan
Source: https://github.com/maestria-co/ai-playbook/tree/main/skills/task-plan
Command: npx skills add https://github.com/maestria-co/ai-playbook --skill task-plan-maestria-co

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Canonical, reusable plan documents that ensure any agent can resume work after interruptions by providing a standardized structure and context.

Core Features & Use Cases

  • Canonical plan.md format stored at .context/tasks/[TASK-ID]/plan.md, including sections like Objective, Acceptance Criteria, Decisions, Key Files, Task Breakdown, Progress Log, and Blockers to guide handoffs.
  • Supports multi-session tasks, refactors, design reviews, and investigations by preserving decisions and context across agents.
  • Provides a Cold Resume Protocol to help a new agent pick up where the previous one left off with minimal rereading.

Quick Start

Create a new plan at .context/tasks/[TASK-ID]/plan.md following the canonical format.

Frequently Asked Questions about task-plan

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

FAQPage Schema
How do I create a standardized task handoff document for multi-session work?

A standardized task handoff document is created as a plan.md file stored at .context/tasks/[TASK-ID]/plan.md, enforcing sections like Objectives, Acceptance Criteria, Key Files, Task Breakdown, Progress Log, and Blockers to ensure seamless work continuity across sessions.

What is the best way to preserve context and decisions for refactors spanning multiple agents?

Preserving context for refactors across multiple agents requires a canonical plan.md format that captures Decisions, Key Files, and Progress Log sections, ensuring any agent can resume work after interruptions with minimal rereading via a Cold Resume Protocol.

How does a Cold Resume Protocol help a new agent pick up an interrupted investigation?

A Cold Resume Protocol helps a new agent pick up an interrupted investigation by providing a standardized plan.md document with structured sections like Objectives, Acceptance Criteria, and Blockers, enabling quick context recovery with minimal rereading.

Can I use a plan.md workflow for design reviews and multi-step task coordination?

Yes, the plan.md workflow applies to design reviews, refactors, investigations, and multi-step task coordination by generating a standardized handoff document that captures objectives, acceptance criteria, decisions, and progress across sessions.

What sections should a task handoff plan include for seamless work continuity?

A task handoff plan should include Objectives, Acceptance Criteria, Decisions, Key Files, Task Breakdown, Progress Log, and Blockers sections to provide canonical, reusable context that ensures any agent can resume work seamlessly.

When do I need a standardized plan document for multi-step task workflows?

A standardized plan document is needed for multi-step task workflows spanning multiple sessions or requiring coordination across agents, ensuring canonical context and decisions are preserved at .context/tasks/[TASK-ID]/plan.md for seamless resumption.