persona-roster-expander

persona-roster-expander

Takes a seed set of named personas and turns it into a usable judgment cast: each persona tiered by a domain safety rule, mapped to a concrete decision-lens, plus a few proposed additions filling uncovered lenses with real anchors. An innovator-family skill — generative, but bounded by a caller-supplied safety rule so the expansion stays faithful to the domain's constraints.

Origin: harvested from the-bible (2026-06-20) — an operator persona seed (priest/nun/angel/devil/ God/Jesus/Holy-Spirit/apostles) tiered relay-vs-lens by a relay-safety rule and mapped to engineering-judgment lenses, +4 sourced proposals. The grounds, inline, because the harvest record does not ship: an ungated persona cast drifts into inventing its own authority — a voice given a lens will speak past what the domain lets it assert — so tiering by a caller-supplied rule is what keeps the expansion faithful, and the lens mapping is what makes a named voice usable as a decision instrument instead of flavor. Full harvest record — hub-local, not distributed in the npm package: tracks/_contrib/field_harvest_2026-06-20_gate-locality-and-grounding-capabilities.md.

Triggers

• "broaden these personas" / "what other voices fit this cast"
• "map these roles to a decision lens"
• "expand the persona roster and keep it faithful to "
• /persona-roster-expander {seed personas + domain + safety rule}

Natural Language Triggers (example user phrases)

• "내가 명명한 페르소나 후보군을 더 넓혀줘, 판단 매핑이랑 같이"
• "take these character archetypes and tell me what engineering judgment each one provides"
• "add a few more voices that cover a perspective these don't"

Steps

1. Collect the seed + the safety rule — the named personas, the domain (what decisions they reflect on), and the caller-supplied tiering rule (the hard constraint that decides what each persona is allowed to do). Without an explicit safety rule, ask for one — do not invent authority.
2. Tier each persona by the safety rule (e.g. relay/quote-only vs lens/framed-perspective). State a one-line justification per persona; the tier caps what the persona may emit.
3. Map each to a decision-lens in the user's domain vocabulary — what concrete judgment- perspective does this voice provide, and when to invoke it. Pair any adversarial voice with a constructive counter-voice (no adversary as the last word).
4. Propose 2–4 additions filling lenses the seed doesn't cover (delegate net-new name generation to the persona-innovator agent — this skill's distinct value is the tiering + lens-mapping, not naming). For the strongest 2–3, find a real anchor (a sourced example/reference); any remaining proposal ships with a literal stub: prefix — unanchored and unlabeled is not an allowed output (see Done When).
5. Emit the tiered, lens-mapped cast (named + proposed) by writing it to a structured file the system can load (e.g. personas.json), then confirm the written file parses. Leaving the cast in the response text only does not complete this step.