Skip to content

spillwavesolutions/account-management

v0.3.4MIT

Generic account and relationship ContentPack: clients, contacts, plans, deliverables, renewals.

Account Management

Generic account and relationship ContentPack: clients, contacts, account plans, deliverables, commitments, and renewals. No hard-coded client names.

MIT. Dual-host: Claude Code, Grok Build, and Codex (Agent Skill Standard). Writes OKF Markdown + YAML into a shared second-brain bundle so other agents and local jobs can read the same graph.

Install

# Claude Code
/plugin marketplace add SpillwaveSolutions/account-management
/plugin install account-management@SpillwaveSolutions

# Skilz CLI
skilz install SpillwaveSolutions/account-management

Point the plugin at a shared knowledge root (default knowledge/). All sibling ContentPack plugins write into the same tree.

Skills

SkillWhat it does
/acm-initScaffold the catalogs this plugin owns
/acm-captureCapture a noun into the shared second brain (deterministic write)
/acm-packBuild a bounded ContextPack from a root concept
/acm-validateValidate frontmatter, types, and links
/acm-sessionOpen or close an isolated write session (worktree + PR)
/acm-doctorHealth check of the bundle this plugin owns

Nouns this plugin may write

TypeMeaning
ClientAccount or organization being served
ContactNamed person at the account
StakeholderPerson with influence or veto
RelationshipHealthQualitative health signal
AccountPlanGoals and plays for the account
StatementOfWorkScoped engagement document
DeliverablePromised output
MilestoneDate-bound checkpoint
IssueOpen problem on the account
RiskAccount-level risk
OpportunityExpansion or upsell
MeetingAccount conversation
CallNoteCall recap
EmailThreadEmail conversation summary
CommitmentPromise made to the account
InvoiceStatusBilling state
ExpansionOpportunityGrowth play
SatisfactionSignalNPS / sentiment note
EscalationRaised account issue
RenewalDateContract renewal marker
SuccessMetricOutcome the account cares about

Relationships

relMeaning
belongs_toContact or deliverable belongs to client
owned_byAccount manager identity
hasClient has plan / SOW / risk
reports_toContact reporting line
committed_toCommitment toward deliverable
due_onMilestone or renewal date
originates_fromCame from meeting or thread
related_toSoft association
blocksIssue blocks deliverable

Catalogs

  • clients/
  • contacts/
  • stakeholders/
  • account-plans/
  • deliverables/
  • milestones/
  • issues/
  • commitments/
  • meetings/
  • risks/

Deterministic write boundary

The model proposes. Schema-enforced scripts commit:

python3 scripts/acm_common.py write \
  --bundle knowledge \
  --type Client \
  --folder clients \
  --title "Example" \
  --author "Grok Bot: Account Management"

Never invent rel values. Never write types owned by another plugin.

Related plugins

ContentPack suite

Foundation

Onboarding

Grok Bot and other host agents should start at docs/ONBOARDING.md. That file is the history of the LLM-wiki effort, the destination state (Grok Bots and local agents sharing one git-native second brain), and the canonical public repo list.

Multi-host

Works with Claude Code, Grok Build, Codex, Cursor, Agent Plugins 1.0 clients, Grok Bot, and LangChain Deep Agents.

HostHow to load
Claude Codemarketplace + plugin install
Grok Buildzero-config Claude plugin
CodexAgent Skills / hooks/hooks.json
Agent Plugins clientsroot plugin.json + skills/
Grok Botdocs/GROK_BOT.md
Cursordocs/CURSOR.md.cursor-plugin + Agent Plugins 1.0
LangChain Deep Agentsdocs/LANG_CHAIN_DEEP_AGENTS.md

Write isolation (worktree + PR) lives in second-brain-core: docs/ISOLATION.md. Point SECOND_BRAIN_ROOT at the session bundle. Never hard-code a private remote.

Eight job-function plugins plus core. Knowledge root is always a local path or env the human already owns.

License

MIT. Copyright 2026 Rick Hightower / contributors.