gtm-persona

GTM Persona

Trigger

Apply this Lifecycle SOP when the requested outcome creates, updates, repairs, or retires a buyer or stakeholder persona owned by an organization node in an existing GTM workspace.

Scope

Own node-local, freeform Markdown personas at personas/<persona-slug>/PERSONA.md across creation, refinement, deletion, and repo-wide persona integrity repair. Read legacy personas/<persona-slug>.md artifacts without requiring migration. Do not author ICP or member files, manage the workspace lifecycle, or classify/research leads against saved personas.

Contract

Field	Public contract
Reads	Accepted persona facts and uncertainty, the root-to-owner ORG.md chain, owner-local personas, and safe supplied sources
Writes	Only the selected owner's canonical persona path, or scoped persona repairs during doctor
Outputs	An accepted node-owned persona and qualified label, a complete health report, or a scoped handoff
Approval	The user accepts the complete bytes and exact path operation before any durable write or deletion
Persists	Accepted persona files in main Git history; no hidden coordination state
Handoff	gtm-workspace for repository structure or connections, gtm-icp for markets, and gtm-workflow for saved operational work

Inputs

Use the user's accepted persona facts and uncertainty, the hosting environment's connected-repo and durable-write declarations, the root-to-owner ORG.md chain, owner-local personas, and safe supplied sources.

Roles

The agent owns the selected persona lifecycle flow. The user accepts durable changes. gtm-workspace owns repository structure and connections; the hosting environment declares fixed connections and any replacement persistence mechanism.

Procedure

Condition	Owned flow
The requested outcome belongs to a sibling workflow	Hand off before workspace resolution or artifact reads; mutate nothing
No lifecycle verb is clear	Guide the persona lifecycle menu and retain ownership of the selected flow
Create or define is requested	Resolve the workspace and owner node, ground a factual draft, check owner-local overlap, preview it, and save the accepted persona
Update or refine is requested	Resolve one visible persona, preserve unrelated facts, preview complete before/after bytes, and save the accepted revision
Delete is requested	Resolve one visible persona, preview ownership and consequences, remove only the accepted target, and explain history recovery
Doctor is requested or persona artifacts seem malformed	Inspect persona placement and content repo-wide, preview one scoped repair set, save it once, and report resulting health

Outputs

Produce the accepted node-owned persona state and its qualified label, or a complete persona health report. A request owned by a sibling workflow produces only a scoped handoff and no artifact mutation.

Exceptions

If no valid workspace is connected or discoverable, stop without writing and direct workspace creation or connection to gtm-workspace. If a required reference is unavailable or the environment cannot durably save the accepted operation, keep the repo unchanged and use the prescribed recovery.

QC

• Begin every question-bearing message with its single bold question without AskUserQuestion; put context and numbered choices below it, mark at most option 1 (Recommended), and end choices exactly Reply with a number, or type your answer.
• Preserve every supplied responsibility, influence fact, authority boundary, disqualifier, and uncertainty; organization facts and adjacent personas are a factual ceiling, never evidence for invented persona claims.
• Preview complete accepted bytes and exact path operations before writing, create new personas only at the canonical nested path, preserve legacy reads and node-local visibility, and mutate only persona paths.
• Keep accepted changes on main, stage only accepted persona paths, inspect the staged diff, and describe a verified durable result as “saved to history.”

References

• Read the persona contract for every flow; it defines workspace resolution, ownership, visibility, content, acceptance, safety, and persistence.
• Read the persona lifecycle flows after selecting the Procedure row; they define menu, create, update, delete, doctor, recovery, and closure.
• Render the persona draft template only for create; it is a starting shape, not a schema or validity test.