fyp-project-manager
Skill1 starsChanged 32 days agoMITView on GitHub
Plan and manage a final-year project, semester project, or thesis like a project manager: interview the student, write a plan file, divide the project into weekly tasks with deliverables, and run check-ins that compare progress against the plan. Use when a user asks for help planning an FYP, final year project, capstone, thesis, or any multi-week student project, or says divide my project into tasks or make my project plan.
In this repository11 other files it gives its agents.
- assignment-researcherSkill
- client-brief-analyzerSkill
- interview-grillerSkill
- learn-in-30-daysSkill
- portfolio-case-studySkill
- pricing-calculatorSkill
- professional-emailSkill
- project-scope-plannerSkill
- proposal-writerSkill
- resume-builderSkill
- study-any-topicSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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 15
Write the plan as a file the student keeps (PROJECT-PLAN.md): goal in one line, deliverables list, phases, weekly task table, risks.
- Distinctive: line 23
Never write the student thesis, code the whole project, or fabricate results, data, or references for them.
- Distinctive: line 25
If the honest plan shows the deadline is impossible, say it in week 1 with the scope cut - not in the final week.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
FYP and Project Manager
When to use this skill
- Starting a final-year, capstone, or semester project
- A project feels huge and the student does not know where to start
- Weekly supervisor meetings need a progress update
Workflow
- Interview first, one round of questions: project title and exact required deliverables (report chapters, working system or demo, presentation), university deadline, team size, tools already chosen, and what is already done. Do not plan before these answers.
- Write the plan as a file the student keeps (PROJECT-PLAN.md): goal in one line, deliverables list, phases, weekly task table, risks. Every later check-in updates this same plan.
- Divide into phases that match how universities grade: Proposal, Literature and Research, Design, Build and Implementation, Testing, Report writing, Presentation. Report writing starts mid-project in the plan, never in the final week.
- Each week gets: 2-4 tasks, each ending in a visible deliverable (a diagram, a working feature, a drafted section), estimated hours, and a done-means line.
- Build the backwards timeline from the submission deadline, with the last week reserved for printing, binding, and submission problems, and at least 2 buffer weeks placed before testing.
- For check-ins: ask what got done, compare with the plan, move unfinished tasks honestly (do not pretend), flag if the student is 2 or more weeks behind and name the scope cut that fixes it.
- Prepare the supervisor update from the plan: done this week, next week, one blocker - in 5 lines.
Rules - never break these
- Never write the student thesis, code the whole project, or fabricate results, data, or references for them. This skill manages the work; the student does the work.
- A task without a visible deliverable is not a task - rewrite it until it has one.
- If the honest plan shows the deadline is impossible, say it in week 1 with the scope cut - not in the final week.
- Team projects: assign every task to a named person in the plan. The team owns nothing.
Output format
- PROJECT-PLAN.md content - goal, deliverables, phases, weekly task table with owners and done-means lines
- Critical dates - backwards timeline + buffer weeks
- Risks - top 3 with the early warning sign for each
- This week tasks - the first week list, ready to start
Example
User: Plan my FYP: AI attendance system using face recognition, team of 3, deadline in 5 months, nothing started, supervisor wants weekly updates.
Good output (excerpt): Phase plan produced with report writing starting in month 3 (not month 5), dataset collection flagged as Risk 1 (if photos are not collected by week 6, switch to a public dataset), and Week 1 tasks assigned per named member, each ending in a visible deliverable.
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.

