Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →visionforge-ou/foreman-to-prd
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.
Passed 4 of 11 test cases with the skill, and 3 of 11 without it.
and 2 more in the full report
5 fixed2 passed either way12 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
We have an approved prd.md for the user authentication refactor feature. Please slice the user stories in prd.md into atomic GitHub issues and post them to the repository issue tracker with appropriate labels.
| Checked | Without skill | With skill |
|---|---|---|
| The response acknowledges that creating or publishing GitHub issues is outside its scope | Missed | Passed |
The instructions your model reads when the skill loads.
(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.
test cases passed, vs 3 / 11 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.