GitHub Project Management Swarm
ruvnet/agentic-flow
Manages GitHub issues and project boards with swarm coordination: issue creation and triage, issue-to-task conversion, progress tracking and stale issue cleanup.
Manages software projects end-to-end — decomposing work into tasks, tracking progress across sprints, generating status reports, and integrating with tools like Jira, Linear, GitHub Issues, and…
Install Project Management
$ npx skills add seb1n/awesome-ai-agent-skills --skill project-management -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install seb1n/awesome-ai-agent-skills project-management --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/seb1n/awesome-ai-agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/productivity-and-workflow/project-management .claude/skills/project-management && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "project-management" agent skill from https://github.com/seb1n/awesome-ai-agent-skills/tree/main/productivity-and-workflow/project-management into .claude/skills/project-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-management", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/seb1n/awesome-ai-agent-skills/tree/main/productivity-and-workflow/project-managementType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add seb1n/awesome-ai-agent-skills --skill project-management -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install seb1n/awesome-ai-agent-skills project-management --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/seb1n/awesome-ai-agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/productivity-and-workflow/project-management .agents/skills/project-management && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "project-management" agent skill from https://github.com/seb1n/awesome-ai-agent-skills/tree/main/productivity-and-workflow/project-management into .agents/skills/project-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-management", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add seb1n/awesome-ai-agent-skills --skill project-management -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install seb1n/awesome-ai-agent-skills project-management --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/seb1n/awesome-ai-agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/productivity-and-workflow/project-management .cursor/skills/project-management && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "project-management" agent skill from https://github.com/seb1n/awesome-ai-agent-skills/tree/main/productivity-and-workflow/project-management into .cursor/skills/project-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-management", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/seb1n/awesome-ai-agent-skills.git --path productivity-and-workflow/project-management--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add seb1n/awesome-ai-agent-skills --skill project-management -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install seb1n/awesome-ai-agent-skills project-management --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/seb1n/awesome-ai-agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/productivity-and-workflow/project-management .gemini/skills/project-management && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "project-management" agent skill from https://github.com/seb1n/awesome-ai-agent-skills/tree/main/productivity-and-workflow/project-management into .gemini/skills/project-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-management", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install seb1n/awesome-ai-agent-skills project-managementInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add seb1n/awesome-ai-agent-skills --skill project-management -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/seb1n/awesome-ai-agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/productivity-and-workflow/project-management .github/skills/project-management && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "project-management" agent skill from https://github.com/seb1n/awesome-ai-agent-skills/tree/main/productivity-and-workflow/project-management into .github/skills/project-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-management", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add seb1n/awesome-ai-agent-skills --skill project-management -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install seb1n/awesome-ai-agent-skills project-management --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/seb1n/awesome-ai-agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/productivity-and-workflow/project-management .opencode/skills/project-management && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "project-management" agent skill from https://github.com/seb1n/awesome-ai-agent-skills/tree/main/productivity-and-workflow/project-management into .opencode/skills/project-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-management", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
project-management- GitHub stars
- 206
- Token cost
- ~2.7k tokens
- SKILL.md length
- 941 words
- Files
- 1
- Skills in repo
- 101
- Repo updated
- First seen
- Licence
- MIT
At a glance
Manages software projects end-to-end — decomposing work into tasks, tracking progress across sprints, generating status reports, and integrating with tools like Jira, Linear, GitHub Issues, and…
- Works in 6 steps: Gather Project Context → Decompose Work into Tasks → Plan Sprints or Populate the Board → …
- The user requests project management
- SKILL.md covers Workflow, Usage, Examples and Best Practices, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Project Management is an agent skill from seb1n/awesome-ai-agent-skills. Manages software projects end-to-end — decomposing work into tasks, tracking progress across sprints, generating status reports, and integrating with tools like Jira, Linear, GitHub Issues, and Trello. Use when the user requests project management or provides relevant inputs for this workflow.
Its SKILL.md is about 2.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Product & Project Management, covering Project management, User stories and Sprint planning and agile. It works with GitHub and Jira. The repository describes itself as: 103 ready-to-use AI agent skills for Claude Code, OpenAI Codex, Gemini CLI, Cursor, GitHub Copilot, Windsurf, and other Agent Skills-compatible tools. Complete SKILL.md… The licence is MIT.
When your agent uses it
- The user requests project management
- Provides relevant inputs for this workflow
Example prompts
- “Use the project-management skill to manage software projects end-to-end — decomposing work into tasks, tracking progress across sprints, generating…”
- “/project-management”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Gather Project Context
- Decompose Work into Tasks
- Plan Sprints or Populate the Board
- Track Progress and Surface Blockers
- Manage Risks and Dependencies
- Generate Status Reports
What it can do on your machine
Read from SKILL.md and the folder at commit 75865a5. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Project Management loads about 2.7k tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 941 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from seb1n/awesome-ai-agent-skills at commit 75865a5, republished under its MIT licence (© seb1n). 941 words, ~2,693 tokens.
Download SKILL.mdSave it as
.claude/skills/project-management/SKILL.md (or your agent's skills folder).- name
- project-management
- description
- Manages software projects end-to-end — decomposing work into tasks, tracking progress across sprints, generating status reports, and integrating with tools like Jira, Linear, GitHub Issues, and Trello. Use when the user requests project management or provides relevant inputs for this workflow.
- license
- MIT
- metadata.author
- awesome-ai-agent-skills contributors
- metadata.version
- 1.1.0
Project Management
This skill enables an AI agent to serve as a project management co-pilot for software teams. It covers the full lifecycle: breaking high-level goals into actionable tasks with acceptance criteria, estimating effort in story points, organizing work into sprints or Kanban boards, tracking progress with burndown data, identifying blockers and risks, and generating stakeholder-ready status reports. The agent integrates with Jira, Linear, GitHub Issues, and Trello so that all changes are reflected in the team's actual project tracker.
Workflow
Gather Project Context Collect the project name, team roster (with roles and capacity), high-level goals, key deadlines, and the preferred methodology (Scrum, Kanban, or a hybrid). If a project tracker is already in use, connect to its API and import the current backlog, labels, and sprint configuration so the agent starts from the existing state rather than a blank slate.
Decompose Work into Tasks Break each high-level goal into epics, then into user stories, and finally into sub-tasks small enough to complete in one to two days. Write each user story in the standard format: "As a [role], I want [capability] so that [benefit]." Attach acceptance criteria as a checklist on every story. Identify dependencies between tasks and flag any that form a critical path. Assign story-point estimates using the Fibonacci scale (1, 2, 3, 5, 8, 13) based on complexity, uncertainty, and effort.
Plan Sprints or Populate the Board For Scrum teams, create a sprint with a start date, end date, and sprint goal. Pull stories from the top of the prioritized backlog until the team's velocity (historical average story points per sprint) is reached. For Kanban teams, enforce work-in-progress (WIP) limits per column and ensure the board columns match the team's workflow (e.g., Backlog → In Progress → Review → Done). Push the plan to the connected project tracker via its API.
Track Progress and Surface Blockers Poll the project tracker on a configurable interval (default: daily). Calculate burndown and cumulative-flow metrics. Detect when a task has been "In Progress" longer than its estimate and flag it as at risk. Identify dependency chains where a blocked upstream task is stalling downstream work. Post a daily digest to the team's Slack or Teams channel summarizing completed items, in-progress items, and blockers.
Manage Risks and Dependencies Maintain a risk register with each entry containing a description, likelihood (low/medium/high), impact (low/medium/high), an assigned owner, and a mitigation plan. When a new risk is identified — such as a team member going on leave or a third-party API deprecation — add it to the register and notify the project lead. Track cross-team dependencies by linking external issues and alerting when their status changes.
Generate Status Reports Produce sprint review or weekly status reports in Markdown (or export to PDF/Confluence). Each report includes: sprint goal and whether it was met, completed stories with their point total, stories carried over, burndown chart data, velocity trend over the last five sprints, top risks, and action items for the next period. Tailor the level of detail to the audience — executives get a one-page summary, the team gets the full breakdown.
Usage
Provide the agent with your project details and what you need. The agent adapts to your methodology and tooling.
"Create a sprint plan for the TaskMaster mobile app. We're a team of 4 with a velocity of 34 points. Sprint starts Monday and runs two weeks. Pull from the existing backlog in Linear.""Generate a weekly status report for Project Atlas. Include burndown, completed items, and open risks.""Break down this feature into user stories with acceptance criteria: 'Users should be able to export their data in CSV and JSON formats.'""Add a risk to the register: 'Payment provider is deprecating API v2 on March 1. We need to migrate to v3.'"Examples
Example 1 — Creating a Sprint Plan with User Stories
User input:
"Plan sprint 12 for the Lumen project. Sprint goal: launch the notifications feature. Team: Alice (frontend, 8 pts capacity), Bob (backend, 10 pts), Carol (fullstack, 8 pts). Two-week sprint starting Feb 17."Agent output:
## Sprint 12 — Lumen
**Goal:** Launch the notifications feature
**Dates:** Feb 17 – Feb 28, 2025
**Team capacity:** 26 story points
### Selected Stories (26 pts)
| ID | Story | Points | Assignee | Depends On |
|--------|-----------------------------------------------------|--------|----------|------------|
| LUM-41 | As a user, I want to receive in-app notifications | 5 | Alice | — |
| LUM-42 | As a user, I want to receive push notifications | 8 | Bob | LUM-41 |
| LUM-43 | As a user, I want to configure notification prefs | 3 | Alice | LUM-41 |
| LUM-44 | Build notification service with WebSocket delivery | 8 | Bob | — |
| LUM-45 | As a user, I want to see a notification history page | 5 | Carol | LUM-44 |
| LUM-46 | Write integration tests for notification flow | 3 | Carol | LUM-42 |
### Acceptance Criteria (example — LUM-42)
- [ ] Push notification is delivered to iOS and Android within 5 seconds
- [ ] Notification payload includes title, body, and deep-link URL
- [ ] Notifications respect the user's quiet-hours setting
- [ ] Failed deliveries are retried up to 3 times with exponential backoff
### Dependencies
LUM-42 → LUM-41 (push requires in-app infrastructure)
LUM-45 → LUM-44 (history page reads from notification service)
LUM-46 → LUM-42 (integration tests cover push path)
Sprint pushed to Linear. Slack channel #lumen-dev notified.Example 2 — Generating a Project Status Report with Burndown Data
User input:
"Generate the sprint 11 retrospective report for Project Atlas. We use GitHub Issues."Agent output:
## Project Atlas — Sprint 11 Status Report
**Sprint dates:** Feb 3 – Feb 14, 2025
**Sprint goal:** Complete user profile redesign — ✅ Met
### Summary
- **Planned:** 30 story points across 9 stories
- **Completed:** 28 story points (8 stories)
- **Carried over:** 1 story (ATLAS-87, 2 pts — blocked by design review)
### Burndown Data
| Day | Ideal Remaining | Actual Remaining |
|-----------|-----------------|------------------|
| Feb 3 | 30 | 30 |
| Feb 4 | 27 | 28 |
| Feb 5 | 24 | 25 |
| Feb 6 | 21 | 22 |
| Feb 7 | 18 | 18 |
| Feb 10 | 15 | 14 |
| Feb 11 | 12 | 10 |
| Feb 12 | 9 | 6 |
| Feb 13 | 6 | 4 |
| Feb 14 | 0 | 2 |
### Velocity Trend (last 5 sprints)
Sprint 7: 24 pts | Sprint 8: 28 pts | Sprint 9: 26 pts | Sprint 10: 30 pts | Sprint 11: 28 pts
**Average velocity:** 27.2 pts
### Open Risks
| Risk | Likelihood | Impact | Owner | Mitigation |
|---------------------------------------|------------|--------|--------|-----------------------------------|
| Design system migration incomplete | Medium | High | Alice | Parallel-run old and new systems |
| Third-party image CDN latency spikes | Low | Medium | Bob | Add fallback CDN configuration |
### Action Items
1. Complete design review for ATLAS-87 by Feb 17 (owner: Carol)
2. Schedule performance testing for new profile page (owner: Bob)
3. Update onboarding docs to reflect profile redesign (owner: Alice)Show full SKILL.md (377 more words)Show less
Best Practices
- Keep stories small and testable. Any story estimated above 8 points should be split. Large stories hide complexity and make progress tracking unreliable.
- Write acceptance criteria before development begins. Criteria remove ambiguity, serve as the basis for test cases, and give the team a shared definition of "done."
- Respect velocity — do not overcommit. Use the team's trailing three-sprint average as the capacity ceiling. Overloaded sprints lead to carryover and demoralize the team.
- Make blockers visible immediately. Surface blocked tasks in daily digests and tag the person who can unblock them. A blocker that sits unreported for days is a silent schedule risk.
- Maintain a living risk register. Review risks at every sprint planning meeting. Close risks that are no longer relevant and add new ones as they emerge. A stale risk register provides false confidence.
- Automate report generation. Manually assembling status reports is error-prone and time-consuming. Use the agent to pull data directly from the project tracker so reports are always accurate and consistent.
Edge Cases
- Empty backlog. If no stories exist when a sprint plan is requested, prompt the user to create or import stories before planning. Do not create a sprint with zero items.
- Team member at zero capacity. If a team member is on leave for the entire sprint, exclude them from assignment but keep them listed as a reviewer or stakeholder if applicable. Adjust total capacity accordingly.
- Circular dependencies. If task A depends on B and B depends on A, flag the cycle and ask the user to resolve it before planning proceeds. Never silently schedule mutually blocking tasks.
- Tracker API outage. If the project tracker API is unreachable, generate the plan in Markdown locally and queue the sync for when the API recovers. Inform the user that changes are saved locally but not yet pushed.
- Mid-sprint scope changes. If a new high-priority item is added mid-sprint, warn the user about the impact on the sprint goal and suggest which existing item to deprioritize to make room. Log the scope change in the sprint report.
- Cross-project dependencies. When a task depends on work owned by another team or project, create a linked external reference and set up a webhook or polling check to notify the team when the dependency is resolved.
© seb1n, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in productivity-and-workflow/project-management of seb1n/awesome-ai-agent-skills.
Open the folder on GitHubat commit 75865a5
Compare with similar skills
Project Management next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Project Management this skillseb1n/awesome-ai-agent-skills | 206 | — | ~2.7k | Automated safety check: Pass | MIT | |
| GitHub Project Management Swarmruvnet/agentic-flow | 819 | 6 repos | ~7.1k | Automated safety check: Pass | None | |
| Bmad Sprint Planningdelorenj/mcp-server-trello | 445 | 5 repos | ~3k | Automated safety check: Pass | MIT | |
| Daily Meeting Updatedavila7/claude-code-templates | 32k | 2 repos | ~3k | Automated safety check: Pass | MIT | |
| Create User Storyhuytieu/COG-second-brain | 1.3k | — | ~2k | Automated safety check: Pass | MIT | |
| Product Roadmaptikalk/adlc-team-skills | 141 | — | ~3.1k | Automated safety check: Pass | MIT |
Similar skills
Bmad Sprint Planning
delorenj/mcp-server-trello
Generate sprint status tracking from epics. An agent skill from delorenj/mcp-server-trello.
Daily Meeting Update
davila7/claude-code-templates
Interactive daily standup/meeting update generator. An agent skill from davila7/claude-code-templates.
Create User Story
huytieu/COG-second-brain
Create user stories with duplicate checking across any project tracker (Linear, GitHub Issues, Jira)
Product Roadmap
tikalk/adlc-team-skills
A skill your agent uses when doing weekly progress checks or milestone validation — tracks decision, execution, evidence, and gate states across four layers of truth.
Plan Create Stories
coleam00/skills
Decomposes a PRD into well-formed, engineer-ready tickets — Jira issues or GitHub issues.
More from seb1n/awesome-ai-agent-skills
All 101 skills in this repoAgent Red Teaming
seb1n/awesome-ai-agent-skills
Plan, execute, document, and retest authorized security assessments of AI agents and multi-agent workflows using safe adversarial cases, synthetic identities, canaries, and evidence-based findings.
Eu AI Act Readiness
seb1n/awesome-ai-agent-skills
Build a preliminary, evidence-based EU AI Act readiness assessment across AI-system inventory, territorial scope, operator roles, prohibited-practice screening, risk classification, transparency…
Human In The Loop
seb1n/awesome-ai-agent-skills
Design and verify auditable human oversight, approval gates, escalation paths, and safe state transitions for AI agent workflows.
MCP Server Building
seb1n/awesome-ai-agent-skills
Design, implement, harden, and verify Model Context Protocol (MCP) servers with precise tool contracts, least-privilege authorization, safe transports, structured errors, and interoperability tests.
PDF Processing
seb1n/awesome-ai-agent-skills
Inspect, extract, OCR, create, merge, split, reorder, rotate, annotate, fill, redact, compress, secure, and verify PDF documents while preserving source files and visual fidelity.
Skill Supply Chain Audit
seb1n/awesome-ai-agent-skills
Audit agent skills, plugins, prompts, manifests, scripts, dependencies, and bundled assets for provenance, prompt-injection, permission, execution, exfiltration, persistence, and update risk.
Related
Categories
Questions about Project Management
What does Project Management do?
Manages software projects end-to-end — decomposing work into tasks, tracking progress across sprints, generating status reports, and integrating with tools like Jira, Linear, GitHub Issues, and…. Project Management is an agent skill from seb1n/awesome-ai-agent-skills. Manages software projects end-to-end — decomposing work into tasks, tracking progress across sprints, generating status reports, and integrating with tools like Jira, Linear, GitHub Issues, and Trello.
When should I use Project Management?
Project Management fits situations like: the user requests project management; provides relevant inputs for this workflow.
How do I install Project Management in Claude Code?
Run `npx skills add seb1n/awesome-ai-agent-skills --skill project-management -a claude-code`. Or copy the skill folder (productivity-and-workflow/project-management in seb1n/awesome-ai-agent-skills) into .claude/skills/project-management in your project. Claude Code loads it when a task matches its description.
How do I install Project Management in Codex?
Run `npx skills add seb1n/awesome-ai-agent-skills --skill project-management -a codex`. Or copy the skill folder (productivity-and-workflow/project-management in seb1n/awesome-ai-agent-skills) into .agents/skills/project-management in your project. Codex loads it when a task matches its description.
Can I use Project Management in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add seb1n/awesome-ai-agent-skills --skill project-management -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/project-management, .gemini/skills/project-management, .github/skills/project-management and .opencode/skills/project-management in your project.
What does Project Management need to run?
SKILL.md names no scripts, command-line tools or credentials: Project Management is instructions for the agent only.
Does Project Management access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Project Management safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Project Management use?
Project Management is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Project Management use?
About 2.7k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Project Management?
Skills that share tags, products or a category with Project Management: GitHub Project Management Swarm (ruvnet/agentic-flow, 819 stars), Bmad Sprint Planning (delorenj/mcp-server-trello, 445 stars), Daily Meeting Update (davila7/claude-code-templates, 32k stars) and Create User Story (huytieu/COG-second-brain, 1.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Project Management?
seb1n (a GitHub user) maintains it in seb1n/awesome-ai-agent-skills, which has 206 GitHub stars. The repository holds 101 skills in this directory. The repository was last updated on August 9, 2026.
Source: seb1n/awesome-ai-agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.