capture-feedback
Skill1 starsChanged 3 months agoMITView on GitHub
Capture and triage inbound signals — customer feedback, support themes, sales asks, stakeholder requests, ideas, bug trends — into the intake register, then route each to discovery, backlog, roadmap, or decline. Use whenever new input arrives or for a triage sweep. Dispatches the product-manager.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- getcargohq/cargo-manifesttheir own version, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- getcargohq/cargo-manifest★ 11same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository30 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- build-business-caseSkill
- build-roadmapSkill
- close-projectSkill
- coordinate-programSkill
- define-metricsSkill
- define-strategySkill
- design-dashboardSkill
- elicit-requirementsSkill
- groom-backlogSkill
- make-deliverableSkill
- manage-changeSkill
- manage-resourcesSkill
- plan-capacitySkill
- plan-launchSkill
- plan-portfolio-automationSkill
- plan-projectSkill
- plan-sprintSkill
- powerbiSkill
- prioritizeSkill
- review-okrsSkill
- review-portfolio-intakeSkill
- run-ceremonySkill
- run-discoverySkill
- run-gate-reviewSkill
- setup-pmoSkill
- track-financialsSkill
- track-portfolioSkill
- track-statusSkill
- write-prdSkill
The file
Files
/capture-feedback — The PMO's front door
When to use
Whenever inbound arrives (feedback, requests, ideas, support/bug themes), or for a regular triage sweep of open intake.
Dispatches
product-manager (lead/triage). Consult discovery-researcher for items needing validation;
product-owner for items going straight to backlog.
Inputs
The raw signal(s), knowledge/intake.md, knowledge/product-context.md (goals/OKRs), knowledge/roadmap.md.
Steps
- Capture each signal into
knowledge/intake.md: date, source, raw request, type. - Classify type (problem / idea / request / bug / insight) and link the goal/OKR it relates to (if any).
- Look for themes — does this match a recurring pattern? Update the themes section if so.
- Triage decision per item:
- Explore →
/run-discovery(unvalidated problem worth investigating) - Backlog →
/groom-backlog(clear, valuable, ready to shape) - Roadmap →
/build-roadmap(strategic, larger than a story) - Now/quick → top of backlog (small, urgent, clear value)
- Decline / Watch → record with a reason (so it doesn't keep re-entering)
- Explore →
- Route and record where each item went and its status.
Methods
knowledge/methods/discovery-and-validation.md (signal strength), knowledge/methods/prioritization-frameworks.md.
Output
Updated knowledge/intake.md; items routed to the right skill/agent. Log consequential decline/accept
decisions to knowledge/decision-log.md. Follow standards/document-standards.md.
Created by Colin Beck<br>
LinkedIn: https://www.linkedin.com/in/beckcolin/<br>
GitHub: https://github.com/link7373
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.