persona-roster-expander
Expands a named persona seed into a tiered, judgment-mapped cast — tiering each persona by a domain safety rule, mapping each to a decision-lens in the user's vocabulary, then proposing additional voices with sourced anchors.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 33
- Forks
- 1
01 前言 Front Matter
- name
- persona-roster-expander
- model
- sonnet
- description
- Expands a named persona seed into a tiered, judgment-mapped cast — tiering each persona by a domain safety rule, mapping each to a decision-lens in the user's vocabulary, then proposing additional voices with sourced anchors.
- allowed-tools
- [ "Read", "Grep", "WebSearch", "WebFetch", "Write", "Agent" ]
- user-invocable
- true
03 SKILL.md 正文
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 <rule>"
/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
- 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.
- 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.
- 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).
- Propose 2–4 additions filling lenses the seed doesn't cover (delegate net-new name
generation to the
persona-innovatoragent — 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 literalstub:prefix — unanchored and unlabeled is not an allowed output (see Done When). - 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.
Done When
- Every persona has a tier + lens label + invoke-condition. Check class: mandatory-pass (binary — all three fields present per persona).
- Every proposal is either anchored or explicitly labeled a stub. An anchored proposal names a source/reference that resolves; a proposal without one is emitted with a literal
stub:prefix and is not counted as a candidate. Check class: mandatory-pass (binary — each proposal carries either a resolving anchor or astub:label; an unanchored, unlabeled proposal is FAIL). Anchor resolution is checked mechanically (fetch/look up the cited reference), not by judgment. (This is the Done-When floor; Step 4's "strongest 2–3" is the effort target that sits above it — a 4th proposal may ship asstub:without violating either.) - The cast is materialized as a loadable artifact (e.g.
personas.json) that a consumer can parse — the file exists on disk and a parse of it succeeds against the declared schema (per persona: tier / lens / invoke-condition; per proposal additionallyanchororstub:). Check class: mandatory-pass (binary — file exists and parses; a cast that exists only in the response text is UNMET). - The tiering respects the caller's safety rule (no persona exceeds its tier's allowed emission). Check class: judged, pair: dispatch
fh-meta:challengerat the tier-escalation angle — "find a persona whose lens mapping lets it emit beyond its tier". The pairing is a different-agent read; the author's own re-read does not satisfy it. If that agent is unreachable, recordpair: unavailable (<reason>)— the condition stays UNMET and is reported as a named residual, never self-scored closed. It does not block delivery: a roster is a reversible artifact, so the degrade direction here is declare-and-ship, not fail-closed (that direction is reserved for irreversible surfaces — publish, delete, history-rewrite). Shipping with an UNMET pairing is honest; silently marking it met is the defect.
Guards
- Caller-supplied safety rule is mandatory — the skill tiers by the domain's rule, it does not invent one (inventing authority is the failure this guard prevents).
- Adversary never last — any devil's-advocate voice is paired with a constructive counter-voice.
- Anchors must be real — a proposal without a resolvable anchor is a stub, not a candidate.
Relationship to persona-innovator (agent)
persona-innovator generates names, frames, and frontier-absorption signals from scratch. This skill
takes an existing seed and adds the tier-by-safety-rule + lens-to-domain mapping — it is the
structuring/governance layer, not the generator. When net-new names are needed (Step 4), it
delegates to persona-innovator rather than reinventing generation.
Independently executable
Yes — needs only the seed + rule + (for anchors) web search. Delegates name generation to
persona-innovator when invoked, but has no hard dependency on it for the core tier+lens mapping.
04 同仓库更多 Skills
todo-orchestrator
TODO CLI 프로젝트의 기능 추가·버그 수정·리팩터링·테스트 보강을 개발자와 QA 에이전트로 조율한다. todo 앱 관련 코드 작업 요청에 사용한다. 다시 실행, 재실행, 수정, 보완, 이전 결과 개선, QA만 다시 같은 후속 요청에도 사용한다. 단순 질문에는 사용하지 않는다.
todo-dev
TODO CLI(todo/cli.py)에 명령을 추가하거나 버그를 고치고 테스트를 작성하는 방법. todo 앱 코드 수정·기능 추가·테스트 작성·리팩터링 작업에 사용한다. 수정, 보완, 다시 구현 요청에도 사용한다.
todo-dev-team
TODO CLI(todo/cli.py) 개발 작업을 개발자·테스터·리뷰어 팀으로 진행하는 오케스트레이터. 명령 추가, 버그 수정, 테스트 작성, 리팩터링, 커밋·푸시 요청에 사용한다. 다시 실행, 재실행, 수정, 보완, 리뷰 반영, 테스트만 다시 같은 후속 요청에도 사용한다. 단순 질문에는 쓰지 않는다.
todo-dev
TODO CLI 개발 작업(명령·기능 추가, 버그 수정, 테스트 작성, 리뷰, 커밋·push)을 개발자·테스터·리뷰어 에이전트 팀으로 진행하는 오케스트레이터. todo CLI, todo.json, todo/cli.py 관련 구현·수정·테스트 요청에 사용한다. 재실행, 수정, 보완, 이전 결과 개선, 테스트만 다시, 리뷰만 다시 요청에도 사용한다. 단순 질문에는 쓰지 않는다.
weekly-summary-write
정리된 회의록으로 주간 회의 요약 문서를 작성하는 형식과 문체 규칙. 주간 요약 작성, 요약 문서 수정·보완, 검토 의견 반영 시 사용한다.
weekly-meeting-summary
주간 회의록을 정리하고 요약 문서를 만드는 전체 작업을 조율하는 오케스트레이터. 회의록 요약, 주간 회의 정리, 주간 보고용 요약 요청 시 사용한다. 다시 실행, 재실행, 요약 수정·보완, 이전 결과를 바탕으로 한 개선, 정리만/검토만 다시 같은 후속 요청에도 사용한다.