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.
A skill your agent uses when handed a GitHub issue (number or URL) to execute end to end.
Install Execute Issue
$ npx skills add lbedner/aegis-stack --skill execute-issue -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install lbedner/aegis-stack execute-issue --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/lbedner/aegis-stack.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/execute-issue .claude/skills/execute-issue && 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 "execute-issue" agent skill from https://github.com/lbedner/aegis-stack/tree/main/.claude/skills/execute-issue into .claude/skills/execute-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "execute-issue", 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/lbedner/aegis-stack/tree/main/.claude/skills/execute-issueType 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 lbedner/aegis-stack --skill execute-issue -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install lbedner/aegis-stack execute-issue --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/lbedner/aegis-stack.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/execute-issue .agents/skills/execute-issue && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "execute-issue" agent skill from https://github.com/lbedner/aegis-stack/tree/main/.claude/skills/execute-issue into .agents/skills/execute-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "execute-issue", 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 lbedner/aegis-stack --skill execute-issue -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install lbedner/aegis-stack execute-issue --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/lbedner/aegis-stack.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/execute-issue .cursor/skills/execute-issue && 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 "execute-issue" agent skill from https://github.com/lbedner/aegis-stack/tree/main/.claude/skills/execute-issue into .cursor/skills/execute-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "execute-issue", 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/lbedner/aegis-stack.git --path .claude/skills/execute-issue--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 lbedner/aegis-stack --skill execute-issue -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install lbedner/aegis-stack execute-issue --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/lbedner/aegis-stack.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/execute-issue .gemini/skills/execute-issue && 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 "execute-issue" agent skill from https://github.com/lbedner/aegis-stack/tree/main/.claude/skills/execute-issue into .gemini/skills/execute-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "execute-issue", 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 lbedner/aegis-stack execute-issueInstalls 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 lbedner/aegis-stack --skill execute-issue -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/lbedner/aegis-stack.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/execute-issue .github/skills/execute-issue && 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 "execute-issue" agent skill from https://github.com/lbedner/aegis-stack/tree/main/.claude/skills/execute-issue into .github/skills/execute-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "execute-issue", 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 lbedner/aegis-stack --skill execute-issue -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install lbedner/aegis-stack execute-issue --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/lbedner/aegis-stack.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/execute-issue .opencode/skills/execute-issue && 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 "execute-issue" agent skill from https://github.com/lbedner/aegis-stack/tree/main/.claude/skills/execute-issue into .opencode/skills/execute-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "execute-issue", 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
execute-issue- GitHub stars
- 143
- Token cost
- ~1.1k tokens
- SKILL.md length
- 674 words
- Files
- 1
- Skills in repo
- 9
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when handed a GitHub issue (number or URL) to execute end to end.
- Works in 9 steps: Read the issue: gh issue view… → Classify the work against the map above… → Load each matching workflow skill and… → …
- Handed a GitHub issue (number
- SKILL.md covers When to use, Files that change, Procedure and Gates, plus 1 more section
- Calls gh and make
What it does
Execute Issue is an agent skill from lbedner/aegis-stack. Use when handed a GitHub issue (number or URL) to execute end to end. Reads the issue, classifies the work, loads the matching workflow skill, runs it against the stated acceptance criteria, and reports results without performing any git operations.
Its SKILL.md is about 1.1k 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 scaffolding and User stories. It works with GitHub, Git and FastAPI. The repository describes itself as: A production-ready FastAPI platform with modular components and a built-in control plane. The licence is MIT.
When your agent uses it
- Handed a GitHub issue (number
- URL) to execute end to end
Example prompts
- “/execute-issue”
Workflow steps
9 steps, taken from the first numbered list in SKILL.md.
- Read the issue: gh issue view --comments. Read the comments; they often
- Classify the work against the map above and name the skill(s) you will load.
- Load each matching workflow skill and read its ## Files that change,
- Restate the issue's acceptance criteria in the session as an explicit
- Verify the issue's claims against the code before writing anything. If the
- Write the failing test first (per the loaded skill's TDD step), then
- Run the loaded skill's gates. Fix what goes red.
- Report results against each acceptance-criterion line one by one: met, not
- Stop before any git operation and hand back to the user for review.
What it can do on your machine
Read from SKILL.md and the folder at commit c8cbfad. 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
Shell commands in SKILL.md call:
ghmake
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.
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
Execute Issue loads about 1.1k tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 674 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 lbedner/aegis-stack at commit c8cbfad, republished under its MIT licence (© lbedner). 674 words, ~1,143 tokens.
Download SKILL.mdSave it as
.claude/skills/execute-issue/SKILL.md (or your agent's skills folder).- name
- execute-issue
- description
- Use when handed a GitHub issue (number or URL) to execute end to end. Reads the issue, classifies the work, loads the matching workflow skill, runs it against the stated acceptance criteria, and reports results without performing any git operations.
Execute issue
Turn a detailed GitHub issue into an executed change. This skill is the router:
it does not itself know how to add a service or cut a release, it classifies the
work and hands off to the workflow skill that does, then holds the run to the
issue's acceptance criteria. Issues authored with the agent-task template
(.github/ISSUE_TEMPLATE/agent-task.yml) map field-for-field onto this run.
When to use
Use when given an issue number or URL and asked to execute, implement, or "do" it.
Do NOT use to triage, comment on, or plan an issue without implementing it, and do NOT use it to open, branch, commit, or PR anything (those stay human-triggered; see Pitfalls). If the issue is vague enough that the scope or acceptance criteria cannot be restated concretely, stop and ask rather than guess.
Files that change
This skill owns no fixed file list. The files that change are whatever the classified workflow skill dictates. Reading order:
- The issue body and comments (via
gh issue view <n> --comments). - The matching workflow skill under
.claude/skills/<name>/SKILL.md, whose## Files that changesection is the authoritative list for the run.
Classification map (issue work type to skill):
- New business capability (auth, AI, payment, blog, finance):
add-service - New infrastructure or a variant axis (worker, scheduler, database, redis, a
*_backendoption):add-component - Locale strings, translations:
i18n - A command on the
aegistool CLI:add-cli-command - Version or rc release:
release - Template edits or backporting from a generated project:
template-dev
An issue may span more than one type (a service that adds a CLI command and locale strings). Load every matching skill and follow each for its slice.
Procedure
- Read the issue:
gh issue view <n> --comments. Read the comments; they often correct the body (a burned-rc note, a moved file). Where a comment and the body disagree, the comment usually wins, but verify against the code. - Classify the work against the map above and name the skill(s) you will load. State the classification back to the user in one line.
- Load each matching workflow skill and read its
## Files that change,## Procedure,## Gates, and## Pitfalls. - Restate the issue's acceptance criteria in the session as an explicit checklist. This is the contract the run is measured against.
- Verify the issue's claims against the code before writing anything. If the issue names a file, function, or flag that does not exist or has moved, stop and surface the contradiction rather than coding to a false premise.
- Write the failing test first (per the loaded skill's TDD step), then implement following that skill's Procedure.
- Run the loaded skill's gates. Fix what goes red.
- Report results against each acceptance-criterion line one by one: met, not met, or blocked, with the evidence (test name, gate output). Do not claim a criterion is met without having exercised it.
- Stop before any git operation and hand back to the user for review.
Show full SKILL.md (185 more words)Show less
Gates
The gates are whichever the loaded workflow skill specifies (for example
make check plus a test-stacks or test-template target). Run exactly those;
do not substitute a lighter target for the one the skill names as the
before-done gate.
Pitfalls
- No git operations: branching, committing, and PRs stay human-triggered even when the issue implies them, because the repo's git policy forbids unrequested git actions.
- An issue is a claim about the code, not the code itself; coding to the issue's described state without checking the real tree ships fixes for problems that do not exist. Surface the mismatch instead.
- Reporting a criterion as met because the code "should" satisfy it is not evidence; a criterion counts as met only after its test or gate has actually run green.
- Skipping the classification step and improvising the file list loses the hard-won completeness the workflow skills encode; always route through a skill, never freehand a workflow the skills already cover.
- A multi-type issue that loads only one skill misses a slice; re-scan the issue for CLI, i18n, and docs work that rides along with the main change.
© lbedner, 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 .claude/skills/execute-issue of lbedner/aegis-stack.
Open the folder on GitHubat commit c8cbfad
Compare with similar skills
Execute Issue 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 |
|---|---|---|---|---|---|---|
| Execute Issue this skilllbedner/aegis-stack | 143 | — | ~1.1k | Automated safety check: Pass | MIT | |
| CCPM Project Managementautomazeio/ccpm | 8.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| degit Project ScaffoldingRich-Harris/degit | 7.9k | — | ~534 | Automated safety check: Pass | MIT | |
| Project Initializationpavel-molyanov/molyanov-ai-dev | 296 | — | ~1.1k | Automated safety check: Notes | MIT | |
| Create SkillSylphAI-Inc/skills | 111 | — | ~1.2k | Automated safety check: Pass | None | |
| GitHub Sync HelperOpenMinis/MinisSkills | 440 | — | ~2.8k | Automated safety check: Pass | MIT |
Similar skills
degit Project Scaffolding
Rich-Harris/degit
Downloads a repository snapshot or template with degit into an empty folder, from GitHub, GitLab, Bitbucket, Sourcehut or a Gist, optionally at a branch, tag or commit.
Project Initialization
pavel-molyanov/molyanov-ai-dev
Initializes a project from the standard dual-runtime template, preserves existing files, configures Git hooks, and creates or connects a private GitHub repository with main and dev branches.
Create Skill
SylphAI-Inc/skills
Guide users through creating AdaL skills by clarifying the skill type (personal, project, or public plugin) and scaffolding the appropriate structure.
GitHub Sync Helper
OpenMinis/MinisSkills
General GitHub basic operations + automation for GitHub platform objects (Issues/Labels/Milestones/Releases/Actions) in the Minis environment.
GitHub Issue Triage
OpenHands/extensions
Prioritize open issues and establish acceptance criteria before marking them ready for development.
More from lbedner/aegis-stack
All 9 skills in this repoRelease
lbedner/aegis-stack
A skill your agent uses when cutting a release of the aegis-stack package.
Template Dev
lbedner/aegis-stack
A skill your agent uses when developing or modifying Copier templates in aegis/templates, or backporting a change from a generated project (e.g.
Add CLI Command
lbedner/aegis-stack
A skill your agent uses when adding a command to the aegis tool CLI (the framework's own aegis ...
Create Plugin
lbedner/aegis-stack
A skill your agent uses when building an Aegis Stack plugin, a separate package (aegis-stack-<name) that renders files into a project through aegis add <name.
I18n
lbedner/aegis-stack
A skill your agent uses when a code or template change introduces a new translation message key, in either the framework CLI (aegis/i18n/locales/) or a generated project's CLI (the app/i18n/locales/…
Squash Branch
lbedner/aegis-stack
A skill your agent uses when collapsing a feature branch into a single commit before opening or merging a PR.
Related
Questions about Execute Issue
What does Execute Issue do?
A skill your agent uses when handed a GitHub issue (number or URL) to execute end to end. Execute Issue is an agent skill from lbedner/aegis-stack. Use when handed a GitHub issue (number or URL) to execute end to end.
When should I use Execute Issue?
Execute Issue fits situations like: handed a GitHub issue (number; URL) to execute end to end.
How do I install Execute Issue in Claude Code?
Run `npx skills add lbedner/aegis-stack --skill execute-issue -a claude-code`. Or copy the skill folder (.claude/skills/execute-issue in lbedner/aegis-stack) into .claude/skills/execute-issue in your project. Claude Code loads it when a task matches its description.
How do I install Execute Issue in Codex?
Run `npx skills add lbedner/aegis-stack --skill execute-issue -a codex`. Or copy the skill folder (.claude/skills/execute-issue in lbedner/aegis-stack) into .agents/skills/execute-issue in your project. Codex loads it when a task matches its description.
Can I use Execute Issue 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 lbedner/aegis-stack --skill execute-issue -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/execute-issue, .gemini/skills/execute-issue, .github/skills/execute-issue and .opencode/skills/execute-issue in your project.
What does Execute Issue need to run?
Going by SKILL.md and its folder, Execute Issue needs the command-line tools its instructions call (gh and make).
Does Execute Issue access the network?
SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Execute Issue 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 Execute Issue use?
Execute Issue is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Execute Issue use?
About 1.1k tokens (SKILL.md is roughly 4.6k 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 Execute Issue?
Skills that share tags, products or a category with Execute Issue: CCPM Project Management (automazeio/ccpm, 8.4k stars), degit Project Scaffolding (Rich-Harris/degit, 7.9k stars), Project Initialization (pavel-molyanov/molyanov-ai-dev, 296 stars) and Create Skill (SylphAI-Inc/skills, 111 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Execute Issue?
lbedner (a GitHub user) maintains it in lbedner/aegis-stack, which has 143 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 7, 2026.
Source: lbedner/aegis-stack on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.