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.
Break an approved PRD into small, dependency-ordered, vertically-sliced implementation issues written as local files in the Foreman feature directory.
Install Foreman To Issues
$ npx skills add VisionForge-OU/foreman --skill foreman-to-issues -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install VisionForge-OU/foreman foreman-to-issues --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/VisionForge-OU/foreman.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/foreman/skills/foreman-to-issues .claude/skills/foreman-to-issues && 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 "foreman-to-issues" agent skill from https://github.com/VisionForge-OU/foreman/tree/main/src/foreman/skills/foreman-to-issues into .claude/skills/foreman-to-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "foreman-to-issues", 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/VisionForge-OU/foreman/tree/main/src/foreman/skills/foreman-to-issuesType 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 VisionForge-OU/foreman --skill foreman-to-issues -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install VisionForge-OU/foreman foreman-to-issues --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/VisionForge-OU/foreman.git skills-src && mkdir -p .agents/skills && cp -r skills-src/src/foreman/skills/foreman-to-issues .agents/skills/foreman-to-issues && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "foreman-to-issues" agent skill from https://github.com/VisionForge-OU/foreman/tree/main/src/foreman/skills/foreman-to-issues into .agents/skills/foreman-to-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "foreman-to-issues", 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 VisionForge-OU/foreman --skill foreman-to-issues -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install VisionForge-OU/foreman foreman-to-issues --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/VisionForge-OU/foreman.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/src/foreman/skills/foreman-to-issues .cursor/skills/foreman-to-issues && 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 "foreman-to-issues" agent skill from https://github.com/VisionForge-OU/foreman/tree/main/src/foreman/skills/foreman-to-issues into .cursor/skills/foreman-to-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "foreman-to-issues", 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/VisionForge-OU/foreman.git --path src/foreman/skills/foreman-to-issues--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 VisionForge-OU/foreman --skill foreman-to-issues -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install VisionForge-OU/foreman foreman-to-issues --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/VisionForge-OU/foreman.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/src/foreman/skills/foreman-to-issues .gemini/skills/foreman-to-issues && 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 "foreman-to-issues" agent skill from https://github.com/VisionForge-OU/foreman/tree/main/src/foreman/skills/foreman-to-issues into .gemini/skills/foreman-to-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "foreman-to-issues", 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 VisionForge-OU/foreman foreman-to-issuesInstalls 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 VisionForge-OU/foreman --skill foreman-to-issues -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/VisionForge-OU/foreman.git skills-src && mkdir -p .github/skills && cp -r skills-src/src/foreman/skills/foreman-to-issues .github/skills/foreman-to-issues && 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 "foreman-to-issues" agent skill from https://github.com/VisionForge-OU/foreman/tree/main/src/foreman/skills/foreman-to-issues into .github/skills/foreman-to-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "foreman-to-issues", 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 VisionForge-OU/foreman --skill foreman-to-issues -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install VisionForge-OU/foreman foreman-to-issues --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/VisionForge-OU/foreman.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/src/foreman/skills/foreman-to-issues .opencode/skills/foreman-to-issues && 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 "foreman-to-issues" agent skill from https://github.com/VisionForge-OU/foreman/tree/main/src/foreman/skills/foreman-to-issues into .opencode/skills/foreman-to-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "foreman-to-issues", 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
foreman-to-issues- GitHub stars
- 443
- Token cost
- ~1.2k tokens
- SKILL.md length
- 500 words
- Files
- 1
- Skills in repo
- 8
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Break an approved PRD into small, dependency-ordered, vertically-sliced implementation issues written as local files in the Foreman feature directory.
- Works in 4 steps: Gather context → Explore the codebase → Draft vertical slices → …
- Tasks that involve PRD writing
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Foreman To Issues is an agent skill from VisionForge-OU/foreman. Break an approved PRD into small, dependency-ordered, vertically-sliced implementation issues written as local files in the Foreman feature directory. Each issue ships a runnable acceptance check and a declared file footprint. No GitHub, no live quizzing of the user — emits files matching Foreman's issue schema with PRD traceability.
Its SKILL.md is about 1.2k 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 PRD writing. It works with GitHub. The repository describes itself as: A Boris-style agentic orchestrator TUI that supervises headless Claude Code agents through a gated software-delivery pipeline — pointed at any repository.
When your agent uses it
- Tasks that involve PRD writing
Example prompts
- “/foreman-to-issues”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
- Gather context
- Explore the codebase
- Draft vertical slices
- Emit one file per slice
What it can do on your machine
Read from SKILL.md and the folder at commit 92d7f79. 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 (its code samples are markdown).
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
Foreman To Issues loads about 1.2k tokens when it runs. Until then it costs about 88 tokens; SKILL.md has 500 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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 500 words (~1,238 tokens).
“(Adapted from mattpocock/skills to-issues — see NOTICE. Removed: all gh CLI usage, GitHub labels/triage vocabulary, and the interactive "quiz the user" loop. Issues are emitted as local files; the human reviews them in Foreman's queue-review screen instead.)”
- name
- foreman-to-issues
- foreman_skill_version
- 2
Files
Just SKILL.md in src/foreman/skills/foreman-to-issues of VisionForge-OU/foreman.
Open the folder on GitHubat commit 92d7f79
Compare with similar skills
Foreman To Issues 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 |
|---|---|---|---|---|---|---|
| Foreman To Issues this skillVisionForge-OU/foreman | 443 | — | ~1.2k | Automated safety check: Pass | Custom licence | |
| CCPM Project Managementautomazeio/ccpm | 8.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Ouroboros PM InterviewQ00/ouroboros | 6.2k | — | ~5.7k | Automated safety check: Pass | MIT | |
| To Issuessmallnest/pigo | 476 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Write A Prdbestofjs/bestofjs | 3.1k | 1 repos | ~722 | Automated safety check: Pass | MIT | |
| Write Update Tidb Docspingcap/docs | 615 | — | ~2.3k | Automated safety check: Pass | Custom licence |
Similar skills
Ouroboros PM Interview
Q00/ouroboros
Runs a guided product-manager interview that classifies each question automatically and produces a Product Requirements Document.
To Issues
smallnest/pigo
Decompose a PRD and/or SPEC into implementable Issues and create them in your chosen platform (GitHub, Local, or Baidu iCafe).
Write A Prd
bestofjs/bestofjs
Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue.
Write Update Tidb Docs
pingcap/docs
Write new TiDB documentation or update existing TiDB documentation from code changes, PRs, issues, design docs, product specs, rough drafts, existing docs, or short feature descriptions.
Write Product Spec
bholmesdev/hubble.md
Write a PRODUCT.md spec for a significant Hubble user-facing feature, focused only on user experience and observable behavior.
More from VisionForge-OU/foreman
All 8 skills in this repoForeman Debug
VisionForge-OU/foreman
Headless root-cause debugging loop for a Foreman worker whose tests, build, or acceptance check are failing — especially on a retry.
Foreman Grill Docs
VisionForge-OU/foreman
Headless grilling pass that challenges an approved implementation plan against the existing codebase and domain model, then writes an ADR draft and a PRD draft into the Foreman feature directory.
Foreman Verify
VisionForge-OU/foreman
Headless self-verification gate a Foreman worker runs before it claims an issue is done.
Foreman TDD
VisionForge-OU/foreman
Stack-agnostic test-driven development loop for a single Foreman issue.
Foreman Plan
VisionForge-OU/foreman
Headless implementation-plan authoring for the Foreman planning stage.
Foreman To Prd
VisionForge-OU/foreman
PRD template and authoring rules for Foreman. An agent skill from VisionForge-OU/foreman.
Related
Works with
Categories
Questions about Foreman To Issues
What does Foreman To Issues do?
Break an approved PRD into small, dependency-ordered, vertically-sliced implementation issues written as local files in the Foreman feature directory. Foreman To Issues is an agent skill from VisionForge-OU/foreman. Break an approved PRD into small, dependency-ordered, vertically-sliced implementation issues written as local files in the Foreman feature directory.
When should I use Foreman To Issues?
Foreman To Issues fits situations like: tasks that involve PRD writing.
How do I install Foreman To Issues in Claude Code?
Run `npx skills add VisionForge-OU/foreman --skill foreman-to-issues -a claude-code`. Or copy the skill folder (src/foreman/skills/foreman-to-issues in VisionForge-OU/foreman) into .claude/skills/foreman-to-issues in your project. Claude Code loads it when a task matches its description.
How do I install Foreman To Issues in Codex?
Run `npx skills add VisionForge-OU/foreman --skill foreman-to-issues -a codex`. Or copy the skill folder (src/foreman/skills/foreman-to-issues in VisionForge-OU/foreman) into .agents/skills/foreman-to-issues in your project. Codex loads it when a task matches its description.
Can I use Foreman To Issues 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 VisionForge-OU/foreman --skill foreman-to-issues -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/foreman-to-issues, .gemini/skills/foreman-to-issues, .github/skills/foreman-to-issues and .opencode/skills/foreman-to-issues in your project.
What does Foreman To Issues need to run?
SKILL.md names no scripts, command-line tools or credentials: Foreman To Issues is instructions for the agent only.
Does Foreman To Issues 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 Foreman To Issues 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 Foreman To Issues use?
Foreman To Issues has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Foreman To Issues use?
About 1.2k tokens (SKILL.md is roughly 5k 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 Foreman To Issues?
Skills that share tags, products or a category with Foreman To Issues: CCPM Project Management (automazeio/ccpm, 8.4k stars), Ouroboros PM Interview (Q00/ouroboros, 6.2k stars), To Issues (smallnest/pigo, 476 stars) and Write A Prd (bestofjs/bestofjs, 3.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Foreman To Issues?
VisionForge-OU (a GitHub organization) maintains it in VisionForge-OU/foreman, which has 443 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on June 29, 2026.
Source: VisionForge-OU/foreman on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.