Files
Magnus HedemarkGitHubusername <username>factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
1dd564e3d9 feat(conditional-customer-success): add conditional customer success skill (#192) (#218)
Add a conditional skill for products with recurring human relationships.
Covers success plans, health evidence, renewal/expansion signals, QBRs,
handoffs, escalation, and closed-loop Voice of Customer. The skill is
conditional: it declines and routes away when the product has no accounts,
renewals, QBRs, or customer-success team.

Includes:
- SKILL.md with conditional frontmatter, trigger sections, four product-
  model adaptations (B2B subscription, transactional, public-service,
  internal product), core artifacts, privacy and human-judgment boundaries,
  and routing to product-analytics-and-measurement, product-adoption,
  product-experimentation, go-to-market, and product-lifecycle-learning.
- README.md with all five required human-facing sections.
- references/discovery-brief.md surveying existing content and defining
  ownership boundaries and routing.
- references/privacy-and-human-judgment.md with consent framework,
  surveillance-risk guidance, decision-support rules, and data
  classification tiers.
- templates/applicability-decision.md, templates/success-plan.md,
  templates/health-risk-record.md, and templates/escalation-and-
  feedback-closure.md.
- evals/evals.json with 5 output-quality cases covering B2B subscription,
  internal-tool decline (negative trigger), public-service routing,
  renewal-risk with mixed signals, and conflicting health evidence.
- Updated root README.md catalog section, references/skill-triggers.md,
  and regenerated marketplace/Codex/llms.txt catalogs.

Co-authored-by: username <username>
Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
2026-08-02 17:30:51 -04:00

2.2 KiB

Success Plan

A structured record of the customer's desired outcomes, aligned product capabilities, measurable milestones, and assigned relationship owner. This is a living artifact — update it at each QBR or health review.

Customer Context

  • Customer: [name or identifier]
  • Product model: [B2B Subscription / Transactional / Public Service / Internal Product]
  • Relationship owner: [named CS team member]
  • Plan period: [start date] to [end date]
  • Last updated: [date]

Desired Outcomes

What does the customer want to achieve? Each outcome must be measurable.

# Outcome Success Metric Target Current Trend
1 [e.g., reduce manual data entry] [e.g., hours saved/week] [target] [current] [↑/→/↓]
2 [outcome] [metric] [target] [current] [trend]
3 [outcome] [metric] [target] [current] [trend]

Product-Capability Alignment

Outcome Supporting Capability Adoption Status Evidence
[outcome #] [feature or capability] [adopted / partial / not adopted] [adoption signal from product-adoption]
[outcome #] [capability] [status] [evidence]

Milestones and Evidence Gates

Milestone Target Date Evidence Required Status
[e.g., complete onboarding] [date] [e.g., activation rate > threshold] [on-track / at-risk / missed]
[milestone] [date] [evidence] [status]

Risk Register

Risk Likelihood Impact Mitigation Owner
[risk description] [high/med/low] [high/med/low] [what we're doing about it] [name]
[risk] [likelihood] [impact] [mitigation] [owner]

QBR / Review Notes

Date Key Discussion Decisions Follow-Up
[date] [summary] [decisions made] [actions assigned]

Plan Health Summary

  • Overall: [on-track / at-risk / critical]
  • Strongest dimension: [which outcome has the best evidence]
  • Weakest dimension: [which outcome has the weakest or conflicting evidence]
  • Next review: [date]