plan-conventions

Enforce frontmatter and lifecycle rules for plans under docs/plans/.

49|15|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/block/proto-fleet --skill plan-conventions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-conventions
Source: https://github.com/block/proto-fleet/tree/main/.claude/skills/plan-conventions
Command: npx skills add https://github.com/block/proto-fleet --skill plan-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides editors to enforce consistent plan documentation and governance for plans under docs/plans/.

Core Features & Use Cases

  • Frontmatter validation: requires title, date, status, and type for every plan.
  • Lifecycle enforcement: defines and enforces transitions through draft → proposed → accepted → implementing → completed or cancelled.
  • Use Case: teams standardize planning artifacts (TDDs, PRDs, lightweight plans) to improve traceability and review.

Quick Start

Create or update a plan file under docs/plans/ with frontmatter including title, date, status, and type, and write a concise plan description.

Frequently Asked Questions about plan-conventions

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

FAQPage Schema
How do I enforce frontmatter and lifecycle rules for PRDs and TDDs?

To enforce frontmatter and lifecycle for PRDs and TDDs, require title, date, status, and type fields in every plan file. This standardizes plan documentation and governs transitions from draft through completed or cancelled.

What frontmatter fields are required for plan documentation under docs/plans?

Required plan frontmatter fields are title, date, status, and type. Including these in docs/plans/ files ensures consistent plan documentation, traceability, and lifecycle validation for TDDs, PRDs, and lightweight plans.

What is the standard lifecycle for a plan from draft to completion?

The standard plan lifecycle transitions are draft, proposed, accepted, implementing, completed, or cancelled. Enforcing these status transitions ensures proper review and governance for plans stored under docs/plans/.

How do I standardize lightweight plans to improve traceability and review?

Standardize lightweight plans by applying frontmatter validation and lifecycle enforcement under docs/plans/. Requiring title, date, status, and type fields improves traceability and review across all planning artifacts.

Can I use this plan governance for both TDDs and PRDs?

Yes, plan governance applies to TDDs, PRDs, and lightweight plans. It enforces consistent documentation by requiring specific frontmatter and managing lifecycle status transitions for every plan file.