Skip to content
Back to skills

Carry A Sales Promise Into Delivery

ASecurity

Reconcile customer-facing commitments with current delivery scope and owners before a sales handoff becomes an untracked promise.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 26, 2026
ai-agents

Security analysis

A100/100

Scanned September 26, 2026

npx -y skills add alisonjieli-png/loop-engine --skill carry-a-sales-promise-into-delivery --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Carry A Sales Promise Into Delivery?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Carry A Sales Promise Into Delivery
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/alisonjieli-png-carry-a-sales-promise-into-delivery/badge)](https://www.skillsdirectory.com/skills/alisonjieli-png-carry-a-sales-promise-into-delivery)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: carry-a-sales-promise-into-delivery
description: Reconcile customer-facing commitments with current delivery scope and owners before a sales handoff becomes an untracked promise.
---

# Carry a sales promise into delivery

## Use case

Use when a deal or pilot moves to onboarding and messages, proposals, and approved scope may not agree. Produce a commitment handoff for review; do not decide legal meaning.

## Required inputs

- Authorized customer-facing messages, proposals, agreement or order references, and an effective-date rule where supplied.
- The current approved product and delivery scope, known dependencies, and the intended handoff date.
- Supplied rules for who may confirm commitments and who may accept changes.

## Procedure

1. Extract each customer-facing statement about timing, capability, service, data handling, or support. Preserve its exact source, speaker, date, audience, and qualifiers.
2. Classify it as an accepted commitment, conditional proposal, aspiration, disputed statement, or unresolved item using only supplied approval and document hierarchy rules. If legal interpretation is needed, flag it for qualified review.
3. Compare each item with the current delivery scope and verified capability. Mark a mismatch or missing dependency; do not silently widen scope to honor a message or erase the message because a later document differs.
4. For each accepted commitment, name the delivery owner, required input, due condition, acceptance evidence, and customer-facing expectation. Leave an owner unknown when none is assigned.
5. Prepare a conflict list for authorized resolution, including what the customer may currently believe and what the team can verify. Draft no corrective promise on its own.
6. Return the source-linked handoff table, unresolved conflicts, missing owners, and confirmation questions.

## Completion check

The delivery team can trace every included commitment to its source and a named acceptance condition. Conflicts between a message and approved scope are visible to the authorized decision maker.

## Stop or hold

Hold fulfillment or a customer-facing assurance when scope, authority, ownership, or legal meaning is disputed. Do not send messages, modify an agreement, provision a service, or present a proposal as a binding commitment.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.