What problem does it solve?
Managing team role composition across a BotMinter repository is error prone and fragmented: roles, statuses, hats, and knowledge live in multiple files and directories and manual changes can orphan issues or break workflows. This Skill centralizes listing, adding, inspecting, and removing roles and ensures each change is validated, applied to botminter.yml and role directories, and recorded as a team decision.
Core Features & Use Cases
- List and inspect roles with descriptions, member counts, associated statuses, hats, skills, knowledge, and invariants for quick visibility into team structure.
- Add roles via a guided conversational workflow that defines statuses, hats, skeleton files, updates botminter.yml, and writes a decision record to agreements/decisions/.
- Remove roles only after performing an impact analysis of active members, statuses, issues, and hat references, requiring explicit operator confirmation before deletion and recording the decision.
- Use Case: When a cos:todo asks for a new role, run the add-role workflow to create the directory skeleton, update configuration, and produce an auditable decision file.
Quick Start
Ask the chief-of-staff to add a new role by providing the role name, a short description, and the statuses the role should own.
