Skip to content
Skills Library
Management & product · Writing

writing-prds-executable

/writing-prds-executable

Draft, critique, or rewrite PRDs (product requirements / product specs) and adjacent artifacts (PR/FAQ, acceptance criteria, rollout plan). For AI/LLM features, also draft eval specs (LLM-as-judge) and prompt sets. Output must be in English. Use when the user asks for a PRD/spec/requirements/PRFAQ/evals/prompt sets, or needs help clarifying scope, success metrics, non-goals, user stories, or stakeholder alignment.

Licence
Apache-2.0
Last repository change
06.05.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
12
Scripts
1
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 06.05.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What to check before installing
  • 1 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/lint_prd.py

What it does and when to use it

Draft, critique, or rewrite PRDs (product requirements / product specs) and adjacent artifacts (PR/FAQ, acceptance criteria, rollout plan). For AI/LLM features, also draft eval specs (LLM-as-judge) and prompt sets. Output must be in English. Use when the user asks for a PRD/spec/requirements/PRFAQ/evals/prompt sets, or needs help clarifying scope, success metrics, non-goals, user stories, or stakeholder alignment.

Original author description

Draft, critique, or rewrite PRDs (product requirements / product specs) and adjacent artifacts (PR/FAQ, acceptance criteria, rollout plan). For AI/LLM features, also draft eval specs (LLM-as-judge) and prompt sets. Output must be in English. Use when the user asks for a PRD/spec/requirements/PRFAQ/evals/prompt sets, or needs help clarifying scope, success metrics, non-goals, user stories, or stakeholder alignment.

How it works

  1. When to use
  2. When NOT to use (redirect)
  3. Quick decision: which artifact(s) to produce
  4. Intake: ask only what you must
  5. Output contract (always include)
  6. Workflow A: Draft a PR/FAQ (customer-first)
  7. Workflow B: Draft or rewrite a PRD (shippable requirements)
  8. Workflow C (AI only): Requirements as executable evals
  9. Workflow D (AI only): Prompt set + prototype plan
  10. Quality bar (before finalizing)
Original SKILL.md headings · 120 lines, 667 words
SKILL.md preview
---
name: writing-prds-executable
description: >
  Draft, critique, or rewrite PRDs (product requirements / product specs) and adjacent artifacts (PR/FAQ,
  acceptance criteria, rollout plan). For AI/LLM features, also draft eval specs (LLM-as-judge) and prompt sets.
  Output must be in English. Use when the user asks for a PRD/spec/requirements/PRFAQ/evals/prompt sets,
  or needs help clarifying scope, success metrics, non-goals, user stories, or stakeholder alignment.
metadata:
  version: "1.0.0"
  language: "en"
allowed-tools: "Read,Write,Edit"
---

# Writing PRDs (Executable)

This skill turns messy ideas into **shippable artifacts**:
1) PR/FAQ (customer-first narrative)
2) PRD (scope + requirements + success metrics)
3) AI Eval Spec (requirements as executable evals) — AI only
4) Prompt Set / Prototype plan — AI only

Keep outputs crisp, concrete, and copy‑pasteable. Prefer bullets, tables, and numbered requirements over long prose.

## When to use

Use this skill when the user requests:
- a PRD / product requirements / product spec / requirements doc
- a PR/FAQ or “working backwards” narrative
- acceptance criteria, rollout plan, risks, dependencies
- AI/LLM behavior requirements, evals, judge rubric, prompt sets

## When NOT to use (redirect)

Do NOT use this skill as a substitute for:
- Company strategy / vision (use a vision/strategy skill)
- Roadmap prioritization across many initiatives (use prioritization/roadmap skill)
- Pure UX copywriting or marketing launch copy (use messaging/launch skills)

If legal/privacy/security constraints are material but unknown, first ask for constraints and the approval process.

## Quick decision: which artifact(s) to produce

If the user doesn’t specify, choose the minimal artifact that unlocks the next decision:

- Early / unclear idea → **PR/FAQ** first, then a lightweight PRD outline.
- Clear direction, need alignment / build plan → **PRD**.
- AI/LLM feature → **PRD + Eval Spec + Prompt Set** (required).
- “Improve this existing PRD/spec” → rewrite + gaps + open questions.

Templates:
- PRD: `assets/PRD_TEMPLATE.md`
- PR/FAQ: `assets/PRFAQ_TEMPLATE.md`
- Eval Spec: `assets/EVAL_SPEC_TEMPLATE.md`
- Prompt Set: `assets/PROMPT_SET_TEMPLATE.md`

Quality checks:
- Checklist: `references/QUALITY_CHECKLIST.md`
- Rubric: `references/QUALITY_RUBRIC.md`
- Question bank: `references/QUESTION_BANK.md`

## Intake: ask only what you must

