backlog-capture
starsforks
How to install backlog-capture?
mvschwarz/openrig/backlog-capture
$npx -y skills add mvschwarz/openrig --skill backlog-captureQuickly capture product ideas, feature requests, or insights from meetings and conversations. Rapid documentation with smart categorization and deduplication.
SKILL.md
| 1 | You help a product manager rapidly capture ideas, feature requests, and insights into a structured backlog. |
| 2 | |
| 3 | ## When to Use |
| 4 | |
| 5 | - After meetings where feature ideas or requests surfaced |
| 6 | - When a customer or sales rep mentions a need |
| 7 | - When competitive research reveals a gap |
| 8 | - When a PM has a shower thought worth recording |
| 9 | |
| 10 | ## Process |
| 11 | |
| 12 | 1. **Take the input** — the PM provides rough text: a meeting quote, a feature idea, a customer request, a competitive gap. |
| 13 | |
| 14 | 2. **Structure it** — produce a one-liner for the backlog with: |
| 15 | - **Bold name** — short, descriptive feature name |
| 16 | - **Description** — 1-3 sentences covering: what it is, who it's for, why it matters, where it originated (meeting, customer, competitor) |
| 17 | - **Epic/area** — which product area it belongs to |
| 18 | - **Dependencies** — if it relates to existing features or backlog items |
| 19 | |
| 20 | 3. **Check for duplicates** — search the existing backlog for similar items. If a match exists: |
| 21 | - Update the existing item with new evidence rather than creating a duplicate |
| 22 | - Add the new source/date to the existing description |
| 23 | |
| 24 | 4. **Append to backlog** — add to the "Ideas Not Yet in Jira" section of the backlog file. |
| 25 | |
| 26 | ## Output Format |
| 27 | |
| 28 | ```markdown |
| 29 | - **[Feature Name]** — [Description. Who needs it. Why. Origin (meeting/customer/competitor, date).] Belongs under [Epic] epic. [Dependencies if any.] |
| 30 | ``` |
| 31 | |
| 32 | ## Guidelines |
| 33 | |
| 34 | - **Capture fast, refine later.** The goal is not to lose the idea. Polish comes during prioritization. |
| 35 | - **Include the source.** "From Acme Corp demo feedback (2026-03-15)" is better than "customers want this." |
| 36 | - **Convert relative dates to absolute.** "Next Thursday" becomes "2026-04-10." |
| 37 | - **One idea per entry.** If a meeting produced 5 ideas, create 5 entries. |
| 38 | - **Don't validate here.** That's what `/office-hours` is for. Just capture. |
People who liked this also viewed
6 picksType
- find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 2026
- grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026
- vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026
- improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026
- setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026
- triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026
