Create the Roles directory with initial role definitions for the product org model. Roles are small prompt fragments that define a perspective/lens for thinking about problems.
Omni/Agent/Roles/
├── Product.md
├── Designer.md
├── Engineer.md
└── Reviewer.md
Each role file has YAML frontmatter and a markdown body:
---
name: product
description: Product/business perspective for feature development
---
When thinking as Product, focus on:
- User value: What problem does this solve? Who benefits?
- Scope control: What's the minimum viable solution?
- Prioritization: Is this the most important thing to work on?
- Acceptance criteria: How do we know when it's done?
- Saying no: What should we explicitly NOT do?
Ask yourself:
- Would a user pay for this?
- Can I explain this in one sentence?
- What's the worst case if we ship this?
Focus on: user value, scope control, prioritization, acceptance criteria, saying no to scope creep. Asks: would a user pay for this? Can I explain it simply?
Focus on: usability, accessibility, edge cases, error states, user mental models, visual consistency. Asks: what happens when things go wrong? Is this intuitive?
Focus on: correctness, testing, maintainability, conventions, performance, security. Asks: how do I know this works? What could break?
Focus on: checking work against spec, catching missed requirements, verifying quality. Asks: does this satisfy the original goal? What was missed?
<role:X> tagsOmni/Agent/Roles/ directory created