plan-protocol

Standardizes implementation planning with frontmatter, citations, and hierarchical tasks.

3|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/opzero1/op1 --skill plan-protocol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-protocol
Source: https://github.com/opzero1/op1/tree/main/packages/install/templates/skill/plan-protocol
Command: npx skills add https://github.com/opzero1/op1 --skill plan-protocol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes implementation planning with a focus on traceable decisions and properly cited research to ensure alignment across teams.

Core Features & Use Cases

  • Plan templates: Provides a repeatable structure for creating implementation plans with frontmatter, goals, and phase definitions.
  • Citations & decisions: Enforces ref: citations in the Context & Decisions table to link research to decisions.
  • Phase-driven tracking: Supports multiple phases with status markers and hierarchical tasks, enabling clear progress tracking.

Quick Start

Load the plan-protocol skill and begin a new plan using the recommended format, then save with plan_save including status, phase, and updated fields.

Frequently Asked Questions about plan-protocol

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

FAQPage Schema
How do I create implementation plans with traceable decisions and citations?

To create implementation plans with traceable decisions, you load the planning protocol and structure your document with frontmatter fields, a one-sentence Goal, a Context & Decisions table using ref: citations, and hierarchical tasks to standardize project tracking.

What is the best way to standardize multi-phase project planning documentation?

The best way to standardize multi-phase project planning documentation is enforcing a repeatable template with frontmatter status and phase markers, research-backed decision tables, and a single CURRENT task to ensure clear progress tracking across teams.

How do I link research citations to project decisions in my planning documentation?

You link research citations to project decisions by using the Context & Decisions table within your plan, applying enforced ref: citations to connect research sources directly to your implementation choices.

Can I track hierarchical tasks across multiple project phases in a single plan?

Yes, you can track hierarchical tasks across multiple project phases in a single plan by utilizing phase-driven status markers and designating a single CURRENT task to maintain clear progress tracking.

Does implementation planning work without prior research data?

Implementation planning requires research data because the protocol enforces ref: citations in the Context & Decisions table to link research to decisions, ensuring traceable choices across project phases.

Why does my project plan require a single CURRENT task field?

Your project plan requires a single CURRENT task field because the protocol enforces hierarchical tasks with a single active focus point, enabling clear progress tracking across multiple phases and updated frontmatter fields.