kata-create-warrior

To create a specialized AI agent role definition, use a templated workflow to generate an artifact specifying identity, responsibilities, consultation chains, and escalation criteria, enforcing delimited scope to prevent responsibility overlap. This ensures agent-like roles have clear boundaries and safe operational guardrails.

A Warrior artifact in agent design is a fully specified role definition document containing identity, responsibilities, consultation chain, workflow, and escalation criteria. It serves as a knowledge architecture component that enforces responsibility boundaries and prevents scope creep among specialized agents.

To avoid responsibility overlap when initializing new agent-like roles, enforce delimited scope by consulting existing Warriors and generating explicit Does and Does Not responsibility lists. This validation process ensures clear boundaries and prevents scope creep across your agent architecture.

Yes, you can generate multilingual documentation for specialized agent workflows by creating the Warrior artifact in the default language and automatically saving translated versions across required languages. This ensures the role definitions and workflow specifications are accessible in all mandatory languages.

Before defining a new specialized agent, you need to read the .ahrena/.directives, codex-warriors, and templates/warrior-sample.md files. These inputs provide the necessary directives, quality criteria, and templates to produce a complete and validated Warrior artifact.

You should not use a templated approach for agent role generation when your use case requires highly dynamic, freeform agent behaviors that cannot be constrained by fixed responsibility boundaries or consultation chains. This method enforces strict scope and workflow specifications, limiting unstructured agent autonomy.