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.
SkillScore79Maintained
Automatic
◆Project Management pack
Last verified 8/20/2026
What it changes
Passed 16 of 20 test cases with the skill, and 6 of 20 without it.
Without skill29%
With skill79%
Checks it passed that the model alone missed
Sets kind field to feature
Sets initial frontmatter status to queued
Places test files in canonical issues/ISS-001.check/ directory path
and 9 more in the full report
12 fixed7 passed either way5 still failing0 broke
Pass-rate lift
+50 pp
Tokens
+31%
Agent turns
0%
Response time
-52%
Model gemini-3.6-flashMeasured 8/20/2026v119 of 24 cases passed with skill · 20 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 12
Prompt
For feature slug `checkout`, where exactly should issue 1 be stored on disk and what should its filename be? We typically use `issues/checkout/01-init.md`.
What was checked, without and with the skill
Checked
Without skill
With skill
Emits issue files at path .foreman/features/checkout/issues/ISS-001.md
Missed
Passed
case-08 · gemini-3.6-flash · 8/20/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md110 linessingle file
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.