Create a new role with a sensible first draft of ROLE.md, a MEMORY.md file, and minimal role scaffolding.
Use this skill when the user wants to create a new role.
A role defines a reusable operating perspective for work, such as product strategist, delivery lead, researcher, or designer. Roles should be durable enough to reuse across multiple areas and projects.
Use references/ROLE.md as the canonical guide for the structure and content of ROLE.md.
Gather or infer the following:
If the request is straightforward, prefer making a sensible first draft over asking too many questions. Only stop to ask questions when the role boundary or purpose is genuinely unclear.
You must confirm the role name with the user before scaffolding anything. If the user suggests multiple possible names, ask them to choose one.
Create this structure:
roles/<role>/
ROLE.md
MEMORY.md
Use assets/MEMORY.md as the template for roles/<role>/MEMORY.md.
If it does not exist, create an empty MEMORY.md.
Create roles/<role>/ROLE.md as a sensible first draft based on the user request.
Populate the body sections with a sensible first draft based on the user request.
If some details are unknown, leave the structure in place and keep placeholders minimal and obvious.
The script is responsible for writing the frontmatter. Do not include frontmatter in the generated stdin content.
product-strategist, delivery-lead, or researcher when the workspace uses kebab-case.ROLE.md body, and ask the user to confirm them.After the user confirms the role name, pipe the generated ROLE.md body into scripts/create-role.sh.
Run the script in this form:
<ROLE.md body> | <skill dir>/scripts/create-role.sh <role-name> <role-description>
Pass the confirmed role name as the first argument.
Pass the short role description as the second argument.
Pass only the markdown body on stdin. Do not pass frontmatter.