roles

Route user requests to specialized AI agent pipelines by engineering role.

1|1|Updated Jul 7, 2026
One-click install
npx skills add https://github.com/hicucu/my-poor-ai --skill roles-hicucu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: roles
Source: https://github.com/hicucu/my-poor-ai/tree/main/skills/roles
Command: npx skills add https://github.com/hicucu/my-poor-ai --skill roles-hicucu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of decision fatigue and inconsistent agent behavior by providing a structured routing layer that maps specific engineering roles to optimized task pipelines.

Core Features & Use Cases

  • Role-Based Routing: Instantly switch the agent's operational mode to architect, builder, debugger, reviewer, or documentation specialist.
  • Preset Catalog: Provides a clear, standardized interface for selecting the right toolset for the current development phase.
  • Use Case: When starting a new feature, invoke the builder role to automatically trigger the test-driven development and subagent-driven development pipeline.

Quick Start

Execute the roles skill with the architect argument to initialize the system architecture planning workflow.

Frequently Asked Questions about roles

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

FAQPage Schema
How do I automate AI agent routing for different software engineering tasks?

AI agent routing for software engineering tasks is automated by mapping predefined role names to specialized task pipelines. This routing layer enforces structured workflow transitions for architectural planning, debugging, and code review processes to ensure consistent task execution.

What is role-based workflow routing for AI development pipelines?

Role-based workflow routing for AI development pipelines is a mechanism that maps specific engineering roles to optimized task sequences. It eliminates decision fatigue and inconsistent agent behavior by providing a standardized interface for selecting the right toolset for the current development phase.

How do I switch an AI agent to a test-driven development workflow?

To switch an AI agent to a test-driven development workflow, invoke the builder role to automatically trigger the test-driven development and subagent-driven development pipeline. This role-based preset ensures consistent task execution for feature building.

Can I use preset engineering roles for architectural planning and code reviews?

Preset engineering roles can be used for architectural planning and code reviews by routing requests to specialized AI agent pipelines. Invoking the architect role initializes the system architecture planning workflow, while the reviewer role enforces structured code review transitions.

When should I use predefined AI engineering roles instead of manual prompting?

Predefined AI engineering roles should be used instead of manual prompting when you need consistent task execution across multiple development phases. They provide a structured routing layer that eliminates decision fatigue and enforces standardized transitions for debugging and documentation processes.