| name | product-intake-system |
| description | Design a product intake system that captures requests/feedback with source, problem, evidence, affected users, urgency, duplication, owner, and disposition without turning every request into roadmap work. |
Product Intake System
Use when this procedure is the primary professional method needed for the assignment.
Procedure
- Confirm the decision or outcome this work must support, its scope, owner, constraints, and definition of success.
- Establish the evidence baseline using support/sales/community/research channels, current backlog, product taxonomy, and decision workflow. Do not fill material gaps with assumptions when they can change the result.
- Map intake channels, define normalized fields/taxonomy, deduplicate, route by decision owner, expose status, and preserve links to source evidence.
- Exercise realistic edge, failure, transition, or exception cases that could invalidate the result; record unresolved uncertainty explicitly.
- Validate the output against the original outcome and any neighboring professional contracts so this skill does not silently absorb another specialist's authority.
- Record the resulting artifact, measurements, decisions, provenance, and handoff information needed for another owner to reproduce or continue the work.
Quality gate
Every material request is traceable to evidence and disposition without bypassing product prioritization authority.