request-intake-triage
Skill0 starsChanged 18 days agoMITView on GitHub
Sort incoming feature requests, asks, and "can we just" messages by source, theme, urgency, and next step, so nothing gets lost and nothing jumps the line without a reason. Use when someone pastes a batch of requests from sales, support, customers, or leadership, asks to triage a backlog or intake queue, or wants to know which asks to act on first.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- kesslernity/awesome-mistral-vibe-skillstheir own version, first seen Oct 20, 2026
- kesslernity/awesome-copilot-agent-skillstheir own version, first seen Oct 13, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- kesslernity/awesome-copilot-agent-skills★ 16same name
- kesslernity/awesome-mistral-vibe-skills★ 1same 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 repository33 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- beta-program-managerSkill
- cross-team-dependency-mapSkill
- customer-advisory-board-prepSkill
- data-request-routerSkill
- decision-logSkill
- deprecation-planSkill
- duplicate-request-mergingSkill
- experiment-logSkill
- feature-flag-trackingSkill
- feedback-taggingSkill
- information-debt-auditSkill
- internal-enablement-briefSkill
- kpi-health-checkSkill
- launch-readiness-checklistSkill
- meeting-to-action-converterSkill
- new-pm-onboarding-packSkill
- pricing-packaging-change-logSkill
- process-documentationSkill
- product-metrics-definitionsSkill
- product-ops-contextSkill
- quarterly-planning-prepSkill
- raci-builderSkill
- release-notes-draftingSkill
- retro-facilitationSkill
- ritual-calendarSkill
- roadmap-hygieneSkill
- sprint-review-summarySkill
- support-escalation-patternsSkill
- tool-stack-auditSkill
- vendor-evaluation-scorecardSkill
- voice-of-customer-digestSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 29
If the need isn't clear from the source, write "Unclear — ask requester" instead of guessing.
- Distinctive: line 53
Every request gets exactly one next step and one owner:
- Distinctive: line 82
Never promise a delivery date or say something "will be built." Triage records the ask.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Request intake triage
Triage is not prioritization. Its job is to make sure every request is understood, sorted, and routed to the right next step, so the people who do prioritize are working from a clean list.
Before you start
If .agents/product-ops-context.md exists (or .claude/product-ops-context.md), read it first. Use the team, owners, tools, meetings, and metric definitions it already has, and only ask for what's missing or specific to this task. If it doesn't exist, go ahead with what you're given, and suggest running product-ops-context once so the next skill doesn't have to ask.
Step 1: Restate each request
For every item, write one line that says what the requester actually needs, in plain words. Separate the need from the solution they proposed.
| Field | What to capture |
| Request | What they asked for, as written |
| Underlying need | The problem behind it, if the source says |
| Requester | Person and team |
| Source | Sales call, support ticket, customer email, exec, internal |
| Customer(s) | Named accounts affected, if any |
| Evidence | Quotes, ticket counts, revenue at stake, as given |
If the need isn't clear from the source, write "Unclear — ask requester" instead of guessing.
Step 2: Sort
Tag each request with:
- Type: new capability, improvement, bug, question (already possible), out of scope
- Theme: the product area or workflow it touches
- Urgency: see below
- Duplicate of: another request in the batch or backlog, if it is one
Urgency comes only from evidence in the source:
| Urgency | When |
| Now | Blocking a live customer, a signed deal, or a legal/security issue |
| Soon | Named revenue or a renewal at risk, with a date |
| Later | Valid, but no deadline or named stakes |
| Unknown | Requester said it's urgent but gave no reason |
"The VP asked" is not by itself a reason for Now. Mark it Unknown and note who to ask.
Step 3: Route
Every request gets exactly one next step and one owner:
- Answer: it's already possible; send how-to
- Fix: it's a bug; route to the team that owns that area
- Add to backlog: valid, merge with any duplicate, attach the evidence
- Clarify: need more from the requester; say what to ask
- Decline: out of scope; say why in one sentence
Output
# Intake triage — [Date] — [N] requests
## Act now
| Request | Need | Requester | Evidence | Next step | Owner |
## Route
[Same table for Fix, Answer, Clarify]
## Add to backlog (grouped by theme)
- **[Theme]** — [N] requests, [accounts]. Merged: [list]
## Decline
- [Request] — [reason]
## Questions to send back
- To [requester]: [exact question]Never promise a delivery date or say something "will be built." Triage records the ask; it doesn't commit to it.
Related skills
- duplicate-request-merging — merge the sorted asks into the backlog with accurate counts
- feedback-tagging — use the same tags across requests and feedback
- data-request-router — when the ask is really for a number
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.