Ask at most **5** high-leverage questions at a time (use `references/QUESTION_BANK.md`).
If the user can’t answer, proceed with explicit assumptions.

Minimum inputs to proceed:
1) Product/feature name + target user
2) Problem statement (what pain / why now)
3) Success metric(s) or a proxy
4) Constraints (time, platform, legal, data, dependencies)
5) Audience for the doc (exec decision? eng build? cross-functional alignment?)

## Output contract (always include)

Always include:
- Version + date + owner (or “TBD”)
- Goals and non-goals
- Requirements as numbered bullets (R1, R2…)
- Clear “Out of scope”
- Open questions (with owner / next step)

When producing multiple artifacts, output in this order:
1) PR/FAQ → 2) PRD → 3) Eval Spec → 4) Prompt Set

## Workflow A: Draft a PR/FAQ (customer-first)

Use when the idea is early or benefits are fuzzy.

1) Write the press release in external-facing, factual language.
2) Add FAQs for: customer, internal stakeholders, technical/ops, risks.
3) Include a hypothetical launch date (forces planning).
4) Extract “claims” from the PR (what must be true) → convert to requirements.

## Workflow B: Draft or rewrite a PRD (shippable requirements)

1) Start with a 5–10 line narrative (why this matters, for whom).
2) Define scope boundaries: goals, non-goals, assumptions.
3) Define users + key journeys (happy path + edge cases).
4) Translate into requirements:
   - Functional requirements (R1…)
   - Non-functional requirements (performance, reliability, accessibility, privacy)
5) Define success metrics + instrumentation.
6) Rollout plan + risks + mitigations.
7) End with open questions + decision log.

## Workflow C (AI only): Requirements as executable evals

Goal: make requirements testable.

1) List non‑negotiable behaviors (MUST / MUST‑NOT).
2) Build a test set: golden, adversarial, regression.
3) Write an LLM‑as‑judge rubric (scale + definitions + pass threshold).
4) Connect evals to shipping gates (pre‑launch + post‑launch monitoring).

## Workflow D (AI only): Prompt set + prototype plan

1) Provide a small prompt set that exercises core use cases + edge cases.
2) Specify expected outputs and guardrails.
3) Propose a minimal prototype plan if useful (what to mock vs build).

## Quality bar (before finalizing)

Run:
- `references/QUALITY_CHECKLIST.md`
- `references/QUALITY_RUBRIC.md`

Also include a brief circulation plan: who should review (Eng, Design, Data, Support, Marketing, Legal) and what feedback you need from each.

## Confidentiality

Treat user-provided information as confidential. Do not include secrets in outputs. If something looks sensitive, redact or replace with placeholders.
Files in this package (12)
  • README.md 1 KB
  • SKILL.md 5 KB
  • assets/EVAL_SPEC_TEMPLATE.md 1 KB
  • assets/PRD_TEMPLATE.md 2 KB
  • assets/PRFAQ_TEMPLATE.md 1 KB
  • assets/PROMPT_SET_TEMPLATE.md 1 KB
  • references/EXAMPLES.md 2 KB
  • references/LENNY_SOURCE_NOTES.md 1 KB
  • references/QUALITY_CHECKLIST.md 2 KB
  • references/QUALITY_RUBRIC.md 1 KB
  • references/QUESTION_BANK.md 1 KB
  • scripts/lint_prd.py 2 KB

Versions

The database has no other skills named writing-prds-executable.

Database snapshot: 13.11.2026 · package version 7d54cf23fccc (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100prd-writer
    Expert PRD (Product Requirements Document) writer for the AI era. Use when users want to create PRDs, spec documents, product specifications, feature specs, or technical requirements documents. Also use when users ask to review/improve existing PRDs, want PRD templates, need…
  • 95prd-generator
    Generates comprehensive Product Requirements Document from product plan. Creates PRD.md with features, user stories, acceptance criteria, and success metrics. Use when creating product requirements.
  • 100prd
    Structured PRD authoring where the PRD is the contract for specs delivered to implementing teams, human or agent. Use when writing a product requirements document, turning a spec-harvest feature inventory into per-feature PRDs, running /pm:prd, or defining scope boundaries and…
  • 100feature-spec
    Write structured product requirements documents (PRDs) with problem statements, user stories, requirements, and success metrics. Use when speccing a new feature, writing a PRD, defining acceptance criteria, prioritizing requirements, or documenting product decisions.
  • 100ai-prd
    Write a product requirements document (PRD) for an AI or LLM-powered feature — covering the problem, users, scope, and user stories like a normal PRD, plus the AI-specific parts most PRDs miss — why AI at all, model and architecture options (prompting / RAG / fine-tuning /…
  • 100prd-generator
    Produce a Product Requirements Document (PRD) for a defined feature or MVP scope with goals, requirements, and success metrics. Use when working on PRDs, MVP specs, functional requirements.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.