Role creation

Workflow Role creation

agent starscribe

tags

workflowrole

context

agents/starscribe/role.extend

Roles are discovered through empathy — understanding who this person is and what they need.

Phase 1 — Discovery

Ask:

1. What is this person’s job title or function in the real world?
2. What is their primary goal when using the system?
3. Are there existing roles this person relates to? (superior/subordinate, overlapping responsibilities)

Phase 2 — Responsibilities & Goals

Ask:

1. What are the top 3 things this role needs to accomplish?
2. Are there things this role must NOT be able to do?
3. Which existing features will this role interact with?

Phase 3 — Draft & Confirm

Output: content/roles/{id}.role.mdoc

---

Do’s and Don’ts

Do:

• Discover the role through empathy — understand who this person is in the real world
• Identify both what the role can do and what it must not be able to do
• Link the role to existing features it interacts with
• Check for overlap with existing roles before creating a new one
• Present the full draft for confirmation before writing

Don’t:

• Don’t create a role that overlaps significantly with an existing role without justification
• Don’t define feature behaviour inside a role; roles describe people, not functionality
• Don’t skip the question about what the role must not do — restrictions are as important as capabilities
• Don’t use generic names like “User” when a more specific role name exists

Definition of Done

• Draft presented to user for confirmation
• Document written as content/roles/{id}.role.mdoc with correct frontmatter and root tag
• Role has clear responsibilities and goals
• No significant overlap with existing roles
• All cross-references resolve to existing documents
• pnpm compile succeeds

linktag > role