菜单
PRD template and authoring rules for Foreman. Synthesizes a PRD from the approved plan and the grilled decisions and writes it as a local file in the Foreman feature directory. Does not interview the user and does not publish to any external issue tracker.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/VisionForge-OU/foreman --skill foreman-to-prd命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Headless root-cause debugging loop for a Foreman worker whose tests, build, or acceptance check are failing — especially on a retry. Find the root cause before changing anything, fix at the source with a regression test, and never thrash on symptom patches. Used inside a foreman-tdd build session; emits no summary of its own.
Headless implementation-plan authoring for the Foreman planning stage. Explore the target repo first, then write a deep, decomposition-aware plan that the grill→ADR/PRD→issues pipeline can build on — goals, seams, data/interface changes, risks, sequencing, and testing strategy. No placeholders. Writes the plan body and stops.
Headless self-verification gate a Foreman worker runs before it claims an issue is done. Re-run the real commands, read the actual output, and only then write the FOREMAN-SUMMARY — evidence before claims, always. Used inside a foreman-tdd build session; emits no summary of its own.
基于 SOC 职业分类
正在显示 SKILL.md
| name | foreman-to-prd |
| description | PRD template and authoring rules for Foreman. Synthesizes a PRD from the approved plan and the grilled decisions and writes it as a local file in the Foreman feature directory. Does not interview the user and does not publish to any external issue tracker. |
| foreman_skill_version | 1 |
(Adapted from mattpocock/skills to-prd — see NOTICE. Removed: live "check with
the user" seam confirmation and the GitHub publish + ready-for-agent label step.
Output is a local prd.md file, not a tracker post.)
This skill is the PRD template authority. The foreman-grill-docs skill calls
it to produce prd.md. Synthesize from the approved plan, the codebase, and the
grilled decisions — do NOT interview anyone.
Explore the target repo to understand the current state, if you haven't. Use
the project's domain glossary (CONTEXT.md) throughout, and respect ADRs in
the area you're touching.
Identify the seams at which the feature will be tested. Prefer existing
seams; use the highest seam possible. If a new seam is needed, propose it at
the highest point you can — and if whether that seam is acceptable is a genuine
product/architecture call you cannot settle from the code, add it to the
## Open questions for reviewer block rather than asking interactively.
Write prd.md into the feature directory using the template below. Begin the
file with the open-questions block (see foreman-grill-docs). Do not publish
anywhere and do not apply any labels.
<unresolved product/architecture questions, or "None — all resolved.">
The problem the user is facing, from the user's perspective.
The solution to the problem, from the user's perspective.
A LONG, numbered list of user stories, each: As an <actor>, I want a <feature>, so that <benefit>. Extremely extensive — cover all aspects of the feature. These
stories are the basis for the slicer (foreman-to-issues) and for the e2e flows,
so make each one concrete and verifiable.
For each end-to-end flow a user can perform, list the ordered steps and the observable outcome. These flows are what Foreman's e2e phase will turn into automated tests, so be precise about preconditions, steps, and expected results.
Modules built/modified, interfaces changed, technical clarifications, architectural decisions, schema changes, API contracts, specific interactions. No file paths or code snippets (they go stale) — exception: a prototype-derived snippet that encodes a decision more precisely than prose (state machine, reducer, schema, type shape) may be inlined, trimmed to the decision-rich parts.
What makes a good test here (test external behavior, not implementation details); which modules will be tested; prior art for the tests (similar tests already in the codebase); the test/lint/typecheck commands Foreman will run to verify work.
What is explicitly not part of this PRD.
Anything else worth recording.
