project-scope-planner
Skill1 starsChanged 31 days agoMITView on GitHub
Divide an accepted freelance project into clear milestones, tasks, deliverables, dependencies, and a realistic timeline, and produce a scope document the client can approve before work starts. Use when a user says a client accepted their proposal, asks how to plan or divide a project, wants milestones for Upwork or a contract, or needs a timeline estimate. Acts as the project manager: plan first, divide the work, then execute.
In this repository11 other files it gives its agents.
- assignment-researcherSkill
- client-brief-analyzerSkill
- fyp-project-managerSkill
- interview-grillerSkill
- learn-in-30-daysSkill
- portfolio-case-studySkill
- pricing-calculatorSkill
- professional-emailSkill
- proposal-writerSkill
- resume-builderSkill
- study-any-topicSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Add the client-side tasks separately: assets, logins, feedback rounds - each with the date you need it by, because most delays are waiting, …
- Distinctive: line 19
Write the Not included list - everything reasonable a client might assume is included but is not.
- Distinctive: line 24
Never schedule the user day at 100 percent.
- Distinctive: line 25
If the deadline cannot fit the honest timeline, say so in the plan and offer two options: reduce scope or extend the date.
- Distinctive: line 33
Not included - explicit list
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Project Scope Planner
When to use this skill
- A job is won and work is about to start
- Setting Upwork milestones or a fixed-price scope
- A client keeps adding one small thing and scope needs re-drawing
Workflow
- Restate the final deliverable in one sentence and get the start date, deadline, and the user real available hours per day. Never plan with fantasy hours.
- Divide the project into 3-6 milestones. Each milestone must end with something the client can see and approve (a draft, a file, a staging link) - never 50 percent done.
- Under each milestone, list tasks in the order they must happen, and mark dependencies (what cannot start until the client sends X).
- Add the client-side tasks separately: assets, logins, feedback rounds - each with the date you need it by, because most delays are waiting, not working.
- Build the timeline from real hours: total estimated hours per milestone divided by available hours per day, plus a 20 percent buffer. Show the maths briefly.
- Write the Not included list - everything reasonable a client might assume is included but is not. This list prevents most disputes.
- End with revision rules: how many revision rounds per milestone, and what counts as a revision vs new scope (which is quoted separately).
Rules - never break these
- A milestone the client cannot see or approve is not a milestone - rewrite it.
- Never schedule the user day at 100 percent. Buffer is part of the plan, not padding to hide.
- If the deadline cannot fit the honest timeline, say so in the plan and offer two options: reduce scope or extend the date. Never silently promise both.
- The scope document is written for the client to read: plain language, no internal notes, no jargon.
Output format
- Project - one-sentence deliverable + deadline
- Milestones - numbered, each with deliverable, tasks, estimated hours, approval point
- Client must provide - item + needed-by date
- Timeline - milestone dates with buffer shown
- Not included - explicit list
- Revisions - rounds included, what counts as new scope
Example
User: Plan this project: client accepted my proposal to build a 5-page WordPress site, I can work 4 hours a day, start Monday, they want it in 2 weeks.
Good output (excerpt): Milestone 1 (Days 1-3): Setup + homepage draft the client can view - 10 hrs. Client must provide: logo, hosting login by Day 1, page text by Day 3. Not included: writing the page copy, buying premium plugins, more than 5 pages.
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.

