Customer Commitments
Use this skill when a customer outcome, promise, follow-up, or retention risk
needs an owner and a trustworthy next action.
Workflow
- Read only the customer evidence available in the workspace.
- Record the customer, desired outcome, latest signal, commitment, owner, due date, state, source, and confidence.
- Use only four states: on track, needs attention, broken, or unknown.
- Draft one next action tied to the desired outcome and existing evidence.
- Route product defects or requests into the existing feedback or task system.
- Stop for human approval before sending, publishing, discounting, refunding, or making a commercial or roadmap promise.
Guardrails
- Never manufacture usage, sentiment, renewal, or revenue data.
- Never replace missing evidence with a composite health score.
- Never create a parallel product backlog from customer notes.
- Keep the view small enough that an owner can see the next commitment immediately.
Example
Input: "The customer asked about exports last week, and we promised an answer by Friday."
Output: Record the customer's export outcome, the dated request as evidence,
the promised answer and its owner, Friday as the due date, the state as needs
attention, and one approval-gated follow-up. Leave any missing owner or customer
sentiment unknown.
Troubleshooting
- If sources conflict, show both signals, lower confidence, and ask the owner to resolve them.
- If no owner or due date exists, mark it unknown and propose one for approval.
- If the next action is product work, link or update the existing task instead of opening a parallel backlog.
1---2name: customer-commitments3description: Turn real customer evidence into a compact commitment view, retention risk, and one approval-gated next action. Use when reviewing customer feedback, follow-ups, promises, churn signals, or retention risk.4---56# Customer Commitments78Use this skill when a customer outcome, promise, follow-up, or retention risk9needs an owner and a trustworthy next action.1011## Workflow12131. Read only the customer evidence available in the workspace.142. Record the customer, desired outcome, latest signal, commitment, owner, due date, state, source, and confidence.153. Use only four states: on track, needs attention, broken, or unknown.164. Draft one next action tied to the desired outcome and existing evidence.175. Route product defects or requests into the existing feedback or task system.186. Stop for human approval before sending, publishing, discounting, refunding, or making a commercial or roadmap promise.1920## Guardrails2122- Never manufacture usage, sentiment, renewal, or revenue data.23- Never replace missing evidence with a composite health score.24- Never create a parallel product backlog from customer notes.25- Keep the view small enough that an owner can see the next commitment immediately.2627## Example2829Input: "The customer asked about exports last week, and we promised an answer by Friday."3031Output: Record the customer's export outcome, the dated request as evidence,32the promised answer and its owner, Friday as the due date, the state as needs33attention, and one approval-gated follow-up. Leave any missing owner or customer34sentiment unknown.3536## Troubleshooting3738- If sources conflict, show both signals, lower confidence, and ask the owner to resolve them.39- If no owner or due date exists, mark it unknown and propose one for approval.40- If the next action is product work, link or update the existing task instead of opening a parallel backlog.
atrislabs