author-role-definition

Generates a 12-section canonical role-definition markdown artifact for Martinez Methods personas.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/gozonerd/shadow-ai-assessment --skill author-role-definition-gozonerd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: author-role-definition
Source: https://github.com/gozonerd/shadow-ai-assessment/tree/main/.claude/skills/author-role-definition
Command: npx skills add https://github.com/gozonerd/shadow-ai-assessment --skill author-role-definition-gozonerd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Personas in the Martinez Methods methodology need a canonical identity source-of-truth document, but authoring one manually risks inconsistent structure, missing sections, and broken cross-references with the other four persona artifacts. ## Core Features & Use Cases - Enforced 12-Section Structure: Produces lineage, derived full name, multiplicative compound-name meaning, mission, authority basis, axis-by-axis defense, operating constraints, refusals, rejected alternatives, versioning, and honest gaps. - Dual Invocation Modes: Runs as Phase 8 step 1 of the /define-your-role-literal meta-skill, or standalone to migrate pre-existing personas to the canonical format. - Consistency Validation: Checks naming rules, per-axis evidence, a minimum of 6 rejected alternatives, and at least 4 honest gaps before writing. - Use Case: After deriving a new persona in /define-your-role-literal Phase 7, invoke this skill to materialize the approved derivation as a versioned markdown file at _grand_repo/docs/Role_Definition_<Name>_<date>_v01_I.md. ## Quick Start Invoke /author-role-definition with the persona derivation context from Phase 7 to write the canonical role-definition markdown file to the default docs path.

Frequently Asked Questions about author-role-definition

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

FAQPage Schema
How do I author a canonical role-definition artifact for a persona?

Invoke /author-role-definition with the persona derivation context, either from /define-your-role-literal Phase 7 output or interactively in standalone mode. The skill composes the 12-section markdown, validates consistency rules, and writes it to the canonical _grand_repo/docs path.

What sections does the role-definition document require?

The artifact enforces 12 sections: lineage, derived full name, multiplicative compound meaning, mission, authority basis, axis-by-axis defense, operating constraints, refusals, rejected alternatives, richer-grounding delta, versioning, and honest gaps.

Can I migrate an existing persona to the canonical role-definition format?

Yes, standalone migration mode accepts a persona slug, workstream description, and minimal context, then prompts you interactively for the axis-by-axis defense and rejected alternatives before producing the artifact.

When should I not use the author-role-definition skill?

Do not use it for the other four persona artifacts: role-manifest YAML, lock-in skill, propagation script, or first-gate audit log, which have their own sibling skills. Also avoid it for re-deriving an existing persona, which requires the full /define-your-role-literal flow.

What are the limitations of the v01 role-definition skill?

Version v01 produces a minimal-viable artifact whose content depth depends on input richness, has no fixture-test corpus, requires user interaction in standalone migration mode, and supports only single-thread authoring.