PlanExe
Create a plan from a description in minutes
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Check it deeper on your machine
It has changed since its scan on 11 Nov 2026.
As a Claude Code plugin, install it and then ask Claude Code:
/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/PlanExeOrg/PlanExe with scanskillsafety
Or from a terminal, clone it and run it:
git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/PlanExeOrg/PlanExe'
It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.
Badge for your README
Markdown
[](/listings/planexeorg--planexe)HTML
<a href="/listings/planexeorg--planexe"><img src="/api/listings/planexeorg--planexe/badge.svg" alt="findsafeskills safety rating" /></a>Install
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
README.md · README · 137 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.
- <p align="center">
- <picture>
- <source media="(prefers-color-scheme: dark)"
- srcset="docs/hero/planexe-hero-v1-grid-dark.svg">
- <img src="docs/hero/planexe-hero-v1-grid-light.svg"
- alt="The PlanExe icon is the P character and E character"
- width="100%">
- </picture>
- </p>
- <p align="center">
- <strong>Planning complex projects should not require a consulting-firm budget.</strong>
- </p>
- > [!IMPORTANT]
- > **PlanExe v2 is here, and it is better than v1.**
- > This repository is PlanExe v1. For new plans, use
- > [PlanExe2](https://github.com/PlanExeOrg/PlanExe2).
- <p align="center">
- Turn a complex project brief into an editable planning baseline in roughly 65–90 minutes.
- </p>
- <p align="center">
- <a href="https://github.com/PlanExeOrg/PlanExe2"><strong>PlanExe v2</strong></a> |
- <a href="https://planexe.org/examples/"><strong>See example plans</strong></a>
- </p>
- ---
- ## Why PlanExe exists
- Good ideas are not limited to people and organizations that can afford a large
- consulting engagement. Turning an ambitious idea into a coherent project,
- however, normally requires substantial time, specialist knowledge, stakeholder
- interviews, and repeated synthesis.
- PlanExe is open-source software for people and AI agents that need to plan
- complex projects. Describe a project in plain language and PlanExe creates a
- structured first-pass plan: the assumptions to challenge,
- decisions to make, work to coordinate, risks to investigate, and questions that
- must be answered before execution.
- The result is not a substitute for stakeholder participation or professional
- sign-off. It is a way to begin with a broad, inspectable planning baseline
- instead of a blank page.
- ## What PlanExe does
- PlanExe examines a project from several planning perspectives and combines the
- results into one self-contained interactive report. Depending on the project,
- the output commonly includes:
- - Executive summary and project purpose
- - Assumptions, constraints, and unanswered questions
- - Strategic choices and alternative scenarios
- - Work breakdown structure and dependency-aware Gantt chart
- - Governance bodies, decision rights, and escalation paths
- - Roles, stakeholders, and engagement approaches
- - Risk register, SWOT analysis, and mitigation proposals
- - Premortem, expert criticism, premise attack, and self-audit
- - Documents to create, documents to find, and data to collect
- - An editable bundle of Markdown, JSON, and CSV source artifacts
- PlanExe v2 runs on your own machine and makes its model calls through the
- Claude Code CLI, using your Claude subscription.
- ## Built for complex projects
- PlanExe is intended for consulting-scale, multi-phase initiatives—not everyday
- task lists or small personal projects.
- Examples of suitable work include:
- - Planning a regional clean-water, energy, or transport infrastructure program
- - Coordinating a regulated healthcare or financial-services transformation
- - Designing a cross-border public-sector initiative
- - Preparing a complex business, industrial, or technology program
- - Structuring an ERP migration, corporate separation, or post-merger integration
- - Helping an under-resourced organization develop an ambitious proposal before
- it has access to specialist advisers
- The richer the brief—objective, location, constraints, stakeholders, resources,
- timeline, and success criteria—the more useful the resulting plan becomes.
- ## A plan you can inspect and change
- PlanExe does not hide the planning process inside a chat transcript. Each run
- produces a folder of readable source artifacts alongside the final report.
- If you find an assumption or early decision you disagree with, you can edit that
- artifact and continue the plan from there. PlanExe rebuilds the later work that
- depends on your change while preserving earlier work you already accept. This
- makes it possible to refine the reasoning behind a plan, not merely rewrite its
- final prose.
- ## What PlanExe does not replace
- PlanExe creates a draft for investigation and refinement. Generated claims,
- budgets, dates, laws, engineering assumptions, and risk estimates may be wrong
- or incomplete. Important projects still require:
- - Evidence and current local data
- - Stakeholder interviews and negotiation
- - Domain experts and professional judgment
- - Legal, financial, medical, safety, or engineering review where applicable
- - Named people who take responsibility for decisions and execution
- Use the report to expose assumptions, focus conversations, and accelerate
- planning—not as proof that a project is safe, feasible, funded, or approved.
- ## See a plan, then generate one
- 1. [Browse plans generated by PlanExe](https://planexe.org/examples/) and open
- any report that interests you.
- 2. [Generate your own plan with PlanExe v2](https://github.com/PlanExeOrg/PlanExe2).
- ## Why run PlanExe on your own machine?
- PlanExe v2 is a small Python program that you clone and run yourself. There is
- no hosted service and no PlanExe account. Running it locally lets you:
- - Keep every generated plan as files on your own disk
- - Edit any intermediate file and regenerate only the work that depends on it
- - Resume an interrupted run without repeating the work already finished
- - Read the log of every prompt and response behind the report
- - Get started with nothing more than Python 3.11 and the Claude Code CLI
- PlanExe v2 sends your project brief and the intermediate planning material to
- Anthropic through the Claude Code CLI. Do not use it for material that must not
- leave systems you control.
- Running PlanExe yourself does not remove your legal, ethical, security, or
- professional responsibilities.
- For setup instructions, see the
- [PlanExe v2 repository](https://github.com/PlanExeOrg/PlanExe2).
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.