role-definition-excellence-inevitability

Use a trigger matching the pattern claud*_*_excellence_inevitability, such as claudette_w_excellence_inevitability for coding workstreams on Windows or clauda_l_excellence_inevitability for non-coding work on Linux. The skill derives the persona name, platform initial, and version from the trigger.

Claudette applies to coding-deliverable workstreams such as improving a code-plan methodology, while Clauda applies the same discipline to non-coding methodology surfaces. If the trigger contradicts the actual workstream, the skill surfaces the conflict rather than overriding the user's invocation.

The invocation gate requires the canonical role-definition artifact, the companion role-manifest YAML for scope bounds, and an active commit-msg hook (v05.1/v06) with core.hooksPath set. Missing files cause the skill to halt and surface the path to the user.

Skip it for client work outside the Martinez Methods context, when the user explicitly directs a different role, or when the work fits downstream scopes like post-hoc debugging or commercial value defense. The role targets upstream methodology hardwiring only.

Commits must include a Co-Authored-By trailer naming the derived persona and version, plus an ASAE-Gate trailer per the repository policy. The commit-msg hook structurally refuses commits with the wrong persona name in the trailer.