Skip to content
Back to search

numal

MarketplaceWorks with Claude CodeGitHub

17 free project manager skills for Claude Code and Codex: meeting minutes, agendas, decision log, RAID log, status reports, 1:1s, retros and more

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/numal-ai--project-manager-skills/badge.svg)](/listings/numal-ai--project-manager-skills)

HTML

<a href="/listings/numal-ai--project-manager-skills"><img src="/api/listings/numal-ai--project-manager-skills/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Claude Code

/plugin install project-manager-skills --marketplace numal-ai/project-manager-skills

On Claude Code older than 2.1.275, add the marketplace first:

/plugin marketplace add numal-ai/project-manager-skills
/plugin install project-manager-skills@numal

All seventeen add about 2,900 tokens to each session (their names and descriptions). A skill's full text loads only when you use it.

Want only some of the skills? Each one is also its own plugin, about 150 to 200 tokens each. Install the full set or single skills, not both, or each skill shows up twice.

/plugin install meeting-minutes --marketplace numal-ai/project-manager-skills
/plugin install meeting-agenda --marketplace numal-ai/project-manager-skills
/plugin install decision-log --marketplace numal-ai/project-manager-skills
/plugin install action-items --marketplace numal-ai/project-manager-skills
/plugin install raid-log --marketplace numal-ai/project-manager-skills
/plugin install status-report --marketplace numal-ai/project-manager-skills
/plugin install one-on-one --marketplace numal-ai/project-manager-skills
/plugin install standup --marketplace numal-ai/project-manager-skills
/plugin install retrospective --marketplace numal-ai/project-manager-skills
/plugin install morning-brief --marketplace numal-ai/project-manager-skills
/plugin install project-charter --marketplace numal-ai/project-manager-skills
/plugin install change-control --marketplace numal-ai/project-manager-skills
/plugin install raci-matrix --marketplace numal-ai/project-manager-skills
/plugin install stakeholder-map --marketplace numal-ai/project-manager-skills
/plugin install lessons-learned --marketplace numal-ai/project-manager-skills
/plugin install team-charter --marketplace numal-ai/project-manager-skills
/plugin install skip-level-meeting --marketplace numal-ai/project-manager-skills

Or copy single skills into your skills folder:

git clone https://github.com/numal-ai/project-manager-skills
cp -R project-manager-skills/skills/meeting-minutes ~/.claude/skills/

Any agent, one command

