using-domain-teams

Routes domain-specific tasks to the correct team based on intent and required deliverables.

6|1|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/kouko/monkey-skills --skill using-domain-teams
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-domain-teams
Source: https://github.com/kouko/monkey-skills/tree/main/domain-teams/skills/using-domain-teams
Command: npx skills add https://github.com/kouko/monkey-skills --skill using-domain-teams

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates uncertainty about which domain-specialized team should handle a request and streamlines routing so work starts with the right expertise and expected deliverables.

Core Features & Use Cases

  • Intent Routing: Translate task descriptions into the appropriate domain team selection (code, docs, qa, devops, design, research, planning, copywriting, skill-team, investing).
  • Deliverable Guidance & Ambiguity Handling: Recommend concrete artifacts (e.g., PRODUCT-SPEC.md, TECH-SPEC.md, TEST-PLAN.md, DEPLOY-SPEC.md) and provide sequencing advice when tasks cross domains.
  • Quality Gate Integration: Surface team responsibilities and connect to shared agents for execution and evaluation, enabling checkpoint-based reviews and pass/fail or rubric-driven verdicts.
  • Use Case: When initiating a new feature, use this Skill to determine whether to start with research, planning, design, or direct implementation and to get the expected outputs for handoff.

Quick Start

Ask using-domain-teams to route this request: Draft a PRODUCT-SPEC.md for a new user onboarding feature and identify the next team steps.

Frequently Asked Questions about using-domain-teams

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

FAQPage Schema
How do I route software development tasks to the correct domain team?

Route software development tasks by mapping task intents and required deliverables to specialized domain teams. This ensures work starts with the right expertise, whether it involves coding, documentation, QA, or DevOps.

What deliverables should I expect when planning a new feature across multiple teams?

When planning a new feature, expect concrete artifacts like PRODUCT-SPEC.md, TECH-SPEC.md, or DEPLOY-SPEC.md. The routing process recommends these deliverables and provides sequencing advice for cross-domain handoffs.

How do I determine whether to start a project with research, planning, or direct implementation?

Determine project kickoff phases by evaluating task intent against domain specializations. The routing mechanism translates request descriptions into team selection, advising whether to begin with research, design, planning, or coding.

Can I enforce checkpoint-based quality gates during team task routing?

Yes, you can enforce checkpoint-based quality gates by integrating routing with worker and evaluator agents. This surfaces team responsibilities and enables pass/fail or rubric-driven verdicts during reviews.

What is the best way to handle ambiguous requests that cross multiple domains?

Handle ambiguous cross-domain requests by using intent mapping to identify expected artifacts and provide sequencing advice. This clarifies team boundaries and streamlines handoffs for complex workflows.

Does this task routing approach work for non-coding scenarios like copywriting and skill development?

Yes, this task routing approach works across diverse project workflows including copywriting, research, design, and skill development. It maps intents to specialized teams like copywriting or skill-team based on the request.