describe-agent-roles

Define and enforce agent role responsibilities and boundaries for software projects.

7|1|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/adamrdrew/ushabti --skill describe-agent-roles
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: describe-agent-roles
Source: https://github.com/adamrdrew/ushabti/tree/main/skills/describe-agent-roles
Command: npx skills add https://github.com/adamrdrew/ushabti --skill describe-agent-roles

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill defines clear role responsibilities and hard boundaries to prevent cross-role work in collaborative software projects.

Core Features & Use Cases

  • Role separation guidelines: outlines distinct responsibilities for Lawgiver, Artisan, Scribe, Builder, and Overseer to reduce overlap.
  • Governance and compliance: helps teams enforce process rules and prevent role violations.
  • Use Case: In a multi-agent workflow, ensure that each agent sticks to its assigned tasks and flags violations.

Quick Start

Summarize and enforce distinct agent roles and boundaries for a software project.

Frequently Asked Questions about describe-agent-roles

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I define agent roles and enforce boundaries in a multi-agent workflow?

To define agent roles and enforce boundaries, outline distinct responsibilities for roles like Lawgiver, Artisan, Scribe, Builder, and Overseer, then apply a validation framework to prevent cross-role work and flag violations during team planning or code reviews.

What is agent role separation in collaborative software projects?

Agent role separation is the process of assigning distinct responsibilities and hard boundaries to individual agents in a collaborative software project to reduce overlap, prevent cross-role work, and maintain strict process governance.

How do I prevent role violations during team code reviews and planning?

Prevent role violations during team code reviews by establishing a validation framework that checks assigned agent responsibilities against actual work performed, ensuring no agent crosses its defined boundaries during governance processes.

Can I use this skill to govern workflows with custom agent names?

This skill is specifically applicable to workflows using roles such as Lawgiver, Artisan, Scribe, Builder, and Overseer. You must provide clear role definitions matching these types to successfully enforce boundaries and prevent cross-role work.

What is the best way to structure process governance for multi-agent software projects?

The best way to structure process governance is to define distinct responsibilities for each agent role and implement a validation framework that flags boundary violations, ensuring strict compliance with team workflow rules.