By eins78
Git-native planning workflow for software development — idea, approve, deliver, release
Verify release readiness and guide the release process. Part of the Plot workflow. Use on /plot-release.
Merge an approved plan and fan out into implementation branches. Part of the Plot workflow. Use on /plot-approve.
Verify all implementation is done, then deliver the plan. Part of the Plot workflow. Use on /plot-deliver.
Create a plan for review: idea branch, plan file, and draft PR. Part of the Plot workflow. Use on /plot-idea.
Reverse a premature delivery — move plan from Delivered back to Approved. Part of the Plot workflow. Use on /plot-reject.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Git-native planning workflow for software development.
Plans are markdown files — written, reviewed, and versioned like source code. They live on branches, merge through pull requests, and stay in place forever. No external tracker, no database, no sync API. If it's not in git, it doesn't exist.
Plot works for any team composition, but is especially designed for human decision-makers working with AI facilitators and AI coding agents. Humans always own the decisions. Every step can also be done by a human with basic git knowledge.
/plot-idea (Draft) Create plan branch + file + draft PR
|
Review Human reviews, refines, marks ready
|
/plot-approve Merge plan to main, fan out implementation branches
|
Implement Parallel work on feature/bug/docs/infra branches
|
/plot-deliver Verify all impl PRs merged, archive plan
|
/plot-release Cut versioned release with changelog
Sprints (/plot-sprint) are orthogonal — they group plans by schedule, not by workflow phase.
New to Plot? Read Intro to Using Plot for a walkthrough of the lifecycle.
| Skill | Description |
|---|---|
| plot | Hub & dispatcher — reads git state, suggests next action |
| plot-idea | Create a plan: idea branch, plan file, and draft PR |
| plot-approve | Merge approved plan, fan out into implementation branches |
| plot-deliver | Verify implementation complete, archive the plan |
| plot-release | Create versioned release from delivered plans |
| plot-sprint | Time-boxed sprint coordination with MoSCoW prioritization |
| ralph-plot-sprint | Automated sprint runner (extension) |
/plugin marketplace add eins78/plot
/plugin install plot@plot-marketplace
Skills auto-update when you run /plugin update.
pnpx skills add https://github.com/eins78/plot.git --global --agent claude-code --all --yes
ln -s ~/CODE/plot/skills/plot ~/.claude/skills/plot
Add a ## Plot Config section to your project's CLAUDE.md:
## Plot Config
- Plan directory: `docs/plans/`
- Sprint directory: `docs/sprints/`
- Branch prefixes: `idea/`, `feature/`, `bug/`, `docs/`, `infra/`
- Active symlink: `docs/plans/active/`
- Delivered symlink: `docs/plans/delivered/`
Plot discovers and adapts to whatever conventions your project provides. No hardcoded paths.
/plot-approve heuristics for work with technical uncertainty. Install separately from eins78/skills.See MANIFESTO.md for Plot's founding principles and design philosophy.
See changelog.md for the complete evolution history.
MIT
npx claudepluginhub eins78/plot --plugin plotSwiss weather data for AI assistants — forecasts, current conditions, stations, and pollen from MeteoSwiss Open Data. Free, no API key required.
Skill-driven planning and execution loop for coding agents: one planr entry point, an autonomous planr-loop, and evidence-backed task graph skills powered by the planr CLI.
Iterative plan review and execution workflow for Claude Code
Structured implementation planning, interactive annotation review, and autonomous plan execution
AI-powered cascading development framework with design document system and multi-agent collaboration. Breaks down projects into Features (Mega Plan), Features into Stories (Hybrid Ralph), with auto-generated technical design docs, dependency-driven batch execution, Git Worktree isolation, and support for multiple AI agents (Codex, Amp, Aider, etc.).
Implementation planning, execution, and PR creation workflows with multi-agent collaboration
A structured development pipeline: task bootstrapping, project planning, feature planning, task generation, TDD implementation, and code review