CCPM Project Management
automazeio/ccpm
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
Create a GitHub milestone for an upcoming release. An agent skill from agentic-community/mcp-gateway-registry.
$ npx skills add agentic-community/mcp-gateway-registry --skill create-milestone -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install agentic-community/mcp-gateway-registry create-milestone --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/agentic-community/mcp-gateway-registry.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/create-milestone .claude/skills/create-milestone && 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 "create-milestone" agent skill from https://github.com/agentic-community/mcp-gateway-registry/tree/main/.claude/skills/create-milestone into .claude/skills/create-milestone/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-milestone", 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/agentic-community/mcp-gateway-registry/tree/main/.claude/skills/create-milestoneType 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 agentic-community/mcp-gateway-registry --skill create-milestone -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install agentic-community/mcp-gateway-registry create-milestone --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agentic-community/mcp-gateway-registry.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/create-milestone .agents/skills/create-milestone && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "create-milestone" agent skill from https://github.com/agentic-community/mcp-gateway-registry/tree/main/.claude/skills/create-milestone into .agents/skills/create-milestone/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-milestone", 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 agentic-community/mcp-gateway-registry --skill create-milestone -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install agentic-community/mcp-gateway-registry create-milestone --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agentic-community/mcp-gateway-registry.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/create-milestone .cursor/skills/create-milestone && 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 "create-milestone" agent skill from https://github.com/agentic-community/mcp-gateway-registry/tree/main/.claude/skills/create-milestone into .cursor/skills/create-milestone/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-milestone", 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/agentic-community/mcp-gateway-registry.git --path .claude/skills/create-milestone--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 agentic-community/mcp-gateway-registry --skill create-milestone -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install agentic-community/mcp-gateway-registry create-milestone --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agentic-community/mcp-gateway-registry.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/create-milestone .gemini/skills/create-milestone && 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 "create-milestone" agent skill from https://github.com/agentic-community/mcp-gateway-registry/tree/main/.claude/skills/create-milestone into .gemini/skills/create-milestone/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-milestone", 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 agentic-community/mcp-gateway-registry create-milestoneInstalls 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 agentic-community/mcp-gateway-registry --skill create-milestone -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/agentic-community/mcp-gateway-registry.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/create-milestone .github/skills/create-milestone && 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 "create-milestone" agent skill from https://github.com/agentic-community/mcp-gateway-registry/tree/main/.claude/skills/create-milestone into .github/skills/create-milestone/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-milestone", 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 agentic-community/mcp-gateway-registry --skill create-milestone -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install agentic-community/mcp-gateway-registry create-milestone --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agentic-community/mcp-gateway-registry.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/create-milestone .opencode/skills/create-milestone && 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 "create-milestone" agent skill from https://github.com/agentic-community/mcp-gateway-registry/tree/main/.claude/skills/create-milestone into .opencode/skills/create-milestone/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-milestone", 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.
create-milestoneCreate a GitHub milestone for an upcoming release. An agent skill from agentic-community/mcp-gateway-registry.
Create Milestone is an agent skill from agentic-community/mcp-gateway-registry. Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.
Its SKILL.md is about 3.5k 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. It works with GitHub. The repository describes itself as: Enterprise-ready MCP Gateway & Registry that centralizes AI development tools with secure OAuth authentication, dynamic tool discovery, and unified access for both autonomous AI… The licence is Apache-2.0.
10 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit ec3a197. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
ghgitFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
github.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Create Milestone loads about 3.5k tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 1,113 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.
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.
The full file from agentic-community/mcp-gateway-registry at commit ec3a197, republished under its Apache-2.0 licence (© agentic-community). 1,113 words, ~3,473 tokens.
.claude/skills/create-milestone/SKILL.md (or your agent's skills folder).Use this skill when the user wants to plan and create a GitHub milestone for an upcoming release. The skill identifies what has changed since a baseline release, presents a draft for approval, and creates the milestone with all approved items.
Supports creating multiple milestones in sequence (e.g., v1.0.20, v1.0.21) by letting the user choose the baseline and which items belong to which release.
The skill accepts optional parameters:
/create-milestone [VERSION] [DATE] [NOTES]v1.0.20). If not provided, suggest based on latest release.2026-04-21). If not provided, ask the user..scratchpad/{version}-release-notes.md with detailed release notesGather the current state of releases and milestones:
# Get recent releases (tags + dates)
gh release list --limit 10 --json tagName,publishedAt,name \
--jq '.[] | "\(.tagName)\t\(.publishedAt)\t\(.name)"'
# Get existing milestones (to avoid duplicates and show what's already planned)
gh api repos/{owner}/{repo}/milestones --jq '.[] | "\(.number)\t\(.title)\t\(.due_on)\t\(.open_issues)\t\(.closed_issues)"'
# Git tags for reference
git tag --sort=-v:refname | grep '^v[0-9]' | head -10Present findings and ask the user to specify:
Example prompt:
Current state:
- Latest release: v1.0.19 (published April 14, 2026)
- Existing milestones: v1.0.19 (due Apr 14, 30 closed / 3 open)
Suggested next milestone: v1.0.20
Questions:
1. What version? (default: v1.0.20)
2. What is the target release date?
3. Which release should I diff from? (default: v1.0.19, the latest)
- Other options: v1.0.18, v1.0.17, v1.0.16, ...
4. Any theme or notes? (e.g., "external registry federation")Baseline flexibility: The user may say:
Wait for the user to respond before proceeding. Do not create anything until the user confirms.
Once the user confirms version, date, and baseline, gather all changes:
# Get the baseline release publish timestamp for precise cutoff
RELEASE_DATE=$(gh release view {baseline_version} --json publishedAt --jq '.publishedAt')
# List all PRs merged after the baseline release
gh pr list --state merged --search "merged:>=$RELEASE_DATE" \
--json number,title,mergedAt,body --limit 100 \
--jq '.[] | "\(.number)\t\(.mergedAt)\t\(.title)"'
# Get all commits since the baseline tag
git log {baseline_version}..HEAD --oneline
# Also get open PRs that might be targeting this release
gh pr list --state open --json number,title --limit 30 \
--jq '.[] | "\(.number)\t\(.title)"'For each merged PR, extract linked issue numbers from:
(#123), (#123, #456)Fixes #123, Closes #123, Resolves #123# For each PR, get the body and extract issue references
gh pr view {pr_number} --json title,body \
--jq '{title: .title, body: (.body // "" | split("\n")[0:10] | join("\n"))}'Build a mapping of PR -> Issues.
Check which items are already assigned to existing milestones:
# For each candidate item, check if it already has a milestone
gh api repos/{owner}/{repo}/issues/{number} --jq '.milestone.title // "none"'If an item is already assigned to a different milestone, mark it in the draft so the user can decide. Do not silently skip items.
Present the draft to the user with two tables and clear guidance on what to include/exclude.
Start with a default recommendation: Proactively offer to include all closed issues and merged PRs since the baseline as the starting point. This saves the user from having to say "pick everything." Frame it as:
I found {N} merged PRs and {M} related issues since {baseline_version}.
Want me to include all of them as a starting point?
You can then add or remove specific items.If the user says yes (or "pick everything", "include all", "yes go ahead"), proceed with the full list. If they want to be selective, present the tables for cherry-picking.
Draft format:
Here's what I found since {baseline_version} ({N} PRs merged, {M} issues referenced):
Items already in other milestones are marked with [in {milestone}].
## Issues ({count})
| # | Title | Status | Notes |
|---|-------|--------|-------|
| #814 | Add GitHub private repo auth env vars | Open | |
| #660 | Support authenticated GitHub access | Open | |
| #764 | Disable demo server auto-registration | Closed | [in v1.0.19] |
...
## Pull Requests ({count})
| # | Title | Status | Notes |
|---|-------|--------|-------|
| #782 | feat: GitHub private repo auth | Open | |
| #820 | fix: search pagination | Closed | |
| #815 | Add config propagation check | Closed | [in v1.0.19] |
...
## Open PRs (not yet merged, consider including?)
| # | Title |
|---|-------|
| #825 | feat: webhook notifications |
...
Options:
- "yes, include all" -- add everything listed above (the default)
- "exclude items already in other milestones" -- skip [in vX.X.X] items
- "only include #814, #782, #820" -- cherry-pick specific items
- "exclude #764, #815" -- remove specific items
- "also add #825" -- include an open PR not in the listImportant: In both tables, always show Open items first, then Closed items. Within each group, sort by number ascending.
Wait for the user to confirm or adjust the list before creating anything.
Once approved, create the milestone:
# First check it doesn't already exist
gh api repos/{owner}/{repo}/milestones --jq '.[] | select(.title == "{version}") | .number'
# Create the milestone
gh api repos/{owner}/{repo}/milestones \
-f title="{version}" \
-f due_on="{date}T07:00:00Z" \
-f description="$DESCRIPTION"The description should contain two markdown tables (Issues and PRs) with clickable links. Format:
Release {version} - targeting {day_of_week} {month} {day}, {year}.
{User's theme/notes if provided}
## Issues
| # | Title | Status |
|---|-------|--------|
| [#{num}](https://github.com/{owner}/{repo}/issues/{num}) | {title} | {status} |
## Pull Requests
| # | Title | Status |
|---|-------|--------|
| [#{num}](https://github.com/{owner}/{repo}/pull/{num}) | {title} | {status} |Table sort order: Open items first, then Closed items. Within each group, sort by number ascending.
Add all approved PRs and issues to the milestone:
# Get milestone number from creation response
MILESTONE_NUMBER={number from Step 7 response}
# Add each item (use --field for integer type)
for item in {list_of_numbers}; do
gh api repos/{owner}/{repo}/issues/$item \
--method PATCH --field milestone=$MILESTONE_NUMBER --silent
doneNote: If an item is being moved from another milestone, --field milestone=N will reassign it. The user must have approved this in Step 6.
Create a detailed release notes draft at .scratchpad/{version}-release-notes.md containing:
This file serves as the starting point for the actual release notes when the release is cut (using the /release-notes skill).
After creating everything, present:
Then ask:
Milestone {version} created.
Would you like to create another milestone? For example:
- "create v1.0.21 targeting April 21" -- I'll use {version} as the new baseline
- "no, I'm done" -- we're finishedThis enables the user to plan multiple sequential releases in one session. When creating the next milestone, the baseline automatically shifts to the version just created, and items already assigned to previous milestones are flagged.
When the user wants to plan multiple releases at once (e.g., "I want to plan v1.0.20 and v1.0.21"):
[in {first_version}]Example flow:
User: I want to plan v1.0.20 for Monday and v1.0.21 for next Friday
Step 1: Create v1.0.20 milestone
- Baseline: v1.0.19 (latest release)
- User picks items for v1.0.20
Step 2: Create v1.0.21 milestone
- Baseline: v1.0.19 (same release baseline, but now items in v1.0.20 are flagged)
- User picks remaining items + new items for v1.0.21#123 (GitHub does not auto-link in milestone descriptions).--field (not -f) when setting the milestone number on issues/PRs, since it must be an integer.User: /create-milestoneResponse:
Current state:
- Latest release: v1.0.19 (published April 14, 2026)
- Existing milestones: v1.0.19 (due Apr 14, 30 closed / 3 open)
Suggested next milestone: v1.0.20
1. What version? (default: v1.0.20)
2. Target release date?
3. Diff from which release? (default: v1.0.19)
4. Theme or notes?User: /create-milestone v1.0.20 2026-04-21Response:
I'll create a v1.0.20 milestone targeting Monday April 21, 2026.
Diffing from v1.0.19 (latest release, published April 14).
Let me gather all changes since v1.0.19...
[presents draft tables for approval]User: /create-milestone v1.0.20 2026-04-21
User (in response to baseline question): everything since v1.0.17Response:
Diffing from v1.0.17 (published March 31).
Note: This spans v1.0.18 and v1.0.19 -- items already in those milestones will be flagged.
[presents draft tables with [in v1.0.18] and [in v1.0.19] annotations]User: I want to plan v1.0.20 for Monday and v1.0.21 for next FridayResponse:
I'll plan both milestones. Starting with v1.0.20.
[runs full workflow for v1.0.20, then asks about v1.0.21]User: only include #820, #821, #814, and #782Response:
Got it. Creating milestone with just those 4 items.
[creates milestone with only the specified items][in {milestone}] annotation. If the user includes it, reassign it to the new milestone.gh auth login.© agentic-community, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .claude/skills/create-milestone of agentic-community/mcp-gateway-registry.
Open the folder on GitHubat commit ec3a197
Create Milestone 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 |
|---|---|---|---|---|---|---|
| Create Milestone this skillagentic-community/mcp-gateway-registry | 967 | — | ~3.5k | Automated safety check: Pass | Apache-2.0 | |
| CCPM Project Managementautomazeio/ccpm | 8.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Project Managerpwrdrvr/openclaw-codex-app-server | 265 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Find Project Anomaliespenpot/penpot | 61k | — | ~1.2k | Automated safety check: Pass | MPL-2.0 | |
| PublishQ00/ouroboros | 6.2k | — | ~2.7k | Automated safety check: Pass | MIT | |
| Gh Read Inspectoreclipse-rdf4j/rdf4j | 420 | — | ~950 | Automated safety check: Pass | BSD-3-Clause |
automazeio/ccpm
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
pwrdrvr/openclaw-codex-app-server
Manage GitHub issues and the GitHub Project board for the current repository, while keeping the local tracker in sync.
penpot/penpot
Check a GitHub milestone against the Main project board, report the five anomaly types to tmp/<MILESTONE-ANOMALIES.md, and fix missing milestone assignments on request.
Q00/ouroboros
Publish Seed specification as GitHub Issues for team-based project management
eclipse-rdf4j/rdf4j
Retrieve GitHub issues, pull requests, and milestones with read-only, whitelisted gh commands only.
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.
agentic-community/mcp-gateway-registry
Explain a GitHub issue or pull request at 100, 200, and 300 level.
agentic-community/mcp-gateway-registry
Debug issues in the MCP Gateway Registry using first-principles thinking.
agentic-community/mcp-gateway-registry
Keep Terraform and CDK infrastructure in sync. An agent skill from agentic-community/mcp-gateway-registry.
agentic-community/mcp-gateway-registry
Generate a search quality benchmark for the AI Registry. An agent skill from agentic-community/mcp-gateway-registry.
agentic-community/mcp-gateway-registry
Write prose people will actually read. An agent skill from agentic-community/mcp-gateway-registry.
agentic-community/mcp-gateway-registry
Given an MCP server URL, probe the server via curl to discover its metadata and tools, then generate a markdown file with copy-pasteable content for each field in the Amazon Bedrock AgentCore…
Works with
Categories
Create a GitHub milestone for an upcoming release. An agent skill from agentic-community/mcp-gateway-registry. Create Milestone is an agent skill from agentic-community/mcp-gateway-registry. Create a GitHub milestone for an upcoming release.
Create Milestone fits situations like: tasks that involve Project management.
Run `npx skills add agentic-community/mcp-gateway-registry --skill create-milestone -a claude-code`. Or copy the skill folder (.claude/skills/create-milestone in agentic-community/mcp-gateway-registry) into .claude/skills/create-milestone in your project. Claude Code loads it when a task matches its description.
Run `npx skills add agentic-community/mcp-gateway-registry --skill create-milestone -a codex`. Or copy the skill folder (.claude/skills/create-milestone in agentic-community/mcp-gateway-registry) into .agents/skills/create-milestone in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add agentic-community/mcp-gateway-registry --skill create-milestone -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/create-milestone, .gemini/skills/create-milestone, .github/skills/create-milestone and .opencode/skills/create-milestone in your project.
Going by SKILL.md and its folder, Create Milestone needs the command-line tools its instructions call (gh and git).
SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
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.
Create Milestone is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.5k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Create Milestone: CCPM Project Management (automazeio/ccpm, 8.4k stars), Project Manager (pwrdrvr/openclaw-codex-app-server, 265 stars), Find Project Anomalies (penpot/penpot, 61k stars) and Publish (Q00/ouroboros, 6.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
agentic-community (a GitHub organization) maintains it in agentic-community/mcp-gateway-registry, which has 967 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 6, 2026.
Source: agentic-community/mcp-gateway-registry on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.