gather-feedbacklisted

# Gather Feedback ## Purpose Collect user-facing feedback (bug reports, feature requests, support tickets, survey responses) from configured sources, deduplicate, and present a triage-ready summary. Reading feedback is a planning input, not an implementation task — this skill produces a list, not changes. ## Scope Operates on whatever feedback sources the project configures. The skill is generic; project-level configuration lists which sources apply (issue tracker, support tickets, Slack channels, in-app feedback, etc.). Without configuration, the skill surfaces "no sources configured" and stops — silent assumption is worse than asking. NOT in scope: writing replies, changing tickets' state, or doing anything that mutates the source systems. Read-only by design. ## Automated pass 1. Read project feedback configuration from `<project>/.claude/feedback-sources.json` (or equivalent — projects define their own location). If absent, surface and stop. 2. For each configured source, fetch entries since the cutoff (default: last 7 days; `--since` overrides). **By default, filter to actionable lifecycle states only** — for sources that expose a status column, default to `status IN ('new','reviewed','in_progress')` (or the project-config-mapped equivalent of "not yet closed"). `--include-resolved` opts in to already-closed entries — useful for retrospective passes and for verifying that the project's auto-resolve hook is firing correctly (PandaOS refer