persona-roster-expander

Convert persona seeds into tiered, lens-mapped judgment casts with safety rules.

7|Updated May 26, 2026
One-click install
npx skills add https://github.com/chrono-meta/forge-harness --skill persona-roster-expander
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: persona-roster-expander
Source: https://github.com/chrono-meta/forge-harness/tree/main/plugins/fh-meta/skills/persona-roster-expander
Command: npx skills add https://github.com/chrono-meta/forge-harness --skill persona-roster-expander

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of turning small, unorganized sets of named personas into structured, domain-aligned judgment casts that respect explicit safety constraints, eliminating inconsistent or unsafe persona use in decision-making workflows.

Core Features & Use Cases

  • Safety-Aligned Tiering: Assigns each persona to a tier defined by your caller-supplied domain safety rule, capping what each persona is allowed to emit to prevent overreach.
  • Decision-Lens Mapping: Maps every persona to a concrete judgment perspective in your domain's vocabulary, with clear conditions for when to invoke each voice, and pairs adversarial personas with constructive counter-voices.
  • Anchored Expansion: Proposes 2-4 additional personas that fill uncovered judgment lenses, with real sourced anchors for the strongest candidates to avoid shallow, unsubstantiated additions.
  • Structured Output: Emits a ready-to-load personas.json artifact that integrates directly with your existing systems. Use Case: For a software engineering team, input a seed set of "senior developer, QA engineer, product manager" plus a safety rule that prohibits personas from making final architectural decisions, and get a fully tiered, lens-mapped cast with additional relevant voices like "security auditor" anchored to real industry security standards.

Quick Start

Use the persona-roster-expander skill to turn your seed personas for your target domain into a tiered, judgment-mapped cast that strictly follows your specified safety rule.

Frequently Asked Questions about persona-roster-expander

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure unstructured persona seeds into a safe judgment cast for domain-specific decision-making?

You can structure persona seeds by applying caller-supplied domain safety rules to tier permissions, mapping each persona to concrete decision lenses, and sourcing external anchors to eliminate shallow stubs.

What is decision-lens mapping for persona governance in engineering workflows?

Decision-lens mapping assigns each persona a specific judgment perspective in your domain vocabulary, defining when to invoke each voice and pairing adversarial personas with constructive counter-voices.

How do I enforce safety tiering to cap what permissions a persona is allowed to emit?

Enforce safety tiering by supplying explicit domain safety rules that assign each persona a tier, capping what they are allowed to emit to prevent overreach in assessment workflows.

Can I expand a small set of named personas with additional roles anchored to real industry standards?

Yes, persona expansion proposes 2-4 additional personas to fill uncovered judgment lenses, sourcing real external anchors for the strongest candidates to eliminate shallow stubs.

What is the best way to integrate a structured persona roster into existing engineering systems?

The best way to integrate a structured persona roster is to use the generated personas.json artifact, a ready-to-load file that enforces safety tiers and decision lenses, connecting directly with existing systems.

When should I not use automated persona expansion for cast structuring?

You should avoid automated persona expansion when you lack explicit caller-supplied domain safety rules, as the system depends on these rules to tier permissions and prevent judgment overreach.