plan-format

Organizes Gherkin-based plan files with trackable TODO/DONE states.

4|Updated Dec 10, 2025
One-click install
npx skills add https://github.com/tommymorgan/claude-plugins --skill plan-format
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-format
Source: https://github.com/tommymorgan/claude-plugins/tree/main/tommymorgan/planning/skills/plan-format
Command: npx skills add https://github.com/tommymorgan/claude-plugins --skill plan-format

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan files specification helps plan development across teams by codifying requirements and tracking progress with a single source of truth.

Core Features & Use Cases

  • Plan file structure and template for features across projects
  • Tracks TODO/DONE state via inline markers to guide autonomous workflows
  • Enables living documentation and consistent feature planning for Gherkin-based plans

Quick Start

Create a new plan file at <project>/plans/YYYY-MM-DD-<slug>.md following the plan template described here.

Frequently Asked Questions about plan-format

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

FAQPage Schema
How do I format feature plans with a consistent markdown template?

You format feature plans by applying a standard markdown template with sections for Created Date, Goal, User Requirements, and Technical Specifications to maintain a single source of truth across project teams.

What is a living Gherkin-based plan file?

A living Gherkin-based plan file is a markdown document that codifies user requirements as scenarios and tracks TODO/DONE states inline, enabling continuous feature planning and living documentation.

How do I track TODO and DONE states in feature planning documentation?

You track TODO and DONE states in feature planning documentation by using inline markers within living Gherkin-based plan files, which guides autonomous workflows and tracks development progress.

Can I use Gherkin scenarios for technical specifications and progress tracking?

Yes, you can use Gherkin scenarios for technical specifications by structuring plan files with living scenario metadata that enforces standard plan templates while tracking development progress.

What is the best way to structure a plan file for autonomous workflows?

The best way to structure a plan file for autonomous workflows is to follow a standard template at <project>/plans/YYYY-MM-DD-<slug>.md with inline TODO/DONE markers and living Gherkin scenarios.