product-prd
Skill1 starsChanged 4 months agoMITView on GitHub
Use when an Electron work item needs product discovery, a PRD, scoped requirements, user flows, or acceptance criteria before architecture. Do not use for implementation, code review, debugging, packaging, or publishing.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- mgiovani/cc-arsenaltheir own version, first seen Sep 25, 2026
- Bosh-Kuo/awesome-agent-toolkittheir own version, first seen Jul 5, 2026
- d-wwei/Product-Prd-Skilltheir own version, first seen Apr 10, 2026
- levinchang/productdesign-skillstheir own version, first seen Apr 2, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- mgiovani/cc-arsenal★ 8same name
- levinchang/productdesign-skills★ 4same name
- Bosh-Kuo/awesome-agent-toolkit★ 2same name
- d-wwei/Product-Prd-Skill★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- electron-debugSkill
- electron-implementationSkill
- electron-ipc-securitySkill
- electron-releaseSkill
- electron-reviewSkill
- electron-test-e2eSkill
- github-deliverySkill
- handoffSkill
- handonSkill
- making-thingsSkill
- mts-moreSkill
- mts-oneSkill
- mts-splitSkill
- solution-architectureSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Read sidecar PROJECT.md, product context, existing PRD, and references/prd-quality.md.
- Very specific: line 20
Keep solution choices out unless they are real constraints.
- Distinctive: line 23
Do not invent approval, metrics, research, legal requirements, or platform verification.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Product PRD
Turn an approved problem into testable requirements in the sidecar PRD.md.
- Read sidecar
PROJECT.md, product context, existing PRD, andreferences/prd-quality.md. - Identify users, jobs, pain, outcomes, constraints, dependencies, and exclusions. Resolve product-changing ambiguity with the user and label reversible assumptions.
- Give every requirement a stable ID, priority, and observable acceptance evidence. Cover applicable security, privacy, accessibility, reliability, performance, data, installation, update, support, and platform needs.
- Separate acceptance by frontend, backend, and integration so an approved architecture can form a contract and later split disjoint workstreams.
- Keep solution choices out unless they are real constraints. Record user
approval in the sidecar PRD before routing to
solution-architecture.
Do not invent approval, metrics, research, legal requirements, or platform verification. Do not write project workflow records in the code repository.
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
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.