backlog-capture

1You 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 
121. **Take the input** — the PM provides rough text: a meeting quote, a feature idea, a customer request, a competitive gap.
13 
142. **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 
203. **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 
244. **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…