agentsclimarketplace
Sign in

Backlog capture

Skill mvschwarz/openrig/skills/_canonical/pm/backlog-capture

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

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.

SKILL.md

2.0 KB, 442 tokens by cl100k_base, 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

  1. Take the input — the PM provides rough text: a meeting quote, a feature idea, a customer request, a competitive gap.

  2. 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

  3. 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

  4. 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.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.