write-product-spec
Skill2.1k starsChanged 5 months agoAGPL-3.0View on GitHub
Write a PRODUCT.md spec for a significant user-facing feature in Zap, focused on detailed behavior and validation. Use when the user asks for a product spec, desired behavior doc, or PRD, wants to define feature behavior before implementation, or when the feature is substantial or behaviorally ambiguous enough that a written spec would improve implementation or review.
We split this skill into the rules it gives an agent
14 rules. 9 are common, 0 are distinctive, and 5 are very specific to this project.
9
Common
Most of the 3 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“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.
Trending
Quiet since August.thin dataabout the whole repository
Who's talking about zerx-lab/warp
- jwp2987/phosphor“Brand leaks in user-visible surfaces: Zap logo on first run, ~/.warp paths, Software\\Zap registry”GitHub · Aug 29, 2026
- jwp2987/phosphor“"Send feedback" opens the dead ancestor repo, and eight doc links are empty strings”GitHub · Aug 29, 2026
- zerx-lab/zap“Update GitHub links to remove openWarp branch references”GitHub · May 3, 2026
- zerx-lab/zap“fix: 修正 desktop 文件 Exec 字段指向的可执行文件名称”GitHub · May 3, 2026
The biggest 4 of 4 mentions linking to the repository that our crawl found. Each line is their own headline.
Other versions4 projects use a version of this.
Word for word · 1
- zerx-lab/zap★ 2.1k100% same
Edited · 2
- warpdotdev/common-skills★ 63098% same
- thesammykins/skills★ 290% same
Wrote their own version · 1
- bholmesdev/hubble.md★ 1.5ksame 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 repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- add-feature-flagSkill
- add-telemetrySkill
- dedupe-issue-localSkill
- diagnose-ci-failuresSkill
- fix-errorsSkill
- implement-specsSkill
- promote-featureSkill
- remove-feature-flagSkill
- resolve-merge-conflictsSkill
- review-pr-localSkill
- review-prSkill
- rust-unit-testsSkill
- spec-driven-implementationSkill
- triage-issue-localSkill
- update-skillSkill
- warp-integration-testSkill
- warp-ui-guidelinesSkill
- write-tech-specSkill
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.