agentleFS
Sign inStart free
evgenii-studitskikhevgenii-studitskikh/Claude-Code-SaaS-Studio/.claude/skills/write-prd/SKILL.md

write-prd

Skill1 starsChanged 5 months agoMITView on GitHub

Turn a validated idea into a full PRD: goals, target users, user stories with acceptance criteria, non-goals, and success metrics. Requires idea-validation.md. Drafts then awaits approval.

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

  • 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

  • SentrySkill

    commit

    Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.

    Also in 4 projects that use this

The file

Create a free account to mount
Files
SKILL.md

Transform the idea-validation canvas into a structured Product Requirements Document that the engineering team can act on. Non-autonomous: every section is presented for approval before the file is written; review intensity controls how much detail is required before proceeding.

Phases

  1. Load context — read docs/specs/idea-validation.md. If it is missing or contains a PIVOT/KILL verdict, stop and direct the user to /validate-idea first. Summarize the validated bet in two sentences and confirm it is still accurate.
  2. Elicit goals and users — work through the PRD skeleton from .claude/templates/prd.md: confirm the primary goal, secondary goals, and the one or two target user personas. Ask one question at a time; do not over-interview.
  3. Draft user stories — propose a ranked list of user stories in "As a [persona], I want [action] so that [outcome]" format, each with two or three acceptance criteria. Present the list; let the user add, remove, or reprioritize before proceeding.
  4. Define non-goals and success metrics — propose explicit non-goals (what will NOT be built in v1) and two to four measurable success metrics tied to the goals. Get the user's sign-off on this list — it becomes the scope boundary for /scope-check.
  5. Write the draft — fill .claude/templates/prd.md with everything gathered and write the draft to docs/specs/prd.md. Show the draft inline before writing; under full review, walk through each section; under lean or solo, write directly after a single confirmation.
  6. Next step — on approval, point to /map-flows to derive the screen and journey list.

Output

docs/specs/prd.md — a complete PRD. Writes nothing else without approval.

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