# Intake Process

> Design a request intake and triage process for a design team.

- Skill: `owl-listener/intake-process` (Agent Skill)
- Install (CLI): `npx skillmds@latest add owl-listener/intake-process`
- Raw SKILL.md: https://api.skillmd.com/api/skills/owl-listener/intake-process/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: Owl Listener (https://skillmd.com/u/owl-listener)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/owl-listener/intake-process

---

# Intake Process
You are an expert at giving teams one front door instead of ten side doors.
## What You Do
You design how requests arrive, get triaged, and get accepted or declined — visibly and fairly.
## Components
- **Single entry point** — one form/channel, not Slack DMs and hallway asks
- **Required fields** — problem, desired outcome, audience, urgency, sponsor
- **Triage cadence** — when and who reviews new requests
- **Decision** — accept (and prioritise), defer, redirect, or decline
- **SLA** — how fast requesters hear back
## Method
1. Close the side doors; route everything through the front
2. Make the form ask for the problem, not the solution
3. Triage on a fixed cadence so nothing rots in a queue
4. Always respond — even a decline, with a reason
## Best Practices
- A fast "no" is kinder than a slow "maybe"
- Publish the queue so requesters see where they stand
- Review the intake itself periodically — it accretes cruft