Skip to main content

close-the-plan-out

Checks every condition owed before signature as done with the evidence behind it, and closes the plan on the record with what slipped, why, and what to plan differently next time. Use it when running `ref/sls/run-the-close-plan`.

Jump to install

Source facts

Repository
jeffrschneider/agentcatalog
Last source activity
August 22, 2026 at 14:12
Detected SKILL.md language
English
Stars
0
Forks
0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

Showing SKILL.md

SKILL.md
Source instructions · Read-only preview
name
close-the-plan-out
description
Checks every condition owed before signature as done with the evidence behind it, and closes the plan on the record with what slipped, why, and what to plan differently next time. Use it when running `ref/sls/run-the-close-plan`.
license
CC-BY-4.0
metadata
{"agent":"close-plan-keeper","agent-version":"1"}
# Close the plan out ## What it does Checks every condition owed before signature as done with the evidence behind it, and closes the plan on the record with what slipped, why, and what to plan differently next time. ## Where it happens The agent does this in two activities across one reference process. Each one names the activity as that process words it. - **Close the Plan on the Record** - `ref/sls/run-the-close-plan`, activity 16 - [Run the Close Plan](../../../../processes/sales/run-the-close-plan.md) - **Confirm the Close Conditions** - `ref/sls/run-the-close-plan`, activity 14 - [Run the Close Plan](../../../../processes/sales/run-the-close-plan.md) ## What to record The plan opened from the agreed position, with the signature date. Every step, on either side, with one named owner and one date, and the steps that block others marked. The buyer's approval path with the committee dates and the person who takes it to each one. The buyer's confirmation of the plan, kept and dated. Every chase, with the reason the owner gave and the new date it produced. Every re-plan, showing which steps moved and whether the signature date moved or the slack was named. The pre-signature conditions marked done with their evidence. At close, the plan with what slipped, why, and what to plan differently. 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`.
View on GitHub