Skip to content
cccskills
FreePublished on GitHub

backlog-capture

Turn rough meeting notes, customer requests, and product ideas into structured backlog entries, a list of possible improvements. Capture who needs each idea and why, categorize it, and update matching entries with new evidence.

OriginalShow the original description

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

See how to install

Good for

  • Capturing feature ideas after a meeting
  • Recording requests from customers or sales
  • Logging product gaps found in competitor research
  • Adding new evidence to an existing idea

Files included (1)

  • SKILL.md2.0 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

agent-browser

FreeSummary

Automate website interactions through a command-line browser tool. Navigate pages, fill forms, extract text, save screenshots or PDFs, reuse login sessions, and compare page states to check the effects of actions or website changes.

  • Automating form entry and submission
  • Extracting page text and saving screenshots
  • Comparing page appearance before and after changes
mvschwarz/openrig7.9KUpdated Oct 20, 2026

Design and maintain applications where OpenRig agents help run the system. Organize instructions, shared state, and artifact checks, then trace unexpected behavior to the code, skill, or schema that needs repair.

  • Designing an application operated by OpenRig agents
  • Organizing instructions and shared application state
  • Tracing unexpected behavior to its source
mvschwarz/openrig7.9KUpdated Oct 20, 2026

Design and run bounded procedures in environments where current conditions are uncertain. The skill separates agent judgment from precise tool actions, verifies each effect, and records checkpoints so interrupted work can resume from observed evidence.

  • Designing procedures for environments with varying conditions
  • Resuming interrupted operations from verified evidence
  • Deciding whether an agent or ordinary code should control a procedure
mvschwarz/openrig7.9KUpdated Oct 20, 2026

agent-starters

FreeSummary

Create reusable starting configurations that combine an agent’s role, startup context, and source history. The skill guides registry entries, checks whether their sources are current, and manages their progression from initial capture to recommendation or retirement.

  • Create reusable startup context for an agent role
  • Refresh an agent workspace from an existing starter
  • Check a starter’s source history and freshness
mvschwarz/openrig7.9KUpdated Oct 20, 2026

Guides the design and review of agent startup context, including role files and links to authoritative records. It helps identify stale guidance, missing updates, overloaded startup files, and instructions that lose the purpose of the work.

  • Designing startup files for a new agent
  • Reviewing stale guidance used by running agents
  • Separating role information from reusable procedures
mvschwarz/openrig7.9KUpdated Oct 20, 2026

Configure selected OpenRig command permissions in Claude Code or Codex at the agreed project or user scope. Preserve existing restrictions, verify that settings load and behave as intended, and record additions so they can be removed later.

  • Configuring command permissions before launching an agent team
  • Reducing repeated approvals for selected rig commands
  • Adding permission rules within a chosen project scope
mvschwarz/openrig7.9KUpdated Oct 20, 2026

See all skills by mvschwarz

Report a problem with this skill