design-sub-agents

Design adversarial reviewer personas that critique creation skill outputs for edge cases.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/SujinHwang27/agent-os-lab --skill design-sub-agents
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-sub-agents
Source: https://github.com/SujinHwang27/agent-os-lab/tree/main/agent-os-factory-v2.0/.claude/skills/design-sub-agents
Command: npx skills add https://github.com/SujinHwang27/agent-os-lab --skill design-sub-agents

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design-sub-agent reviewer lenses introduce adversarial perspectives to quality gates, ensuring outputs from creation skills are challenged for edge cases and biases.

Core Features & Use Cases

  • Adversarial reviewer personas: distinct lenses that protect outputs by challenging assumptions and catching subtle errors.
  • Structured design workflow: defines how sub-agents map to audiences, triggers, and evaluation priorities.
  • Use Case: When designing a new agent OS, use these reviewer sub-agents after /define-audiences and /design-skills to validate outputs from creation skills.

Quick Start

Draft 2-4 reviewer personas with distinct evaluation lenses and wire them into the trigger map after /design-skills

Frequently Asked Questions about design-sub-agents

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

FAQPage Schema
How do I design adversarial reviewer sub-agents to catch missed edge cases?

Design adversarial reviewer sub-agents by defining distinct personas that critique outputs from creation skills, ensuring edge cases and biases are challenged. Wire these personas into the trigger map to validate agent outputs.

What is an adversarial reviewer persona in prompt design?

An adversarial reviewer persona is a distinct lens in prompt design that protects outputs by challenging assumptions and catching subtle errors. It introduces adversarial perspectives to quality gates, ensuring outputs are validated against edge cases.

When should I introduce sub-agents into my agent OS design workflow?

Introduce sub-agents after defining audiences and designing skills, when domain-input/audiences.md has sub-agent candidates. These reviewer personas validate outputs by mapping to sub-agent design templates and defining trigger integration.

How do I map reviewer sub-agents to evaluation priorities and triggers?

Map reviewer sub-agents by defining trigger integration and evaluation priorities that align with the sub-agents directory for the target OS. This structured workflow ensures personas map to audiences and validate creation skill outputs.

How many reviewer personas do I need to draft for a quality gate?

Draft 2-4 reviewer personas with distinct evaluation lenses to establish effective quality gates. Wire these adversarial reviewer sub-agents into the trigger map after designing skills to challenge output assumptions and catch biases.

Can I use adversarial sub-agents to validate outputs from creation skills?

Yes, adversarial sub-agents validate outputs from creation skills by introducing reviewer lenses that challenge assumptions and catch subtle errors. They act as quality gates, ensuring outputs are tested for edge cases and biases.