backlog-capture

Agent Skills › mvschwarz/openrig › backlog-capture

backlog-capture

GitHub

辅助产品经理快速从会议、客户反馈等渠道捕获产品想法和需求，进行结构化记录、智能分类及去重，并追加至待办列表。

skills/_canonical/pm/backlog-capture/SKILL.md mvschwarz/openrig

Trigger Scenarios

会议后记录功能想法客户或销售提出需求竞品分析发现缺口产品经理捕捉灵感

Install

npx skills add mvschwarz/openrig --skill backlog-capture -g -y

More Options

Non-standard path

npx skills add https://github.com/mvschwarz/openrig/tree/main/skills/_canonical/pm/backlog-capture -g -y

Use without installing

npx skills use mvschwarz/openrig@backlog-capture

指定 Agent (Claude Code)

npx skills add mvschwarz/openrig --skill backlog-capture -a claude-code -g -y

安装 repo 全部 skill

npx skills add mvschwarz/openrig --all -g -y

预览 repo 内 skill

npx skills add mvschwarz/openrig --list

SKILL.md

Frontmatter

{
    "name": "backlog-capture",
    "description": "Quickly capture product ideas, feature requests, or insights from meetings and conversations. Rapid documentation with smart categorization and deduplication."
}

You help a product manager rapidly capture ideas, feature requests, and insights into a structured backlog.

When to Use

After meetings where feature ideas or requests surfaced
When a customer or sales rep mentions a need
When competitive research reveals a gap
When a PM has a shower thought worth recording

Process

Take the input — the PM provides rough text: a meeting quote, a feature idea, a customer request, a competitive gap.
Structure it — produce a one-liner for the backlog with:
- Bold name — short, descriptive feature name
- Description — 1-3 sentences covering: what it is, who it's for, why it matters, where it originated (meeting, customer, competitor)
- Epic/area — which product area it belongs to
- Dependencies — if it relates to existing features or backlog items
Check for duplicates — search the existing backlog for similar items. If a match exists:
- Update the existing item with new evidence rather than creating a duplicate
- Add the new source/date to the existing description
Append to backlog — add to the "Ideas Not Yet in Jira" section of the backlog file.

Output Format

- **[Feature Name]** — [Description. Who needs it. Why. Origin (meeting/customer/competitor, date).] Belongs under [Epic] epic. [Dependencies if any.]

Guidelines

Capture fast, refine later. The goal is not to lose the idea. Polish comes during prioritization.
Include the source. "From Acme Corp demo feedback (2026-03-15)" is better than "customers want this."
Convert relative dates to absolute. "Next Thursday" becomes "2026-04-10."
One idea per entry. If a meeting produced 5 ideas, create 5 entries.
Don't validate here. That's what /office-hours is for. Just capture.