Arguments
What you get
Four kinds
It never invents willingness
- No asserted role, relationship owner, or appetite the evidence does not support.
- Unknown is stated as unknown.
- One specific ask per candidate.
Documentation Index
Fetch the complete documentation index at: /docs/llms.txt
Use this file to discover all available pages before exploring further.
Finds the customers worth inviting to shape a feature: detailed feedback, genuinely engaged, and not the same three names again.
/closedloop-product-ambassadors who should we invite as design partners for the onboarding flow?
| Argument | Required | Default |
|---|---|---|
| Feature, product area, workflow or initiative | yes | asks if you leave it open |
| Time window | no | last 90 days |
| Candidates returned | no | 20 |
PRODUCT AMBASSADORS: onboarding flow
1. Marcus, Ops Lead, Contoso Retail DESIGN PARTNER
THE ASK
Two sessions while the flow is still on paper. He should
see it before it is built, not after.
WHY HIM
He described the current flow end to end, unprompted, and
named the step he works around. That is a problem he has
already modelled.
"We skip your step three entirely and paste it in later."
2. Priya, Northwind Trading BETA USER
THE ASK
Give her the build once it runs. She wants the outcome,
not the design conversation.
WATCH-OUT
She is mid-renewal. Route through her CSM, not cold.
3. Sam, Fabrikam Group EXPERT REVIEWER
Deepest power user in the data, and the most critical.
Invite for the critique, not for encouragement.
| You want | Ask for |
|---|---|
| Someone to help shape the problem and the solution | Design partner |
| Someone to validate something you have built | Beta user |
| Someone to carry the rollout inside their company | Internal champion |
| Someone to critique the workflow as a power user | Expert reviewer |