plan-protocol

Generate implementation plans with frontmatter, citations, and phased tasks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan protocols provide a structured approach to producing implementation plans that are clear, evidence-backed, and easy to audit.

Core Features & Use Cases

  • Structured frontmatter: Enforces status, phase, and updated fields for reliable planning.
  • Context & Decisions table: Captures rationale and sources for architectural or workflow decisions.
  • Phased execution: Defines tasks in numbered phases with progress markers and a single current task.

Quick Start

Create a new implementation plan using this framework and include frontmatter, a one-sentence goal, a context & decisions table with citations, and phased tasks.

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, define a one-sentence goal, a Context & Decisions table with sources, and phased tasks. This enforces frontmatter validation to ensure your multi-phase project is evidence-backed and auditable.

What is a citation-backed plan protocol and when do I need one?

A citation-backed plan protocol structures implementation plans with goals, context, decisions, and phased tasks. You need one for multi-phase projects across teams requiring traceable, evidence-backed governance and clear architectural rationale.

How do I structure project management tasks across multiple phases?

Structure project management tasks by defining them in numbered phases with strict progress markers. This approach designates a single current task per phase, ensuring clear milestones and traceable execution across multi-phase projects.

Does this planning protocol work for multi-team project governance?

Yes, this planning protocol works for multi-team project governance by enforcing structured frontmatter with status and phase fields. It captures decisions and rationale in a dedicated table, providing the traceability needed for cross-team coordination.

Why does my implementation plan need a Context & Decisions table?

Your implementation plan needs a Context & Decisions table to capture the rationale and sources for architectural or workflow decisions. This ensures your project governance remains evidence-backed, easy to audit, and clearly traceable.

What's the best way to enforce frontmatter validation in project documentation?

The best way to enforce frontmatter validation in project documentation is using a plan protocol that mandates status, phase, and updated fields. This ensures reliable planning and consistent documentation across all implementation phases.