The open [skills](https://github.com/vercel-labs/skills) installer puts the skills where your agent looks for them: Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI and many others. It asks which agents and which skills.

npx skills add numal-ai/project-manager-skills

One skill only:

npx skills add numal-ai/project-manager-skills --skill meeting-minutes

claude.ai and Claude Cowork

Download a ready ZIP from the [latest release](https://github.com/numal-ai/project-manager-skills/releases/latest):

| Download | What's inside | |---|---| | [Starter pack](https://github.com/numal-ai/project-manager-skills/releases/latest/download/project-manager-skills-starter.zip) | meeting-minutes, meeting-agenda and status-report. The best first download | | [All skills](https://github.com/numal-ai/project-manager-skills/releases/latest/download/project-manager-skills-all.zip) | All seventeen | | Single skill | `https://github.com/numal-ai/project-manager-skills/releases/latest/download/<skill>.zip`, for example [meeting-minutes.zip](https://github.com/numal-ai/project-manager-skills/releases/latest/download/meeting-minutes.zip) |

1. Unzip the pack. Inside are one ZIP per skill. 2. Upload those skill ZIPs in **Customize → Skills** (on older versions, **Settings → Capabilities → Skills**). Don't upload the pack itself. 3. Start a new chat and say what you need, for example `Write minutes from this transcript`.

In Cowork you can also add this repository as a plugin marketplace in **Customize → Plugins**. More in [docs/claude-cowork.md](docs/claude-cowork.md).

OpenAI Codex

Copy the skills into your personal skills folder:

git clone https://github.com/numal-ai/project-manager-skills
mkdir -p ~/.agents/skills
cp -R project-manager-skills/skills/* ~/.agents/skills/

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.

.claude-plugin/marketplace.json · Manifest · 172 lines
  1. {
  2. "name": "numal",
  3. "owner": {
  4. "name": "Numal",
  5. "url": "https://numal.ai"
  6. },
  7. "metadata": {
  8. "description": "Open-source project manager skills for Claude and Codex",
  9. "version": "0.1.2"
  10. },
  11. "plugins": [
  12. {
  13. "name": "project-manager-skills",
  14. "description": "Project manager skills for Claude Code, Cowork and Codex: meeting minutes, meeting agendas, decision log, action items, RAID log, status reports, 1:1s, skip-level meetings, standups, retrospectives, morning brief, project charter, team charter, change control, RACI matrix, stakeholder map and lessons learned. The skills share one folder of Markdown records.",
  15. "source": "./",
  16. "category": "productivity"
  17. },
  18. {
  19. "name": "meeting-minutes",
  20. "description": "Meeting minutes from a transcript or notes: decisions accepted and not accepted, action items with owners and dates, risks, open questions and a recap message.",
  21. "source": "./skills/meeting-minutes",
  22. "category": "productivity",
  23. "skills": [
  24. "."
  25. ]
  26. },
  27. {
  28. "name": "meeting-agenda",
  29. "description": "Meeting agendas built from what is still open: overdue actions, decisions due for a revisit, risks and leftovers. Each item has an outcome, a lead and a time box.",
  30. "source": "./skills/meeting-agenda",
  31. "category": "productivity",
  32. "skills": [
  33. "."
  34. ]
  35. },
  36. {
  37. "name": "decision-log",
  38. "description": "A decision log: records decisions with who decided and why, finds past ones with their source, flags contradictions and decisions due for a revisit.",
  39. "source": "./skills/decision-log",
  40. "category": "productivity",
  41. "skills": [
  42. "."
  43. ]
  44. },
  45. {
  46. "name": "action-items",
  47. "description": "One action list across meetings: owners, due dates, what is overdue and polite follow-ups. Creates tracker tickets with the meeting context after you confirm.",
  48. "source": "./skills/action-items",
  49. "category": "productivity",
  50. "skills": [
  51. "."
  52. ]
  53. },
  54. {
  55. "name": "raid-log",
  56. "description": "A RAID log and risk register: risks, assumptions, issues and dependencies, each with an owner, a mitigation and a weekly review of what changed.",
  57. "source": "./skills/raid-log",
  58. "category": "productivity",
  59. "skills": [
  60. "."
  61. ]
  62. },
  63. {
  64. "name": "status-report",
  65. "description": "Weekly project status reports with an honest RAG status, built from the record. Also rolls several projects up into one page.",
  66. "source": "./skills/status-report",
  67. "category": "productivity",
  68. "skills": [
  69. "."
  70. ]
  71. },
  72. {
  73. "name": "one-on-one",
  74. "description": "1:1 prep and notes with your reports or your manager, kept in a private running doc per person.",
  75. "source": "./skills/one-on-one",
  76. "category": "productivity",
  77. "skills": [
  78. "."
  79. ]
  80. },
  81. {
  82. "name": "standup",
  83. "description": "Async standup summaries with blockers first and who can unblock them, plus work that has not moved.",
  84. "source": "./skills/standup",
  85. "category": "productivity",
  86. "skills": [
  87. "."
  88. ]
  89. },
  90. {
  91. "name": "retrospective",
  92. "description": "Sprint retrospectives, project post-mortems and lessons learned, grounded in what happened, ending with a few owned actions.",
  93. "source": "./skills/retrospective",
  94. "category": "productivity",
  95. "skills": [
  96. "."
  97. ]
  98. },
  99. {
  100. "name": "morning-brief",
  101. "description": "A one-page morning brief: what needs you today to decide, unblock or do, plus prep for today's meetings. Read-only.",
  102. "source": "./skills/morning-brief",
  103. "category": "productivity",
  104. "skills": [
  105. "."
  106. ]
  107. },
  108. {
  109. "name": "project-charter",
  110. "description": "Project charter from a kickoff transcript or notes: goal, measurable success criteria, scope in and out, milestones, who approves changes, plus seed rows for the RAID log, decisions and actions.",
  111. "source": "./skills/project-charter",
  112. "category": "productivity",
  113. "skills": [
  114. "."
  115. ]
  116. },
  117. {
  118. "name": "change-control",
  119. "description": "Scope change control: change requests with the impact on scope, dates, budget, people and risks, a change log, and plan updates after the owner decides.",
  120. "source": "./skills/change-control",
  121. "category": "productivity",
  122. "skills": [
  123. "."
  124. ]
  125. },
  126. {
  127. "name": "raci-matrix",
  128. "description": "RACI matrix from the charter, actions and decisions: one accountable person per row, gaps and bottlenecks flagged, and answers to who decides on what.",
  129. "source": "./skills/raci-matrix",
  130. "category": "productivity",
  131. "skills": [
  132. "."
  133. ]
  134. },
  135. {
  136. "name": "stakeholder-map",
  137. "description": "Stakeholder map and communication plan: interest and influence, what each person needs to hear, how and how often, and who needs to hear about a change.",
  138. "source": "./skills/stakeholder-map",
  139. "category": "productivity",
  140. "skills": [
  141. "."
  142. ]
  143. },
  144. {
  145. "name": "lessons-learned",
  146. "description": "Lessons learned register and closure report: lessons from retros and reviews with sources, what came of past decisions, and matching lessons for a new project.",
  147. "source": "./skills/lessons-learned",
  148. "category": "productivity",
  149. "skills": [
  150. "."
  151. ]
  152. },
  153. {
  154. "name": "team-charter",
  155. "description": "Team charter and working agreements: what the team is for and owns, how it decides, its agreements and meetings, kept true at each retro.",
  156. "source": "./skills/team-charter",
  157. "category": "productivity",
  158. "skills": [
  159. "."
  160. ]
  161. },
  162. {
  163. "name": "skip-level-meeting",
  164. "description": "Skip-level meeting prep and private notes, themes across a round without names, and what to take back to the lead.",
  165. "source": "./skills/skip-level-meeting",
  166. "category": "productivity",
  167. "skills": [
  168. "."
  169. ]
  170. }
  171. ]
  172. }
README.md · README · 303 lines
  1. # Project Manager Skills
  2. Seventeen open-source project manager skills for **Claude Code**, **Claude Cowork**, **claude.ai** and **OpenAI Codex**: meeting minutes, meeting agendas, a decision log, action items, a RAID log, status reports, 1:1s, skip-level meetings, standups, retrospectives, a morning brief, a project charter, a team charter, change control, a RACI matrix, a stakeholder map with a communication plan, and a lessons learned register.
  3. ![A meeting transcript becomes minutes, a decision log and action items. Then the agenda for the next meeting opens with what this one left open.](assets/demo.gif)
  4. They are written for project managers, and they work just as well for team leads, engineering managers and product managers who run meetings and keep projects on track. Any agent that reads the open [Agent Skills](https://agentskills.io) format can use them.
  5. The skills share one folder of plain Markdown files. Whatever a meeting decides shows up in the next agenda, the Friday status report and tomorrow's morning brief, without you copying anything between them.
  6. ```
  7. kickoff ──────► project-charter ──► PROJECT.md: goal, scope, milestones, who decides
  8. transcript ───► meeting-minutes ──► DECISIONS.md, ACTIONS.md, RAID.md ──► meeting-agenda
  9. ├─► status-report
  10. ├─► standup
  11. └─► morning-brief
  12. "can we add…" ► change-control ───► CHANGES.md ──► the agenda, for whoever decides
  13. launch review ► lessons-learned ──► LESSONS.md ──► the next project's charter and RAID log
  14. how we work ──► team-charter ─────► TEAM.md ─────► the retro checks the agreements
  15. ```
  16. ## Try it in five minutes
  17. 1. Get the skills:
  18. - **Claude Code:** `/plugin install project-manager-skills --marketplace numal-ai/project-manager-skills`
  19. - **Codex, Cursor, GitHub Copilot and other agents:** `npx skills add numal-ai/project-manager-skills`
  20. - **claude.ai or Claude Cowork:** download the [starter pack](https://github.com/numal-ai/project-manager-skills/releases/latest/download/project-manager-skills-starter.zip) and unzip it. Upload the three skill ZIPs inside it in **Customize → Skills**.
  21. 2. Paste the notes or the transcript of your last meeting and say: `Write minutes from this meeting.`
  22. 3. Then say: `Prep the agenda for our next meeting.`
  23. The agenda opens with what the minutes left open. That's the point of the set: each skill picks up where the last one stopped.
  24. ## Start here by situation
  25. | Your situation | Skills, in order | Say this first |
  26. |---|---|---|
  27. | A meeting just ended and you have the transcript or notes | `meeting-minutes` → `action-items` | "Write minutes from this transcript, then draft the follow-ups" |
  28. | The next meeting is tomorrow | `meeting-agenda` | "Prep the agenda for tomorrow's sync from what's still open" |
  29. | It's Friday and stakeholders want an update | `status-report` | "Write my Friday status update for stakeholders" |
  30. | You're starting a project and just had the kickoff | `project-charter` → `raci-matrix` → `stakeholder-map` | "Write the project charter from this kickoff transcript" |
  31. | You just took over a project | `raid-log` → `decision-log` → `meeting-agenda` | "Read these docs and start a RAID log and a decision log" |
  32. | Someone wants to add work, move a date or spend more | `change-control` | "Sales wants bulk import in v1. Write a change request with the impact" |
  33. | Nobody is sure who decides, or who needs to hear | `raci-matrix`, `stakeholder-map` | "Who's accountable for the rollout dates? Who needs to hear that billing is late?" |
  34. | Someone asks why we decided something | `decision-log` | "Why did we pick a staged launch? Show me the source" |
  35. | The standup thread is long and you need the blockers | `standup` | "Summarise today's standup: blockers first, and who can unblock them" |
  36. | You have a 1:1 coming up | `one-on-one` | "Prep my 1:1 with Sam tomorrow" |
  37. | You manage managers and meet the people on their teams | `skip-level-meeting` | "Prep my skip-level with Sam tomorrow" |
  38. | Someone new joins, or the team keeps tripping over how it works | `team-charter` | "Write up our team charter from this how-we-work talk" |
  39. | The sprint or project just ended | `retrospective` → `lessons-learned` | "Plan our sprint retro from these notes" |
  40. | You're about to do something the team has done before | `lessons-learned` | "Have we run a launch like this before? What did we learn?" |
  41. | It's morning and you don't know where to start | `morning-brief` | "Brief me" |
  42. Each skill reads what the earlier ones saved, so the second step needs no copying. An empty folder is fine to start with: the first skill asks once before it saves anything.
  43. [Worked examples on one demo project](#one-demo-project-every-skill) show the output of every skill.
  44. ## The skills
  45. | Skill | What it does | Say something like |
  46. |---|---|---|
  47. | [meeting-minutes](skills/meeting-minutes/SKILL.md) | Turns a transcript or notes into minutes: decisions accepted and not accepted, action items with owners and dates, risks, open questions, and a recap message | "Write minutes from this Zoom transcript" |
  48. | [meeting-agenda](skills/meeting-agenda/SKILL.md) | Builds an agenda from what's open: overdue actions, decisions due for a revisit, risks, leftovers from last time. Each item gets an outcome, a lead and a time box. Kickoff agendas too | "Prep the agenda for Tuesday's sync" |
  49. | [decision-log](skills/decision-log/SKILL.md) | Keeps a decision register: records decisions, finds past ones with their source, flags contradictions and decisions due for a revisit | "Why did we pick a staged launch?" |
  50. | [action-items](skills/action-items/SKILL.md) | One action list across meetings: who does what by when, what's overdue, polite follow-ups. Creates tracker tickets with the meeting context, after you confirm | "What's overdue, and turn these into Jira tickets" |
  51. | [raid-log](skills/raid-log/SKILL.md) | RAID log / risk register: risks, assumptions, issues and dependencies, each with an owner, a mitigation and a "what changed" review | "Update the RAID log from this week's notes" |
  52. | [status-report](skills/status-report/SKILL.md) | Weekly project status report with an honest RAG status, built from the record. Also rolls several projects up into one page | "Write my Friday update for stakeholders" |
  53. | [one-on-one](skills/one-on-one/SKILL.md) | 1:1 prep and notes with your reports or your manager, in a private running doc per person | "Prep my 1:1 with Sam" |
  54. | [standup](skills/standup/SKILL.md) | Async standup summary with blockers first and who can unblock them, plus work that hasn't moved | "Summarise today's standup thread" |
  55. | [retrospective](skills/retrospective/SKILL.md) | Sprint retros, project post-mortems and lessons learned, grounded in what happened. Ends with a few owned actions the next retro checks | "Plan our sprint retro" |
  56. | [morning-brief](skills/morning-brief/SKILL.md) | One page of what needs you today: decide, unblock, do, plus prep for today's meetings. Reads your files and connected tools, never writes to them | "Brief me" |
  57. | [project-charter](skills/project-charter/SKILL.md) | Writes the project charter from the kickoff: goal, measurable success, scope in and out, milestones, who decides. Seeds the RAID log, decisions and first actions | "Write the project charter from this kickoff transcript" |
  58. | [change-control](skills/change-control/SKILL.md) | Turns "can we also add…" into a change request with the impact on scope, dates, money, people and risks. Keeps the change log and updates the plan once the owner decides | "Sales wants SSO in v1. Write a change request" |
  59. | [raci-matrix](skills/raci-matrix/SKILL.md) | RACI matrix with one accountable person per row, built from who actually does and decides the work. Flags gaps and bottlenecks | "Who's accountable for the rollout dates?" |
  60. | [stakeholder-map](skills/stakeholder-map/SKILL.md) | Stakeholder map and communication plan: who cares, who has sway, who gets which update and how often | "Who needs to hear that billing is late?" |
  61. | [lessons-learned](skills/lessons-learned/SKILL.md) | Lessons learned register and closure report. Brings the right lessons back when the next project starts, and says what came of past decisions | "What did we learn from the last launch?" |
  62. | [team-charter](skills/team-charter/SKILL.md) | Team charter and working agreements: what the team is for and owns, how it decides, its agreements and meetings. The retro checks that the agreements still hold | "Write up our team charter from this transcript" |
  63. | [skip-level-meeting](skills/skip-level-meeting/SKILL.md) | Skip-level prep and private notes, then the themes of a round without names, and what to take back to the lead | "Prep my skip-level with Sam tomorrow" |
  64. ## Which project manager skills they cover
  65. Most lists of project manager skills agree on the same core: communication, risk management, planning, leadership, problem solving, time management and fluency with tools. PMI groups them into ways of working, power skills and business acumen. These skills take over the routine part of each one. You keep the judgment, the relationships and the final say.
  66. | Project manager skill | What the agent does for you |
  67. |---|---|
  68. | Communication and stakeholder updates | `stakeholder-map` decides who hears what, how and how often. `status-report` writes the weekly update for the team, stakeholders or executives, with an honest RAG status and what you need from the reader. `meeting-minutes` drafts the recap message. Nothing is sent without your yes |
  69. | Risk management | `raid-log` keeps the RAID log (risk register, issue log, assumptions, dependencies), each row with an owner and a real mitigation, and prepares the top risks for a steering meeting |
  70. | Meeting facilitation | `meeting-agenda` builds the agenda from what is still open, with an outcome, a lead and a time box per item. `meeting-minutes` records what was decided and who does what |
  71. | Decision making and governance | `decision-log` records what was decided, by whom and why, what was turned down, and when to revisit it. It answers "why did we decide X?" with the source |
  72. | Organization and follow-through | `action-items` keeps one list of owners and due dates across meetings, drafts follow-ups and creates tracker tickets with the meeting context after you confirm |
  73. | Project planning and scope | `project-charter` writes the charter from the kickoff: goal, measurable success, scope in and out, milestones and who decides. `meeting-agenda` plans the kickoff itself |
  74. | Change control and scope creep | `change-control` turns each request into a change request with its impact, keeps the change log, and updates the plan only after the person with the right to decide says yes |
  75. | Roles and responsibilities (RACI) | `raci-matrix` builds the RACI matrix, one accountable person per row, and answers "who decides on X?" |
  76. | Time management and prioritization | `morning-brief` shows what needs you today: what to decide, unblock and do |
  77. | Agile ceremonies | `standup` puts blockers first and spots work that hasn't moved. `retrospective` plans the retro and ends with a few owned actions |
  78. | Leadership and coaching | `one-on-one` prepares 1:1s and keeps a private running doc per person. `skip-level-meeting` prepares skip-levels with the people on your leads' teams and brings back themes without names |
  79. | Team building and ways of working | `team-charter` writes the team charter and working agreements from the team's own words, and the retro checks that they still hold |
  80. | Lessons learned and project closeout | `retrospective` runs post-mortems from what actually happened. `lessons-learned` keeps the lessons register, writes the closure report, and brings the right lessons back when the next project starts |
  81. | Reporting to leadership across projects | `status-report` rolls several projects or teams into one page, red and amber first |
  82. | Tool and AI fluency | The skills run in Claude Code, Claude Cowork, claude.ai and Codex, and work with Jira, Linear, Asana, Trello or GitHub Issues when they are connected |
  83. **Not covered yet:** scheduling, the work breakdown structure and Gantt charts, budgeting and cost control, resource and capacity planning, vendor management and quality acceptance. Issues and pull requests are welcome.
  84. **Stays with you:** negotiation, conflict, adaptability and the relationships behind every update. The agent brings you the facts, and you make the call.
  85. ### What are the most important project manager skills?
  86. Communication comes first on almost every list, followed by risk management, planning, leadership, problem solving and adaptability. Budgeting, agile methods and fluency with tools, now including AI, round out the core. Agents already do a large share of the routine around the first three: reports, minutes, follow-ups and spotting risks. The judgment and the relationships stay with the project manager. The table above shows which skill takes over which part.
  87. ## What the output looks like
  88. From [a 32-minute weekly sync transcript](demo/weekly-sync-transcript.md), `meeting-minutes` writes [these minutes](demo/after/meetings/2026-11-17-weekly-sync.md) and starts the [decision log](demo/after/DECISIONS.md) and the [action list](demo/after/ACTIONS.md):
  89. > **D-001 Accepted:** Launch the new onboarding to 10% of new sign-ups on 2026-12-01 and to everyone on 2026-12-15. Decided by Maya, Leo, Priya. Why: avoid both waves of support tickets in pricing week. Revisit 2026-12-08, before going to 100%.
  90. >
  91. > **D-002 Not accepted:** Move the whole launch to January. Why not: sales already promised December to two accounts.
  92. >
  93. > | A-001 | Write the rollout note for support | Priya | 2026-11-19 |
  94. >
  95. > **Open question:** Who updates the help center articles for the new onboarding? No owner yet.
  96. ### One demo project, every skill
  97. Each skill has a worked example on the same made-up launch, in the order the project runs: the kickoff, one launch week, the weeks after it, and the review after the launch. Each one shows the request, the reply and the files written.
  98. | Day | What happened | Example |
  99. |---|---|---|
  100. | Oct 5 | The kickoff transcript becomes the project charter | [project-charter](skills/project-charter/examples/charter-from-kickoff.md) |
  101. | Mon | Sprint retro, from the plan to the write-up | [retrospective](skills/retrospective/examples/sprint-retro.md) |
  102. | Tue | Weekly sync transcript becomes minutes, decisions and actions | [meeting-minutes](skills/meeting-minutes/examples/weekly-sync.md) |
  103. | Tue | A RAID log started from the same minutes | [raid-log](skills/raid-log/examples/start-from-minutes.md) |
  104. | Wed | «Brief me» at 08:30 | [morning-brief](skills/morning-brief/examples/launch-week-brief.md) |
  105. | Wed | The Slack standup thread, blockers first | [standup](skills/standup/examples/launch-week-standup.md) |
  106. | Wed | Prep for a 1:1 with an engineer stuck waiting on legal | [one-on-one](skills/one-on-one/examples/prep-with-sam.md) |
  107. | Fri | A decision from the PM's notes, then «why did we…?» | [decision-log](skills/decision-log/examples/log-and-ask.md) |
  108. | Fri | The action list updated from the week's notes | [action-items](skills/action-items/examples/friday-update.md) |
  109. | Fri | The status report for a VP and a sales lead | [status-report](skills/status-report/examples/friday-status.md) |
  110. | Fri | Next Tuesday's agenda, built from what's still open | [meeting-agenda](skills/meeting-agenda/examples/next-sync-agenda.md) |
  111. | Fri | Sales asks for more in the December release: a change request, then the decision | [change-control](skills/change-control/examples/scope-change-request.md) |
  112. | Fri | A RACI built from the folder, then «who decides…?» | [raci-matrix](skills/raci-matrix/examples/raci-from-records.md) |
  113. | Fri | The stakeholder map and communication plan, then «who needs to hear?» | [stakeholder-map](skills/stakeholder-map/examples/communication-plan.md) |
  114. | Nov 24 | After the sync, a how-we-work talk becomes the team charter | [team-charter](skills/team-charter/examples/charter-from-session.md) |
  115. | Dec 2–3 | The VP's skip-levels with two engineers: prep, private notes, and themes to take back to the lead | [skip-level-meeting](skills/skip-level-meeting/examples/round-with-themes.md) |
  116. | Dec 18 | Lessons from the retro and the launch review, and what came of the staged launch | [lessons-learned](skills/lessons-learned/examples/lessons-from-retro.md) |
  117. ## Install
  118. ### Claude Code
  119. ```
  120. /plugin install project-manager-skills --marketplace numal-ai/project-manager-skills
  121. ```
  122. On Claude Code older than 2.1.275, add the marketplace first:
  123. ```
  124. /plugin marketplace add numal-ai/project-manager-skills
  125. /plugin install project-manager-skills@numal
  126. ```
  127. All seventeen add about 2,900 tokens to each session (their names and descriptions). A skill's full text loads only when you use it.
  128. Want only some of the skills? Each one is also its own plugin, about 150 to 200 tokens each. Install the full set or single skills, not both, or each skill shows up twice.
  129. ```
  130. /plugin install meeting-minutes --marketplace numal-ai/project-manager-skills
  131. /plugin install meeting-agenda --marketplace numal-ai/project-manager-skills
  132. /plugin install decision-log --marketplace numal-ai/project-manager-skills
  133. /plugin install action-items --marketplace numal-ai/project-manager-skills
  134. /plugin install raid-log --marketplace numal-ai/project-manager-skills
  135. /plugin install status-report --marketplace numal-ai/project-manager-skills
  136. /plugin install one-on-one --marketplace numal-ai/project-manager-skills
  137. /plugin install standup --marketplace numal-ai/project-manager-skills
  138. /plugin install retrospective --marketplace numal-ai/project-manager-skills
  139. /plugin install morning-brief --marketplace numal-ai/project-manager-skills
  140. /plugin install project-charter --marketplace numal-ai/project-manager-skills
  141. /plugin install change-control --marketplace numal-ai/project-manager-skills
  142. /plugin install raci-matrix --marketplace numal-ai/project-manager-skills
  143. /plugin install stakeholder-map --marketplace numal-ai/project-manager-skills
  144. /plugin install lessons-learned --marketplace numal-ai/project-manager-skills
  145. /plugin install team-charter --marketplace numal-ai/project-manager-skills
  146. /plugin install skip-level-meeting --marketplace numal-ai/project-manager-skills
  147. ```
  148. Or copy single skills into your skills folder:
  149. ```bash
  150. git clone https://github.com/numal-ai/project-manager-skills
  151. cp -R project-manager-skills/skills/meeting-minutes ~/.claude/skills/
  152. ```
  153. ### Any agent, one command
  154. The open [skills](https://github.com/vercel-labs/skills) installer puts the skills where your agent looks for them: Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI and many others. It asks which agents and which skills.
  155. ```bash
  156. npx skills add numal-ai/project-manager-skills
  157. ```
  158. One skill only:
  159. ```bash
  160. npx skills add numal-ai/project-manager-skills --skill meeting-minutes
  161. ```
  162. ### claude.ai and Claude Cowork
  163. Download a ready ZIP from the [latest release](https://github.com/numal-ai/project-manager-skills/releases/latest):
  164. | Download | What's inside |
  165. |---|---|
  166. | [Starter pack](https://github.com/numal-ai/project-manager-skills/releases/latest/download/project-manager-skills-starter.zip) | meeting-minutes, meeting-agenda and status-report. The best first download |
  167. | [All skills](https://github.com/numal-ai/project-manager-skills/releases/latest/download/project-manager-skills-all.zip) | All seventeen |
  168. | Single skill | `https://github.com/numal-ai/project-manager-skills/releases/latest/download/<skill>.zip`, for example [meeting-minutes.zip](https://github.com/numal-ai/project-manager-skills/releases/latest/download/meeting-minutes.zip) |
  169. 1. Unzip the pack. Inside are one ZIP per skill.
  170. 2. Upload those skill ZIPs in **Customize → Skills** (on older versions, **Settings → Capabilities → Skills**). Don't upload the pack itself.
  171. 3. Start a new chat and say what you need, for example `Write minutes from this transcript`.
  172. In Cowork you can also add this repository as a plugin marketplace in **Customize → Plugins**. More in [docs/claude-cowork.md](docs/claude-cowork.md).
  173. ### OpenAI Codex
  174. Copy the skills into your personal skills folder:
  175. ```bash
  176. git clone https://github.com/numal-ai/project-manager-skills
  177. mkdir -p ~/.agents/skills
  178. cp -R project-manager-skills/skills/* ~/.agents/skills/
  179. ```
  180. Or add the repository as a plugin marketplace with `codex plugin marketplace add numal-ai/project-manager-skills`, then install **project-manager-skills** from the plugins directory.
  181. Restart Codex if the skills don't show up. Call one directly with `$meeting-minutes`.
  182. ### ChatGPT, Cursor and other agents
  183. Any tool that supports Agent Skills loads the folders in `skills/` as they are. Step-by-step guides:
  184. - [ChatGPT](docs/chatgpt.md)
  185. - [Cursor](docs/cursor.md)
  186. - [Claude Cowork](docs/claude-cowork.md)
  187. - [OpenAI Codex](docs/codex.md)
  188. ## The shared folder
  189. The skills keep their records in the folder you work in. The first time one of them wants to save something, it asks you once.
  190. ```
  191. PROJECT.md DECISIONS.md ACTIONS.md RAID.md CHANGES.md LESSONS.md TEAM.md (optional)
  192. meetings/ one-on-ones/ skip-levels/ standups/ retros/ reports/
  193. ```
  194. Formats and rules are in [docs/workspace.md](docs/workspace.md). In short:
  195. - **Nothing is invented.** Unclear items become questions or are marked `(check)`.
  196. - **Rows are never deleted.** Their status changes instead.
  197. - **IDs stay stable:** `D-001`, `A-001`, `R-001`, `CR-001`, `L-001`.
  198. ## Safety
  199. - **Nothing goes to other people without your yes.** Tracker tickets, recap messages and chat posts are first shown to you as an exact list. Tickets and messages notify people, so they are never a side effect.
  200. - **Few questions.** Everything that needs your yes comes as one list with one question. Most runs ask for none or one.
  201. - **The plan stays yours.** No skill changes dates, budget or scope on its own. `change-control` prepares the change with its impact, and the person with the right to decide makes the call.
  202. - **The morning brief is read-only.** It reads your calendar, tracker, email and chat and never acts in them.
  203. - **1:1 and skip-level notes stay private.** Nothing from `one-on-ones/` or `skip-levels/` is copied into shared files unless you ask. What leaves a skip-level leaves as a theme, without names.
  204. - **No servers, no accounts, no telemetry.** These are instructions plus Markdown files. Your data stays wherever your agent already runs.
  205. ## Templates without an agent
  206. If you'd rather fill a template by hand, these are copy-paste versions of the same formats:
  207. - [meeting recap](https://numal.ai/templates/meeting-recap?utm_source=github&utm_medium=readme&utm_campaign=project-manager-skills&utm_content=templates)
  208. - [decision log](https://numal.ai/templates/decision-log?utm_source=github&utm_medium=readme&utm_campaign=project-manager-skills&utm_content=templates)
  209. - [action items](https://numal.ai/templates/action-items?utm_source=github&utm_medium=readme&utm_campaign=project-manager-skills&utm_content=templates)
  210. - [RAID log](https://numal.ai/templates/raid-log?utm_source=github&utm_medium=readme&utm_campaign=project-manager-skills&utm_content=templates)
  211. - [project status report](https://numal.ai/templates/project-status-report?utm_source=github&utm_medium=readme&utm_campaign=project-manager-skills&utm_content=templates)
  212. - [one-on-one meeting](https://numal.ai/templates/one-on-one-meeting?utm_source=github&utm_medium=readme&utm_campaign=project-manager-skills&utm_content=templates)
  213. ## Made by Numal
  214. These skills do by hand what [Numal](https://numal.ai/?utm_source=github&utm_medium=readme&utm_campaign=project-manager-skills&utm_content=made-by) does on its own. After every team call, Numal:
  215. - records the decisions;
  216. - puts the context into the right tracker tasks once you approve;
  217. - prepares the next agenda and each manager's morning brief, across all of a company's teams.
  218. If pasting transcripts gets old, [request access](https://numal.ai/?utm_source=github&utm_medium=readme&utm_campaign=project-manager-skills&utm_content=request-access).
  219. ## Contributing
  220. Issues and pull requests are welcome, especially:
  221. - formats your team actually uses, such as other RAID variants or report layouts;
  222. - trigger phrases a skill missed;
  223. - translations.
  224. Keep each skill focused on one job, and keep `SKILL.md` readable by a person.
  225. Before you open a pull request, run `python scripts/build_zips.py --check`. It checks every skill's name and description, the plugin list and the README links, using only the Python standard library. A new skill needs an entry in `.claude-plugin/marketplace.json` and a row in the table above.
  226. ## License
  227. [MIT](LICENSE)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.