plot-approve

Merge approved GitHub PR plans into main and create per-branch implementation PRs.

2|Updated Feb 7, 2026

Search Tags:#automation #git #workflow #plot #branch #pr #approve

Ready to run

npx skills add https://github.com/eins78/skills --skill plot-approve

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plot-approve
Source: https://github.com/eins78/skills/tree/main/skills/plot-approve
Command: npx skills add https://github.com/eins78/skills --skill plot-approve

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Merge approved plans into main and seed per-branch implementation work with proper approval metadata.

Core Features & Use Cases

Automates the fan-out of an approved plan into multiple implementation branches, each prepared for PR creation.
Parses the plan, validates branches, assigns approval metadata, and updates the plan on main with linked PRs.
Use case: A team has an approved plan and wants to automatically generate feature branches and corresponding PRs for parallel work.

Quick Start

Run /plot-approve with a valid slug to merge the plan and fan out into implementation branches.

Frequently Asked Questions about plot-approve

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

FAQPage Schema

How do I automate creating implementation branches from an approved GitHub PR plan?▼

Automating implementation branch creation from an approved GitHub PR plan involves parsing the plan file, merging it into main, and fanning out into per-branch work with associated PR creation and approval metadata. This process enforces branch naming conventions automatically.

What's the best way to fan out an approved project plan into multiple feature branches?▼

Fanning out an approved project plan into multiple feature branches requires parsing the plan, validating branch names, and spawning per-branch implementation work with PR creation. The plan on main is then updated with linked PRs and approval metadata.

Does this workflow automation tool enforce branch naming conventions when seeding implementation work?▼

Yes, this workflow automation enforces branch naming conventions during the plan fan-out process. It validates branches, assigns approval metadata, and creates associated PRs while parsing the plan file to guide the branching structure.

Can I extract project configuration from CLAUDE.md to guide the release workflow during plan approval?▼

Yes, you can extract project configuration from CLAUDE.md to guide the release workflow during plan approval. The process optionally reads project-config to inform branch creation, approval stamping, and PR generation.

How do I merge an approved plan into main and update it with linked PRs automatically?▼

Merging an approved plan into main and updating it with linked PRs happens by integrating the plan, spawning implementation branches, and stamping approval metadata. The plan file on main is then updated with links to the newly created PRs.

Do I need a valid slug to start the plan approval and branch seeding process?▼

Yes, you need a valid slug to start the plan approval and branch seeding process. Running the approval command with a valid slug triggers the plan merge, branch fan-out, PR creation, and approval metadata stamping.