plan-project
Skill1 starsChanged 3 months agoMITView on GitHub
Build a project plan — scope (in/out), work breakdown, schedule and milestones, dependencies and critical path, and an initial RAID log. Use for a defined deliverable with constraints. Dispatches the project-manager.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- mattolson/agent-sandboxtheir own version, first seen Oct 8, 2026
- KodingDev/skillstheir own version, first seen Oct 2, 2026
- pi247/classic-PM-skillstheir own version, first seen Aug 21, 2026
- YUVARAJ-R-ai/my-claude-skillstheir own version, first seen Jun 30, 2026
- qkitzero/kage-bunshintheir own version, first seen Apr 5, 2026
- MooseDesign1/DDD-DesignDrivenDevelopmenttheir own version, first seen Mar 30, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- mattolson/agent-sandbox★ 212same name
- MooseDesign1/DDD-DesignDrivenDevelopment★ 9same name
- KodingDev/skills★ 2same name
- YUVARAJ-R-ai/my-claude-skills★ 2same name
- pi247/classic-PM-skills★ 1same name
- qkitzero/kage-bunshin★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository30 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- build-business-caseSkill
- build-roadmapSkill
- capture-feedbackSkill
- close-projectSkill
- coordinate-programSkill
- define-metricsSkill
- define-strategySkill
- design-dashboardSkill
- elicit-requirementsSkill
- groom-backlogSkill
- make-deliverableSkill
- manage-changeSkill
- manage-resourcesSkill
- plan-capacitySkill
- plan-launchSkill
- plan-portfolio-automationSkill
- plan-sprintSkill
- powerbiSkill
- prioritizeSkill
- review-okrsSkill
- review-portfolio-intakeSkill
- run-ceremonySkill
- run-discoverySkill
- run-gate-reviewSkill
- setup-pmoSkill
- track-financialsSkill
- track-portfolioSkill
- track-statusSkill
- write-prdSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 33
Start from templates/project-plan.md.
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/plan-project — Plan a defined deliverable
When to use
Planning a project/initiative with a defined outcome, schedule, or dependencies (beyond a single sprint).
Dispatches
project-manager (lead). Consult program-manager for cross-team dependencies; delivery-monitor for the
RAID/health setup.
Inputs
knowledge/product-context.md, knowledge/roadmap.md, knowledge/cadence.md, knowledge/stakeholder-map.md.
Steps
- Choose and tailor the development approach (predictive / adaptive / hybrid) and delivery cadence to the work.
- Define scope as deliverables with acceptance criteria; state what's out of scope.
- Decompose into a WBS of work packages small enough to estimate and own.
- Sequence by dependency; estimate durations with the fitting technique (analogous / parametric / bottom-up / three-point) and stated confidence; identify milestones and the critical path.
- Set explicit reserves (contingency for known risks, management for unknowns); set up the RAID log: top risks (prob × impact, owner, response), assumptions, issues, dependencies.
- Confirm RACI for key deliverables (exactly one Accountable each); note the change-control approach and, where a cost/schedule baseline applies, how progress will be tracked by earned value (SPI/CPI).
Methods
knowledge/methods/project-management.md, knowledge/methods/agile-scrum-mechanics.md.
Output
Start from templates/project-plan.md. Save a project plan artifact (e.g., knowledge/projects/<name>.md) and initialized/updated knowledge/raid-log.md;
log scope/schedule decisions to knowledge/decision-log.md. Follow standards/document-standards.md.
Created by Colin Beck<br>
LinkedIn: https://www.linkedin.com/in/beckcolin/<br>
GitHub: https://github.com/link7373
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.