foreman-to-issues
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.
npx skills add VisionForge-OU/foreman --skill foreman-to-issues --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# foreman-to-issues (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.) Break the **approved PRD** into independently-grabbable issues using vertical slices (tracer bullets). Run headless: produce the files and stop. The human will reorder/edit/delete/add in Foreman's queue-review screen — do not ask them anything here. ## Process ### 1. Gather context Read the approved `prd.md` (path injected by Foreman) — its body, user stories, and user flows. Read the approved `plan.md` and `adr.md` too for decisions. ### 2. Explore the codebase Understand the current state so titles and descriptions use the project's domain glossary (`CONTEXT.md`) and respect ADRs in the area you're touching. ### 3. Draft vertical slices Break the PRD into **tracer-bullet** issues. Each issue is a thin vertical slice that cuts through ALL integration layers end-to-end (schema → logic → API → UI → tests), NOT a horizontal slice of one layer. <vertical-slice-rules> - Each slice delivers a narrow but COMPL
- Process
- 1. Gather context
- 2. Explore the codebase
- 3. Draft vertical slices
- 4. Emit one file per slice
- acceptancecheck — the executable form of acceptance (REQUIRED)
- touches — the declared file footprint (for safe parallelism)
What does the foreman-to-issues skill do?
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.
How do I install it?
Run `npx skills add VisionForge-OU/foreman --skill foreman-to-issues --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From VisionForge-OU/foreman, a repository with 421 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.