cc-skill:prd-writer

Claude Code skill · anthropic · active

last 30 days

0 calls

0 of 30 days active

explain like I am new to this

what it does

Generates a structured product requirements document (PRD) for a specific feature. It lays out the what, why, who, and how in a format that designers, contractors, and non-technical collaborators can understand and act on.

who it is for

Product managers, founders, and solo builders who need to spec out a single feature before handing it off to a designer or developer.

when it fires

When you ask for a PRD, product requirement document, feature spec, feature brief, user story, acceptance criteria, or scoping document.

say something like

"Write a PRD for a dark mode toggle in my app"
"I need a feature spec for account recovery via email"
"Create acceptance criteria and user stories for a search filter"

what you might get back

A formatted PRD titled 'Dark Mode Toggle' that includes: why it matters now, the primary user and their job to be done, must-have user stories, acceptance criteria (like 'dark mode persists after logout'), what's out of scope, and the one metric you're tracking (e.g., adoption rate in first 30 days).

how to know it worked

You'll see a feature-level document structured for cross-functional handoff, with user stories and acceptance criteria written clearly enough for a designer or contractor to start work without asking clarifying questions.

is this skill working for me

never used

cloud runs

0 deployments

local fires

Claude Code (optional)

posts published

from drafts

attributed

$0.00

signups + revenue

Deploy this skill as a cloud automation to put it to work — runs on a schedule, dispatches output to Telegram or email, and logs every result here.

Deploy this skill

no laptop required

Run this skill on a schedule in the cloud. Pipe output to Telegram, email, or any webhook. Every run is logged here with full output, cost, and thumbs feedback.

How this performs

Cloud-automation runs, real outputs, and feedback.

No cloud runs yet for this skill.

Once you deploy it (above), every run will show up here with the actual output, exact cost, and a thumbs button so you can rate quality over time.

what this is

Claude Code skill at /Users/olanrewajukareem/.claude/skills/prd-writer/SKILL.md. Auto-triggered by description matching when you type in Claude Code, OR embedded into agent system prompts (LeadFlow framework skills are wired this way). Auto-synced from disk every 6h via launchd.

Use this skill when generating product requirement documents (PRDs), feature specs, or detailed feature briefs that need user stories, acceptance criteria, and dependency tracking. Triggers on "PRD", "product requirement doc", "feature spec", "featur

Local Claude Code use (optional)

Install the SKILL.md file locally so this skill is available the next time you open Claude Code on your Mac. Most users skip this and just use cloud deployments above.

Install on your machine

Save this skill to ~/.claude/skills/prd-writer/SKILL.md so Claude Code auto-loads it whenever its description matches your prompt.

30-day activity

never used

2026-04-03today

cost model

unitincluded

capabilities

{
  "source": "global",
  "description": "Use this skill when generating product requirement documents (PRDs), feature specs, or detailed feature briefs that need user stories, acceptance criteria, and dependency tracking. Triggers on \"PRD\", \"product requirement doc\", \"feature spec\", \"feature brief\", \"user story\", \"acceptance criteria\", or \"scoping doc\". Different from product-spec-generator (which produces architecture-first specs) — this is feature-level, Notion/Linear-friendly, optimized for cross-functional handoff."
}

how it gets called

{
  "method": "embed_in_prompt",
  "skill_path": "/Users/olanrewajukareem/.claude/skills/prd-writer/SKILL.md"
}

This tool has never been called in the last 30 days.

That means either: (a) the system has not had a task that matched its strengths, (b) a more cost-effective alternative was picked by the router, or (c) the related automation is toggled OFF on /automations. The Recommender reviews idle tools weekly and may suggest killing it.