prd-mastery
From the author
Pointer to the upstream skill for writing PRDs grounded in the existing repo, with a fixed output folder, installed from upstream.
Install
npx skills add coco-research/coco --skill prd-mastery -a claude-code
Installs to .claude/skills/prd-mastery/ · Each command fetches the skill straight from GitHub with the open skills CLI.
No download: this skill’s licence (Custom or unclear) does not let us redistribute its files. The install commands fetch them from GitHub instead.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 82
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- sharing-skillsNickCrew/Claude-CortexUse when you've developed a broadly useful skill and want to contribute it upstream via pull request - guides process of branching, committing, pushing, and creating PR to contribute skills back to upstream repositoryEngineering★ 61
- prd-developmentdeanpeters/Product-Manager-SkillsBuild a structured PRD that connects problem, users, solution, and success criteria. Use when turning discovery notes into an engineering-ready document for a major initiative.Planning★ 7.7K
- to-prdsickn33/agentic-awesome-skillsTurn the current conversation into a PRD and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.Planning★ 48.5K
- prd-mastermajiayu000/spellbookPRD writing and product definition expert. Use when writing PRDs, user stories, acceptance criteria, or prioritizing features. Covers RICE/MoSCoW frameworks, agile requirements, and specification best practices.Planning★ 288
- create-prdnurettincoban/ai-prd-workflowInterview the user about a product idea and write PRD.md. Use at the start of a new project, before features, rules or RFCs exist.Planning★ 305
- mentorapache/magpieDraft a teaching-register comment on a GitHub issue or PR thread on the configured `<upstream>` repo, aimed at a contributor missing context the maintainer would spell out. Reads the thread, decides whether an intervention is warranted, drafts one comment per the tone guide and convention pointers, and waits for explicit confirmation before posting via `gh`. Escalates on the four hand-off triggers.Writing★ 126
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in