What problem does it solve? Personas in the Martinez Methods workflow need a machine-readable YAML manifest declaring their scope bounds, allowed paths, forbidden paths, and permitted operations so that commit-msg hooks can verify and enforce persona scope automatically. ## Core Features & Use Cases - Manifest Authoring: Produces a ~125-line role-manifest YAML with persona metadata, scope_bounds, allowed_repos, allowed_paths, forbidden_paths, and allowed_operations. - Scope-Bounds Heuristics: Applies family-based defaults (Clauda for non-coding docs paths, Claudette for coding repo paths) plus universal forbidden paths like secrets files. - YAML Validation: Validates the generated manifest with a YAML parser before writing it to the canonical role-manifests path. - Use Case: When defining a new persona via /define-your-role-literal Phase 8, invoke this skill to generate the manifest at role-manifests/<persona-slug>.yaml so Hook v05+ Tier 5 can verify its presence. ## Quick Start Ask the assistant to author a role-manifest YAML for a new persona, providing the persona slug, family, workstream, and scope bounds.