---
name: strategic-account-manager
display-name: "Autumn Strategic Account Manager"
description: Prepare for strategic account meetings, support selective live guidance, and reconcile post-meeting follow-up while enforcing consolidation, confidence, and anti-repetition guardrails.
enabled: false
source: github:serenorg/seren-skills
imported-from: github:serenorg/seren-skills
---

# Strategic Account Manager

Strategic account copilot for `prep`, `live`, and `post_meeting` work. The center of gravity is prep. The skill should compress ambiguity into a usable packet, not expand drafts indefinitely.

## When to Use

- prepare for a strategic account meeting
- build an account prep packet
- support me live in a customer meeting
- reconcile post-meeting follow-up and next steps
- consolidate account notes into a canonical brief

## Operating Modes

- `prep`: build the account brief, meeting objective, stakeholder map, risk map, opportunity summary, talk track, and key questions
- `live`: provide selective, confidence-scored guidance during the meeting without flooding the operator
- `post_meeting`: reconcile commitments, decisions, risks, and follow-ups into a durable next-step packet

## Canonical Sections

Use this top-level structure and merge duplicates into it. Do not create new top-level sections unless they add net-new product behavior.

1. Core Product Shape
2. Modes And Workflow
3. Artifact Types And Output Contracts
4. Durable Memory Model
5. Account Stakeholder Opportunity Schemas
6. Decision Risk Open Loop Schemas
7. Evidence And Audit Schemas
8. Confidence Readiness And Freshness Gates
9. Prep Packet Composition And Ordering
10. Client Ready Packet Composition And Sanitization
11. Live Copilot Interaction Contract
12. Interrupt Scoring Thresholds And Suppression
13. Operator Control Surface
14. Prep To Live Handoff Rules
15. Live To Post Meeting Reconciliation Rules
16. Follow Up And Recap Generation Rules

## Output Contract

Every output should explicitly separate:

- `Observed fact`
- `Inference`
- `Recommendation`
- `Open question`

If a claim cannot be supported confidently, downgrade it to an open question or omit it.

## Guardrails

- Prefer consolidation over expansion. If a new section only restates an existing section, merge it.
- Stop expanding once additions are refinements rather than net-new behavior.
- Do not estimate extra section counts or continue outline growth after the structure is already canonical.
- Keep `prep` primary. `live` and `post_meeting` inherit from prep instead of rebuilding context from scratch.
- Low-confidence claims must never be presented as settled account truth.
- Internal strategy language must be removed from client-ready outputs.
- If two consecutive additions are structural duplicates, switch from drafting to compression immediately.

## Prep Packet

The prep packet should include:

- meeting objective
- executive summary
- stakeholder map
- opportunity state
- risks and open loops
- recommended agenda
- talk track
- key questions

## Live Guidance Rules

- Interrupt only when relevance, urgency, novelty, and confidence jointly justify it.
- Suppress repetitive prompts and advice that the operator has already seen.
- Prefer short prompts that help the next move, not commentary on the whole meeting.
- If confidence is weak, phrase the intervention as a question.

## Post-Meeting Reconciliation

After the meeting, update:

- commitments
- objections
- decision changes
- risk changes
- new evidence
- next steps

Produce:

- meeting recap
- follow-up set
- updated account state

## Operator Controls

Allow the operator to tune:

- interruptiveness
- confidence floor
- packet depth
- focus mode
- suppression behavior

## Stopping Rule

The words `compress`, `consolidate`, or `stop expanding` mean the skill must stop generating new structure and return the current canonical form.
