plan-protocol

Create structured implementation plans with frontmatter and a traceable decision log.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/Xerrion/opencode --skill plan-protocol-xerrion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-protocol
Source: https://github.com/Xerrion/opencode/tree/main/skills/plan-protocol
Command: npx skills add https://github.com/Xerrion/opencode --skill plan-protocol-xerrion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan protocol provides a standardized framework for creating and maintaining implementation plans, ensuring decisions are traceable and plans stay up-to-date.

Core Features & Use Cases

  • Frontmatter-driven planning: mandates status, phase, and updated fields and enables traceable planning logs.
  • Context & Decisions with citations: supports a structured table of decisions and cited sources (e.g., ref: delegation-id) to back architectural or process choices.
  • Phase-driven task tracking: organizes work into phases with status markers ([COMPLETE], [IN PROGRESS], [PENDING]), supports hierarchical task numbering, and enforces a single active current task.
  • Usage scenarios: ideal for multi-step implementations, complex user requests, and research-informed project planning.

Quick Start

Load this skill and begin a new Implementation Plan using the Plan Format template, including status, phase, updated, and a Context & Decisions log.

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 citations for a multi-phase project?

To create an implementation plan with citations, use a structured format with frontmatter for status and phase tracking, plus a decision log linking cited sources to architectural choices for multi-phase projects.

What is phase-based task tracking with a single active current task?

Phase-based task tracking organizes work into phases with explicit status markers like COMPLETE or IN PROGRESS, enforcing a single active current task to maintain focus during complex project execution.

How do I maintain traceable decisions and planning logs for complex projects?

Maintain traceable decisions by using frontmatter with updated fields and a context table that records decisions with cited sources, ensuring architectural choices are backed by formal planning logs.

When do I need structured planning guidelines with hierarchical task numbering?

Structured planning guidelines with hierarchical task numbering are needed for multi-step implementations and complex user requests that require formal notes and phase markers across planning, execution, and review.

Can I use this structured planning format for research-informed project planning?

Yes, this format supports research-informed project planning by requiring citations for research-based decisions, backing architectural and process choices with referenced sources throughout the phases.

What are the limitations of enforcing a single current task in project management?

Enforcing a single current task prevents parallel task execution, limiting workflows that require multiple active tasks simultaneously but ensuring strict focus and traceable progress in structured plans.