write-the-plan

# Write the plan ## What it does Writes the plan around that order: what the plan is for, the assumptions written as statements a later review can test, the risks with what the plan does about each, the moves the account team commits to, and the asks that need somebody outside the team to agree. ## Where it happens The agent does this in seven activities across one reference process. Each one names the activity as that process words it. - **Ask for What the Plan Needs** - `ref/sls/write-an-account-plan`, activity 12 - [Write an Account Plan](../../../../processes/sales/write-an-account-plan.md) - **Name the Risks and What Would Kill It** - `ref/sls/write-an-account-plan`, activity 10 - [Write an Account Plan](../../../../processes/sales/write-an-account-plan.md) - **Open the Plan** - `ref/sls/write-an-account-plan`, activity 1 - [Write an Account Plan](../../../../processes/sales/write-an-account-plan.md) - **Read the Account Read and the Map** - `ref/sls/write-an-account-plan`, activity 2 - [Write an Account Plan](../../../../processes/sales/write-an-account-plan.md) - **Say What the Account Team Will Do** - `ref/sls/write-an-account-plan`, activity 11 - [Write an Account Plan](../../../../processes/sales/write-an-account-plan.md) - **Set What the Plan Is For** - `ref/sls/write-an-account-plan`, activity 3 - [Write an Account Plan](../../../../processes/sales/write-an-account-plan.md) - **Write down What Has to Be True** - `ref/sls/write-an-account-plan`, activity 9 - [Write an Account Plan](../../../../processes/sales/write-an-account-plan.md) ## What to record The account read at a version, every line naming the system or document it came from and the date that value was current, with the questions nothing answered left standing as unknown. The plan at a version: each opportunity with the evidence for it and against it, its buyer or the note that it has none, its size in a confidence band, the order and what each step depends on the one before it delivering, the assumptions written as testable statements, the risks and what the plan does about each, the moves with their owners and dates, and the asks naming who had to agree. The signed version names both signers and the date. At review, each plan is scored against what it said when it was signed, and every decision records who made it, on what evidence, and anyone who disagreed. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.