sales-plan

---
name: sales-plan
description: Use when creating a forward-looking sales Plan from reviewed Actuals and confirmed commercial or FX assumptions.
---

<!-- VERA_WORKFLOW_USAGE_BEGIN -->
## Task usage and user feedback

Before substantive work, follow `../vera/references/workflow-usage.md`: start one
retained task UUID for the primary user process (including AI-led work), reuse
it across helpers/resumption, and record only observed outcomes. Discover the
native `vera_incident_host_link` tool, including deferred tools, and verify the
same run's Computer ID on the server. Privacy reporting applies only to the fixed pipeline list in
`../vera/references/selective-reporting.md`, using the exact Studio Archive run.
Studio Archive start and terminal writes automatically create a local report for
every run of those pipelines, including full exposure or incomplete observations.
The server proof binds the report hash to the same Archive run and existing Vera
userID. No agent-authored phase file or separate usage-task receipt link is needed.
Other pipelines and chat-only tasks do not get this report. After delivery ask once for the user's 1–5 stars and optional
comment; never infer a score. Studio Archive is infrastructure, not another rated
process. Synthetic/agent tests are marked and excluded. Start and record deliver
only the retained task's events. Retry with
`workflow_usage.py flush --run-id <retained-uuid>`; unrelated queued events do not
block this task. The shared contract applies even on direct skill invocation
and on both Codex and Cowork.
<!-- VERA_WORKFLOW_USAGE_END -->


<!-- VERA_CONNECTED_KNOWLEDGE_BEGIN -->
## Connected studio knowledge

When the user or an adopted studio instruction requests relevant repository
evidence, read `../vera/references/connected-studio-knowledge.md` before the
dependent work, including direct specialist invocation. Use only callable host
search/read tools; preserve citations and this workflow's qualification gates.
Without a repository, continue ordinary work. Studio skills remain independently
invoked by the user; Vera does not dispatch them.
<!-- VERA_CONNECTED_KNOWLEDGE_END -->

<!-- VERA_OPENAI_ONBOARDING_BEGIN -->
Onboarding is optional. Continue ordinary professional work immediately,
including direct specialist invocation, without checking or completing a local
onboarding profile. Missing, unfinished, inaccessible or corrupt onboarding state,
or unavailable voice/window controls, must never block ordinary work. Do not
automatically start, resume or repeatedly offer onboarding.
Only for a user-requested tutorial or a native teaching handoff, read
`../vera/references/local-onboarding.md`. A verified paired lesson worker
executes only its bound lesson and token; never bypass tutorial validation.
Tutorial profiles, progress, examples and feedback remain local; never send a
change request, stamp a tutorial receipt or call hosted interviews for a tutorial.
Current user requests take precedence over saved preferences.
<!-- VERA_OPENAI_ONBOARDING_END -->

# Plan

<!-- VERA_OPENAI_NATIVE_WORKSPACE_BEGIN -->
On Codex, read `../vera/references/native-workspace.md` and open the maintained
workspace for an explicitly bound Sales Plan run. The panel can prepare mappings,
periods, calculation choices and commercial/FX assumptions from a registered
strict Actual CSV, or explicitly copy choices from an inspected registered v2
case. Semantic meaning, scope and commercial rationale must come from the actual
inputs and the professional's decisions; the form does not infer them.

Unfinished fields are retained in an operator/tenant/run-scoped draft outside
outputs. Recovering or rebasing a draft never restores confirmation; explicit
rebase clears declared review attribution. Review every mapping, period and
assumption, enter the real reviewer/date/basis, then confirm the exact saved
version before execution. The adapter encodes the existing case contract and
calls the unchanged complete Plan runner. It retains Actual bytes, the compiled
case, attributed choices, optional original seed case and immutable generations.
Producer contract refusals remain visible as choices to correct; failed checks
remain visible; uncertain interruption requires specialist recovery.

The panel neither approves the Plan nor completes the Archive run. Literal
source previews and complete-source member lookup remain app-private. Prepared
summary and assumption-ledger rows, reconciliation and lineage can be discussed
only at the selected exact revision. The full scenario is excluded from this
default read. In the exact native revision, open the scenario consultation and
declare a question, exact filters/row IDs and output columns. The adapter calls
unchanged `model_use.py` on retained byte-identical copies in a separate query
tree. Never run the writing helper inside an immutable native Plan generation.
Every exact match is retained; app pages stay private. Explicit discussion reads
all matches through `vera_workspace_sales_plan_query_explain`, or refuses a
complete result above 64 KiB and requires a narrower new query. Never replace
complete matches with a sample. Viewer can inspect registered Actual sources
through the separate source consultation without changing the authoring draft.
Source registration, unsupported formats, unresolved semantic intake, professional
approval and final closure retain their maintained workflows. Cowork keeps the
same module workflow and output contract. Source/browser tests do not establish
installed native-host acceptance.
<!-- VERA_OPENAI_NATIVE_WORKSPACE_END -->

After substantive use of this workflow, read and follow the `Plugin Improvement Feedback` section in `../vera/SKILL.md`.

Resolve `../../modules/sales-plan` from this skill directory when it exists;
otherwise resolve `../../../sales-plan` in the repository. Read that module's
`skills/sales-plan/SKILL.md` completely and follow it. Treat the resolved module
root as the plugin working directory for all commands.