persona

honne — Persona Synthesis

When invoked, execute Step 1 through Step 5 in order immediately. Do not summarize the skill or ask what the user wants — invocation itself is the request. Start by asking the Step 1 question.

Step 1: Locale HITL

Invoke AskUserQuestion tool:

• question: "Locale?"
• options: [{"label":"ko","description":"한국어"},{"label":"en","description":"English"},{"label":"jp","description":"日本語"}]

Set LOCALE from the reply. Do not use plain-text Q&A — arrow-key selection only.

Step 2: Load and Validate

Check that persona.json exists:

bash "${CLAUDE_PLUGIN_ROOT}/scripts/honne" persona check --persona .honne/persona.json

• Exit 66 → tell user: ".honne/persona.json not found. Please run /honne:whoami first to generate your persona." Stop.
• Exit 0 → proceed.

Check staleness:

python3 -c "import json,datetime; d=json.load(open('.honne/persona.json')); ts=datetime.datetime.fromisoformat(d.get('generated_at','2000-01-01T00:00:00Z').replace('Z','+00:00')); print((datetime.datetime.now(datetime.timezone.utc)-ts).days)"

Capture stdout as STALE_DAYS.

If STALE_DAYS exceeds 7 (or the value of HONNE_PERSONA_STALE_DAYS if set): warn "persona.json last updated {STALE_DAYS} days ago — consider re-running /honne:whoami." Then continue.

Step 3: Build Conflict Payload

Read .honne/persona.json in your mental context. Construct CONFLICT_PAYLOAD as a JSON object without writing to any file or using heredocs:

CONFLICT_PAYLOAD = {
  "locale": "<LOCALE>",
  "antipattern": {
    "claim": "<axes.antipattern.claim>",
    "explanation": "<axes.antipattern.explanation>",
    "evidence_strength": <axes.antipattern.evidence_strength>
  }  — or null if antipattern axis is absent or claim is null,
  "signature": {
    "claim": "<axes.signature.claim>",
    "explanation": "<axes.signature.explanation>",
    "evidence_strength": <axes.signature.evidence_strength>
  }  — or null if signature axis is absent or claim is null,
  "supporting_axes": {
    "<axis>": {"claim": "...", "explanation": "...", "evidence_strength": <val>}
    for each of the 5 remaining axes: lexicon, reaction, workflow, obsession, ritual
  }
}