plan-protocol

Creates and manages structured implementation plans with citations and phase tracking.

1|Updated Jul 23, 2026
One-click install
npx skills add https://github.com/sanjanb/my-agent-harness --skill plan-protocol-sanjanb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-protocol
Source: https://github.com/sanjanb/my-agent-harness/tree/main/skills/plan-protocol
Command: npx skills add https://github.com/sanjanb/my-agent-harness --skill plan-protocol-sanjanb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Multi-step implementations often lose track of progress, decisions, and the research behind them. This Skill enforces a consistent markdown plan format with YAML frontmatter, phase status markers, and citations so plans stay accurate and auditable across sessions. ## Core Features & Use Cases - Standardized Plan Format: Defines an exact markdown template with frontmatter (status, phase, updated), a Goal section, a Context & Decisions table, and hierarchically numbered tasks. - State Machine Rules: Enforces lifecycle rules so only one phase is IN PROGRESS and only one task carries the CURRENT marker at any time. - Research Citations: Links architectural decisions and tasks to delegation research via ref:delegation-id references, with validation against fabricated citations. - Use Case: When starting a JWT authentication feature, create a plan that cites prior auth research, tracks phases from research through testing, and keeps exactly one current task marked as work progresses. ## Quick Start Ask the agent to create an implementation plan for your multi-step feature using the plan protocol format with phases, citations, and a current task marker.

Frequently Asked Questions about plan-protocol

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

FAQPage Schema
How do I create an implementation plan with phases and task tracking?

Use the plan_save tool with the defined markdown format: YAML frontmatter with status, phase, and updated fields, a one-sentence Goal section, phases marked [PENDING], [IN PROGRESS], or [COMPLETE], and hierarchically numbered tasks like 1.1 and 2.1.

How do I cite research in an implementation plan?

Cite research using the ref:delegation-id format, where the ID comes from a completed delegation such as ref:swift-amber-falcon. Add citations to the Context & Decisions table, append them to task lines, or include them inline in Notes.

When should I use a structured plan instead of simple todos?

Use a structured plan for multi-step implementations, complex requests, and work spanning multiple phases. Skip it for simple one-off tasks, pure research, quick fixes, or single-file changes, where built-in todos are sufficient.

Why does my plan fail validation with multiple CURRENT markers?

The protocol allows exactly one task marked with the CURRENT arrow at any time. Remove the marker from all tasks except the one actively being worked on, and move it immediately when starting a new task.

What are the limitations of this planning approach?

The format requires citations from actual delegations, so decisions without prior research cannot be cited and fabricated IDs are prohibited. It also adds overhead unsuited to trivial tasks that do not need phase tracking.