Foreman To Prd logo

Foreman To Prd

Organization
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.

Overview

PublisherVisionForge-OU
Repositoryforeman
Skill nameforeman-to-prd
Stars
444
Forks
117
Bundled files
Instructions only
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by VisionForge-OU on GitHub. Read the source before you install it.

Installation

Install the Foreman To Prd AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/VisionForge-OU/foreman/tree/main/src/foreman/skills/foreman-to-prd
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/VisionForge-OU/foreman.git /tmp/foreman
mkdir -p .claude/skills
cp -r /tmp/foreman/src/foreman/skills/foreman-to-prd .claude/skills/foreman-to-prd
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Foreman To Prd in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Foreman To Prd on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Foreman To Prd is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

foreman-to-prd

(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.

Process

  1. 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.

  2. 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.

  3. 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.

Open questions for reviewer

<unresolved product/architecture questions, or "None — all resolved.">

Problem Statement

The problem the user is facing, from the user's perspective.

Solution

The solution to the problem, from the user's perspective.

User Stories

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.

User Flows

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.

Implementation Decisions

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.

Testing Decisions

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.

Out of Scope

What is explicitly not part of this PRD.

Further Notes

Anything else worth recording.

Frequently asked questions

What does the Foreman To Prd AI skill do?

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.

Why use Foreman To Prd on TypingMind?

Because you install it once and use it with any model. Foreman To Prd is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Foreman To Prd in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/VisionForge-OU/foreman/tree/main/src/foreman/skills/foreman-to-prd. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Foreman To Prd?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Foreman To Prd?

As many as you like. As long as a model supports skills, you can use Foreman To Prd with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Foreman To Prd AI skill free?

It is published on GitHub by VisionForge-OU. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