agentleFS
Sign inStart free
konglong87konglong87/superPM/skills/workflows/write-prd/SKILL.md

write-prd

Skill84 starsChanged 8 months agoMITView on GitHub

PRD writing workflow — chain demand validation, clarification, prioritization, MVP scoping, and document generation Use when: Writing a PRD, BRD, or MRD, or need to produce product requirement documents

28 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use stakeholder-update, prioritize and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AnthropicSkill

    stakeholder-update

    Generate a stakeholder update tailored to audience and cadence. Use when writing a weekly or monthly status for leadership, announcing a launch, escalating a risk or blocker, or translating the same progress into exec-brief, engineering-detail, or customer-facing versions.

    Also in 3 projects that use this

  • blueOctopusAISkill

    prioritize

    Also in 3 projects that use this

  • SentrySkill

    write-docs

    Create or update documentation pages for the Abacus docs site. Use when adding new documentation, updating existing pages, or ensuring docs stay in sync with code changes. Ensures pages follow Starlight patterns and build correctly.

    Also in 3 projects that use this

  • MicrosoftSkill

    cut-release

    Use this skill to cut an APM release from the current worktree: assess whether the cycle since the last tag warrants a patch or minor bump (semver discipline against the merged-since-last-tag diff), sanitize the [Unreleased] CHANGELOG block into a dated version block with one concise "so what" entry per merged PR (drop internal-only churn, consolidate duplicates), bump pyproject.toml + uv.lock, run the CI-mirror lint chain, and open the release PR. Activate on "ship a release", "cut v0.x", "release prep", "bump and PR", "open release PR", "what kind of release do we need", or any phrasing that ends in opening a release PR -- even when the user does not say "skill". Stops BEFORE tagging; tagging stays a human gate that triggers the release workflow. Refuses to bump to a major (>= 1.0.0) version without explicit operator confirmation.

    Also in 3 projects that use this

  • SentrySkill

    write-tests

    Write tests following project conventions. Use when adding new tests or modifying existing ones.

    Also in 3 projects that use this

  • VercelSkill

    agent-browser

    Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

    Also in 3 projects that use this

  • +1 more from getsentry

The file

Create a free account to mount
Files
SKILL.md
<!-- workflow-deps:start -->

安装依赖预检（执行工作流之前）

本工作流入口 write-prd 只负责编排；单独安装它不会自动安装所调用的技能。 必需技能：pm-demand、pm-clarify、pm-priority、pm-mvp、pm-docs。 新产品额外需要 pm-brainstorm；仅在已有相关头脑风暴产物或用户明确跳过时可不调用它。

先用当前平台的技能列表检查必需技能是否可用。若缺少依赖，停止工作流，不要假装已执行；告知用户缺少的技能并给出安装方式。不要擅自安装或跳过。 完整安装命令（只装本入口并不够）：

npx skills add https://github.com/konglong87/superPM --skill write-prd pm-demand pm-clarify pm-priority pm-mvp pm-docs pm-brainstorm

没有 Node.js/npm 时，可按仓库 README 手动安装完整技能包；安装后重新检查技能列表，再继续流程。

<!-- workflow-deps:end -->

Workflow contract

When the full pack is installed, also consult skills/_shared/workflow-contract.md; standalone installation follows the complete steps below. For a new product idea, first run /pm-brainstorm unless relevant work already exists or the user explicitly opted out. Inspect existing outputs for relevance and ask which stages to reuse; do not skip a missing prerequisite merely because docs/ exists. Pause between stages that create or overwrite documents; use ordinary chat if AskUserQuestion is unavailable.

Execution flow

  1. Demand validation — 执行 /pm-demand。确认用户痛点与证据。
  2. Requirement clarification — 执行 /pm-clarify。确认边界条件和验收标准。
  3. Prioritization — 执行 /pm-priority。对已确认需求排序并记录取舍依据。
  4. MVP scoping — 执行 /pm-mvp。仅纳入已排序的必要范围。
  5. Document generation — 执行 /pm-docs。使功能和验收标准可追溯到需求、优先级与 MVP。

完成时仅列实际生成的文件；建议运行 /pm-prd-review 验证文档质量。

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free