Backlog Capture
Quickly capture product ideas, feature requests, or insights from meetings and conversations. Rapid documentation with smart categorization and deduplication.
Install
$ agentstack add skill-mvschwarz-openrig-backlog-capture ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-mvschwarz-openrig-backlog-capture) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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-hoursis for. Just capture.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: mvschwarz
- Source: mvschwarz/openrig
- License: Apache-2.0
- Homepage: https://openrig.dev
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.