Writing Prds logo

Writing Prds

Community
cnfeat
writing-prds

Help users write effective PRDs. Use when someone is documenting product requirements, preparing specs for engineering, writing feature briefs, or defining what to build for their team.

Overview

Publishercnfeat
Repositorytop-pm-skills
Skill namewriting-prds
Stars
55
Forks
6
Bundled files
1
LicenseMIT
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.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by cnfeat on GitHub. Read the source before you install it.

Installation

Install the Writing Prds 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/cnfeat/top-pm-skills/tree/main/参考skill/lenny-skills-main%20(2)/lenny-skills-main/skills/writing-prds
  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.

Use it in TypingMind

Enable Writing Prds 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 Writing Prds 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 Writing Prds 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.

Writing PRDs

Help the user write effective product requirements documents using frameworks and insights from 11 product leaders.

How to Help

When the user asks for help with PRDs:

  1. Start with the why - Ask about the problem being solved and why it matters now, before features
  2. Define success upfront - Help them articulate how they'll know the feature succeeded
  3. Choose the right format - Discuss whether they need a traditional doc, a prototype, or executable evals
  4. Keep it actionable - Ensure the document leads to clear team action, not just documentation

Core Principles

Lead with problem and context

Maggie Crowley: "The most important section is the first part - what is the background and context? What is the problem, why does it matter, and why does it matter now?" Center the team on the 'why' and the urgency before discussing solutions.

The PR/FAQ forces clarity

Bill Carr: "Whenever we're devising a new product, we start by writing a press release describing it in a way that speaks to the customer. The idea better jump off the page." Use the PR to describe customer, problem, and solution in factual, data-rich language.

Demos before memos in AI age

Aparna Chennapragada: "If you're not prototyping and building to see what you want to build, you're doing it wrong. Prompt sets are the new PRDs." For AI features, include functional prototypes and prompt sets as core requirements.

Evals as living PRDs

Hamel Husain & Shreya Shankar: "This is the purest sense of what a product requirements document should be - this eval judge that's telling you exactly what it should be, and it's automatic and running constantly." Translate product requirements into executable evaluations for AI products.

Keep it lightweight for action

Eric Simons: "We tend to keep them pretty light. I like to have the minimal amount of context that ensures everyone's on the same page and that key outcomes will be present when we get there." Focus on key outcomes rather than exhaustive details that developers ignore.

PRDs demonstrate craft

Vikrama Dhiman: "Is your PRD quality good enough? Are you writing drafts that go to care teams, marketing teams? You must have impact through the artifacts you work on." High-quality PRDs demonstrate professional craft and create clarity at scale.

AI can scaffold the basics

Claire Vo: "I had used ChatGPT to come up with a very serviceable PRD spec for this very technical product." Use AI to scaffold basics like user stories and out-of-scope items, then focus on high-level strategy and narrative.

Live PRDs reduce ambiguity

Guillermo Rauch: "The product management team is now actually building the product. We've specced out in v0, think of it as a live PRD. The amount of detail - we're all saying 'just ship it.'" Interactive, animated prototypes reduce ambiguity and speed up approval.

Include the 'Why Now'

Justify the timing of this investment against other opportunities. If you can't explain why this matters now versus later, the priority is questionable.

Questions to Help Users

  • "What problem is this solving, and why does it matter now?"
  • "How will you know if this feature was successful - what metric moves?"
  • "Who is the customer, and what does their life look like after this ships?"
  • "What is explicitly out of scope to prevent scope creep?"
  • "Could you build a quick prototype instead of writing more documentation?"
  • "What are the key decisions that still need to be made?"

Common Mistakes to Flag

  • Starting with the solution - The document should lead with the problem and context
  • No success criteria - Every PRD needs a clear definition of how you'll measure success
  • Exhaustive detail - Lightweight PRDs focused on outcomes are more likely to be read and used
  • Static when prototypes work better - For AI and UI work, live prototypes communicate more than prose
  • Missing the 'Why Now' - Without urgency justification, priorities will be questioned

Deep Dive

For all 14 insights from 11 guests, see references/guest-insights.md

Related Skills

  • Writing Specs & Designs
  • Working Backwards
  • Stakeholder Alignment
  • Shipping Products

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Writing Prds AI skill do?

Help users write effective PRDs. Use when someone is documenting product requirements, preparing specs for engineering, writing feature briefs, or defining what to build for their team.

Why use Writing Prds on TypingMind?

Because you install it once and use it with any model. Writing Prds 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 Writing Prds in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/cnfeat/top-pm-skills/tree/main/参考skill/lenny-skills-main%20(2)/lenny-skills-main/skills/writing-prds. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Writing Prds?

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 Writing Prds?

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

Is the Writing Prds AI skill free?

Yes. It is published on GitHub by cnfeat under the MIT license. 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 👇