Project Manager Skill
A single SKILL.md for ChatGPT that drives a project through small milestones, exact-build testing, fixes and a Space log
- 157 ★ on the repository
- Last commit
Minimal access
Why this level
- The skill is text instructions and runs nothing itself
- It drives work through the tools and Space you connected, so limit their permissions
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/project-manager-skillDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- The skill is text instructions and runs nothing itself
- It drives work through the tools and Space you connected, so limit their permissions
This is third-party code. Review the repository files before installing.
What it does
Project Manager Skill is a self-contained skill in a single `SKILL.md` file for ChatGPT. It takes the role of a project manager for an app, game or program. It agrees the vision with you, slices the work into small milestones, hands the task to an existing implementation thread, then independently tests the exact built version and runs a fix-and-retest loop. The project log is kept in a private Space (a ChatGPT workspace): progress, decisions, screenshots and versioned test evidence. For testing the skill uses separate QA workers if available, otherwise it requires a separately reported test pass. It is called with the `@project-manager` mention: describe the project, desired outcome, existing implementation thread and Space. The skill supplies only the workflow, not tools, access rights or unattended execution. Publishing, production deployment, merging, spending and account changes need separate authorization.
Who it is for. Founders and product leads who run app or game development through ChatGPT and need discipline in milestones and testing.
Good fit when
- Development runs in a separate ChatGPT thread and you need a lead who slices work into small milestones
- After every build you want an independent check of that exact version, not a general impression
- Decisions, screenshots and test evidence must live in one private Space
- You need a controlled loop: found a bug, fixed it, rechecked
Not a fit when
- You need a tool that writes and deploys code itself: the skill only drives the process and uses tools you connected
- You have no access to a Space, repository or build environment: without them part of the scenario cannot run
- You need Claude Code or Cursor support with project files: the skill targets ChatGPT
Example request
@project-manager Manage this app through the agreed milestones. Use my existing implementation thread, test each exact build and keep the Space currentLimitations
Installation and invocation depend on skill support in your ChatGPT environment. The skill gives no tools itself: the repository, implementation thread, build and testing need connected and authorized tools, while screenshots, artifact transfer and evidence storage need matching capabilities.
Maintaining a Space needs access to it and editing tools. Separate QA workers are used only if available. The skill must report unfinished or untested criteria explicitly. The repository has no license, so check reuse terms with the author.
How to disable. Ask ChatGPT to remove the `project-manager` skill in the skill settings. Entries created in the Space stay in your workspace.
FAQ
How do I install the skill?
Download `SKILL.md`, upload it to ChatGPT and ask to install it as `project-manager`. Invoke it with the `@project-manager` mention.
Are scripts or dependencies needed?
No, the whole workflow is in a single `SKILL.md` and no companion scripts are required.
Who tests the builds?
Separate QA workers if available. Otherwise a separately reported test pass of the exact build is required.
What will the skill not do without permission?
Publishing, production deployment, merging, spending and account changes. Each step needs separate user confirmation.
What is stored in the Space?
Progress, decisions, screenshots and versioned test evidence. The Space must be private and accessible to the agent.
Discussion
No questions or reviews yet.
Related
SkillsProject Interview Skill turns a repository into a source-code course with resume points and interview questions.
A spec-driven delivery skill: PRDs, epics, tasks, GitHub Issues sync and parallel agents in git worktrees
Table Skills: project-handoff
Table Skills (project-handoff)
The project-handoff skill saves goals, decisions and the next step to PROJECT_STATE.md for a fresh Codex or Claude Code session
ProductMind Skills gives an agent 17 skills where the product decision comes before code: feature vetting, MVP or SLC, pricing.
PM Skills
PM Skills Marketplace
A plugin marketplace for product managers: discovery, strategy, PRDs, launch, growth and audits of AI-built code
A skill that keeps project memory in plain Markdown files: session logs, a wiki, rules, a to-do list and a note on where to resume
README in short
The repository has two files: a README and `SKILL.md`. The README describes installation, invocation and limits: connected tools, Space access and testing capabilities are required. The author stresses that the skill sets a workflow and does not replace tools.
README badge
Original SKILL.md
--- name: project-manager description: Manage an authorized software, app, or game project from the user's vision through small milestones, an existing implementation thread, independent exact-build testing, and fix-and-retest loops. Maintain the requested private project Space with progress, decisions, screenshots, and versioned QA evidence. Use when asked to manage or drive a project to completion; a status-only question does not authorize code changes or ongoing work. --- # Project Manager Drive the authorized project toward the user's agreed outcome. Own coordination, acceptance, and evidence. Keep implementation in the user's selected thread and environment, and keep the user informed at meaningful checkpoints while continuing work between them. This file contains the complete workflow; no companion files, proprietary tool names, or bundled scripts are required. Adapt operations to the capabilities actually available. Do not claim this workflow is proven merely because it is installed; improve it using observed complete build–test–fix–retest loops. ## 1. Check capabilities and establish the project contract Before promising execution, inspect the tools and access actually available for: - Reading project context, repositories, branches, and existing implementation threads. - Messaging or continuing the selected implementation thread in its selected environment. - Building, transferring, identifying, launching, and independently exercising the product. - Capturing screenshots, recordings, logs, and durable evidence the user can access. - Reading and safely updating the requested project Space, including its media and permissions. Use available tool documentation and relevant engineering, environment, testing, and document guidance. This skill does not grant tools, credentials, computer access, or permission. Verify connection and authorization separately; a disconnected, unsupported, and access-denied capability are different blockers. Never bypass an access denial through another route. Recover the latest request, vision, selected implementation thread, repository, branch, environment, build entry point, and existing Space from authorized sources before asking the user to repeat them. Separate current evidence from historical reports. Record project-specific facts in the project record, never in this reusable skill. Write the project contract in the user's terms: - Intended audience and essential experience. - Required features and quality b