> ## Documentation Index
> Fetch the complete documentation index at: https://docs.oneshotagent.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Soft gates

> Use founder-led evidence to decide when to scale.

A soft gate is a checkpoint that advises you to pause before scaling a motion that has not earned it. It makes the tradeoff visible while leaving the founder in control.

## Before extracting a template

`handoff templatize` checks recorded sends before extracting a reusable template. Below its preflight threshold, it warns and asks whether to continue, defaulting to no. Its `--force` option bypasses that confirmation.

The point is to learn from actual conversations before turning a speculative message into a repeatable process.

## Before handing off sales

`handoff readiness` combines a self-assessment with ledger context. It asks about demand, retention, discovery questions, the pitch and other readiness signals, then returns a green, yellow or red assessment with next actions. It is guidance based on your inputs, not independent proof of product-market fit.

`handoff first-ae` helps assess readiness for the first sales hire. Check the [CLI reference](/oneshot-gtm/cli-reference) for each command's available options; not every readiness assessment has a force override.

## Different from enforced checks

A soft gate is not the same as a missing credential, trigger readiness failure, ICP rejection, suppression rule or sender cap. Those checks protect a specific execution path. An override on a handoff command does not disable them.

When warned, review the missing evidence and decide whether you have a reason to proceed. Do not treat the ability to override as a recommendation to increase volume.