gr-product-dev-ops SKILL.md skillA
gr-product-dev-ops from gingiris-1031/gingiris-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add gingiris-1031/gingiris-skills/gr-product-dev-ops@git:20261015.68deea2Pins git:20261015.68deea2 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- gingiris-1031/gingiris-skills
- Path
skills/gr-product-dev-ops/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261015.68deea2, committed Oct 15, 2026
- First version recorded
- Jun 2, 2026
- Size
- 20,103 bytes
- Repository stars
- 91
- License
- MIT
🇺🇸 Your dev team ships features nobody asked for while user-reported bugs pile up for months. Operations blames engineering for ignoring users; engineering blames operations for not understanding technical constraints. This gives you the complete Product × Engineering × Operations alignment SOP — from unified backlog to 10-day sprint cadence to veto power rules. What's inside: • Dual-layer Kanban system (master backlog + sprint board with unified tagging) • 10-day sprint standard process…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
> 🌍 **Language / 语言**: [中文](#中文版) | [English](references/en/README.md) | [日本語](references/ja/README.md) | [한국어](references/ko/README.md) ## 📦 Install ```bash clawhub install product-dev-ops-playbook ``` **What you get after installing:** - Complete 10-day sprint cadence with tri-party alignment checkpoints - Issue template + severity auto-escalation rules (3x reported = must-fix) - Ready-to-use meeting templates for sprint planning, review, and daily standups --- # 产品研发 × 运营协同 SOP ## 证据补充:避免“40 分功能”陷阱 本地播客逐字稿中的 AFFiNE 复盘指出:方案被想出来时,产品工作才刚开始。若团队不断追逐新点子,会留下大量只做到 40–60 分、没有验证激活和留存的功能。每次迭代规划必须回答:本期把哪个已有能力从“能用”磨到“可靠”,完成阈值是什么,以及为此明确停止什么。 > 本 SOP 整合一场真实产品战略会议纪要、用户反馈录入模板、内测用户访谈体系,提炼出一套**产品、研发、运营三方协同**的通用工作框架。 > > **核心原则:** 一切面向商业化服务。一切为赚钱服务。 > > **使用说明:** 本文档为通用模板,将所有 `[产品名称]` / `[项目代号]` / `[系统名称]` 替换为对应信息即可直接使用。 --- ## 一、核心问题诊断:为什么产研运总是协同不好? ### 1.1 几乎所有成长期产品都会遇到的三个矛盾 | 矛盾 | 表现 | 本质原因 | |------|------|----------| | **新功能 vs 用户反馈** | 开发团队总在追新功能,用户反馈的小 Bug 被无限搁置 | 没有统一的优先级决策机制 | | **研发想做什么 vs 运营要什么** | 研发觉得运营不懂技术,运营觉得研发不听用户 | 缺少共同目标 | | **快 vs 稳** | 产品形态还没稳定就急着增长,技术债越积越多 | 没有明确的产品阶段判断 | ### 1.2 解决思路 > **来自真实会议洞察:** 商业化变现做得好的公司(如 Manus、DeepSeek),COO 或运营负责人直接为商业化服务,产研运三方高度协同。 …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_qoevrgp4ypu5drhq/646421d8b063edc658bdd71189f6d6aea27d1cdd7079a0f9a1d3d519746069c4.json
Then /plugin install gr-product-dev-ops@markdownregistry-qoevrgp4ypu5drhq in Claude Code. It installs git:20261015.68deea2, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add gingiris-1031/gingiris-skills/gr-product-dev-ops@sha256:646421d8b063edc6The line at the top of this page pins the label git:20261015.68deea2, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_qoevrgp4ypu5drhq)
4 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in gingiris-1031/gingiris-skills/gr-product-dev-ops since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of gr-product-dev-ops from somewhere else? Ask it: where did my gr-product-dev-ops come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 5 versions of this file, between Jun 2, 2026 and Oct 15, 2026, about one every 34 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261015.68deea2 latest | 2026-10-15 | 68deea2 | 20,103 B | A | view · diff |
| git:20260814.12f81b9 | 2026-08-14 | 12f81b9 | 19,282 B | A | view · diff |
| git:20260706.a658be7 | 2026-07-06 | a658be7 | 18,865 B | A | view · diff |
| git:20260616.fccec03 | 2026-06-16 | fccec03 | 18,871 B | A | view · diff |
| git:20260602.680dabb | 2026-06-02 | 680dabb | 18,778 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/gr-product-dev-ops/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (20103 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
gingiris-1031/gingiris-skills · 91 stars · license MIT · pushed 2026-11-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_qoevrgp4ypu5drhq GET https://markdownregistry.com/api/v1/resolve?ref=gingiris-1031/gingiris-skills/gr-product-dev-ops GET https://markdownregistry.com/api/v1/blob/646421d8b063edc658bdd71189f6d6aea27d1cdd7079a0f9a1d3d519746069c4
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.