plot

Manage software development planning within a git repository.

2|3|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/plot-pm/plot --skill plot-plot-pm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plot
Source: https://github.com/plot-pm/plot/tree/main/skills/plot
Command: npx skills add https://github.com/plot-pm/plot --skill plot-plot-pm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires claude-code, git, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill replaces issue trackers with a git-native planning system, allowing for the creation, review, and implementation of plans directly within the git repository. It streamlines the software development process by using markdown files on branches, pull requests as workflow metadata, and git as the single source of truth.

Core Features & Use Cases

  • Git Native Planning: Create and manage plans as markdown files on branches, with pull requests serving as workflow metadata.
  • Lifecycle Phases: Plans progress through defined phases: Draft, Approved, Delivered, and Released, with specific commands for each step.
  • Parallel Implementation: Multiple implementation branches can be created from a single plan, allowing for parallel work on different aspects of the project.
  • Sprints: Optional time-boxed sprints can be used to coordinate and prioritize work within a set timeframe.
  • Use Case: A development team can use this Skill to plan a new feature, with the ability to review, approve, implement, and ultimately release the feature all within the git repository.

Quick Start

Run the following command to create a new plan for a feature:

/plot-idea <feature-name>

Frequently Asked Questions about plot

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

FAQPage Schema
How do I manage software development planning within a git repository?

Yes, you can replace traditional issue trackers with a git-native planning system. This approach uses markdown files on branches and pull requests as workflow metadata, establishing git as the single source of truth for all your software development planning needs.

How do I create and track a feature plan through its lifecycle using git?

To create a feature plan, run the /plot-idea command. Plans then progress through defined lifecycle phases: Draft, Approved, Delivered, and Released, with specific git commands automating each step from creation to final release.

Do I need Claude Code integration to use this git planning workflow?

Yes, Claude Code integration is required to run this planning workflow. You also need basic knowledge of git and pull requests to manage the lifecycle commands and markdown files effectively within your software development repository.

Can I implement multiple branches from a single plan for parallel software development?

Yes, multiple implementation branches can be created from a single plan. This allows for parallel work on different aspects of the project, and optional time-boxed sprints can be used to coordinate and prioritize the parallel work within a set timeframe.

What are the limitations of using markdown files on git branches for project planning?

This git-native planning approach relies entirely on git and markdown files, meaning all planning data lives in your repository. It requires Claude Code and git proficiency, shifting the planning workflow away from standalone issue trackers into your codebase.