recurring-customer-impact

Review customer impact evidence across the revenue lifecycle using SPICED principles.

1|Updated Aug 3, 2026
One-click install
npx skills add https://github.com/getyak/talent-signal --skill recurring-customer-impact-getyak
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: recurring-customer-impact
Source: https://github.com/getyak/talent-signal/tree/main/.agents/skills/recurring-customer-impact
Command: npx skills add https://github.com/getyak/talent-signal --skill recurring-customer-impact-getyak

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Revenue teams lose customer context at every handoff: pain discovered in sales never reaches customer success, promised impact is never verified, and seller urgency gets mistaken for real customer deadlines. This Skill reviews conversations, account plans, handoffs, and renewal or expansion proposals to check whether customer impact claims are grounded in actual evidence. ## Core Features & Use Cases - SPICED Evidence Review: Extracts and versions situation, pain, impact, critical event, and decision evidence, flagging missing causal links instead of filling gaps. - Handoff and Lifecycle Audit: Traces promised impact from signature through implementation, renewal, and expansion, requiring source-linked context to survive each handoff. - Structured Review Packet: Returns a verdict, 0-4 score, confidence level, findings with severity and recommendations, vetoes, and open questions. - Use Case: Before approving a renewal proposal, run this review to confirm the claimed customer impact has a baseline, source, and verified outcome rather than relying on a CRM stage or health score. ## Quick Start Use recurring-customer-impact to review this account plan and renewal proposal and tell me whether the claimed customer impact is supported by evidence.

Frequently Asked Questions about recurring-customer-impact

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review whether customer impact claims are supported by evidence?▼

Run this review against the account plan, conversation notes, or proposal in question. It extracts situation, pain, impact, critical event, and decision evidence, checks the causal chain, and returns a verdict with findings, missing evidence, and vetoes.

What is the SPICED framework used for in sales reviews?▼

SPICED structures customer context into situation, pain, impact, critical event, and decision so it survives handoffs across the revenue lifecycle. This Skill applies it as a review lens based on Winning by Design's public materials, without reproducing proprietary training content.

Can this review sales handoffs to customer success teams?▼

Yes. It audits handoffs by requiring the receiving team to see source-linked customer context, explicit promises, unknowns, permissions, and changed state. A generated summary or CRM stage alone is not accepted as handoff truth.

When does the review return abstain or a veto?▼

It abstains when customer-specific evidence or a valid outcome link is missing for impact, urgency, renewal, or expansion claims. It vetoes fabricated impact, manufactured critical events, seller revenue mislabeled as customer success, silent handoff state, or synthetic health scores.

Does this Skill write to my CRM or contact customers?▼

No. It only produces a review packet. Any CRM writes, customer communication, pricing, contract, renewal, or expansion effects require separate explicit approval before execution.