← all tools

cc-skill:to-prd

Claude Code skill · anthropic · active

0
last 30 days
0 calls
0 of 30 days active
explain like I am new to this
what it does

This skill reads your current conversation and project code, then writes a Product Requirements Document (PRD) that describes what needs to be built. It then automatically posts that PRD to your project's issue tracker so your team can see it.

who it is for

Product managers, founders, and developers who want to turn a discussion into a formal requirements document without writing it from scratch.

when it fires

When you ask Claude Code to create a PRD from what you've been discussing, or to turn your current context into a PRD.

say something like
  • "Turn this conversation into a PRD and post it to the tracker"
  • "Create a PRD for the feature we just discussed"
  • "Make a PRD from our context and submit it"
what you might get back
The skill produces a structured PRD with sections for the problem, solution, user stories, implementation decisions, testing approach, and out-of-scope items. It then posts this to your issue tracker with a 'needs-triage' label, making it immediately visible to your team for review and feedback.
how to know it worked

You will know it worked when you see a new issue appear in your project tracker with the PRD content and the 'needs-triage' label applied.

is this skill working for me
never used
cloud runs
0
0 deployments
local fires
0
Claude Code (optional)
posts published
0
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/to-prd/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.

Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.

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/to-prd/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": "Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context."
}
how it gets called
{
  "method": "embed_in_prompt",
  "skill_path": "/Users/olanrewajukareem/.claude/skills/to-prd/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.