Backlog capture

Skill mvschwarz/openrig/packages/daemon/specs/agents/shared/skills/pm/backlog-capture

Multi-agent harness that runs Claude Code and Codex together as one system

Install

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

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

Quickly capture product ideas, feature requests, or insights from meetings and conversations. Rapid documentation with smart categorization and deduplication.

SKILL.md

2.0 KB, as published. Nobody here has run it

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