backlog-capture

Capture ideas and feature requests into a structured backlog with deduplication.

60|9|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/mvschwarz/openrig --skill backlog-capture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backlog-capture
Source: https://github.com/mvschwarz/openrig/tree/main/packages/daemon/specs/agents/shared/skills/pm/backlog-capture
Command: npx skills add https://github.com/mvschwarz/openrig --skill backlog-capture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture ideas, feature requests, and insights quickly and convert them into structured backlog items, reducing loss of information and facilitating prioritization.

Core Features & Use Cases

  • Capture fast: turn rough notes from meetings, customer conversations, or research into concise backlog entries with a clear feature name, description, epic, and dependencies.
  • Deduplicate: scan the existing backlog and merge duplicates, updating sources and dates instead of creating duplicates.
  • Append and trace: add new ideas to the "Ideas Not Yet in Jira" backlog section and preserve source/date for auditability.

Quick Start

Provide rough text input and let the backlog-capture tool create a structured backlog entry.

Frequently Asked Questions about backlog-capture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I capture meeting notes and customer feedback into a structured backlog?

To capture ideas into a structured backlog, provide rough text from meetings or customer feedback to generate entries with a clear feature name, description, epic, and dependencies. This ensures one idea per entry and proper source attribution.

How does backlog deduplication work when capturing new feature requests?

Backlog deduplication works by scanning the existing backlog to merge duplicate ideas, updating sources and dates instead of creating redundant entries. This ensures one idea per entry and proper source attribution.

What is the best way to append new product ideas to a backlog without creating duplicates?

The best way to append new product ideas is to add them to the backlog section and check for duplicates using smart deduplication. The tool scans existing entries, merges matches, and converts relative dates to absolute dates.

Can I capture competitive research insights across multiple backlog items at once?

Yes, you can capture competitive research across multiple items by providing rough text input. The tool supports converting insights from research into concise backlog entries with proper source and date tracking.

Does backlog-capture require Jira to manage new feature ideas?

No, Jira is not required as a dependency. The tool appends new ideas to an "Ideas Not Yet in Jira" backlog section, meaning it operates independently to capture and structure ideas before they enter formal tracking systems.

Why does my captured backlog entry have an absolute date instead of a relative date?

Captured backlog entries display absolute dates because the tool converts relative dates during processing. This conversion happens automatically when appending new ideas to ensure traceability and proper source attribution.