القائمة
Coordinates QA workflow across planning, writing, and execution agents. Use when user requests testing, quality assurance, or test documentation.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Pre-action boundary checking — validates agent tool calls against declared capabilities and task contracts
Auto-detect project context and optimize harness — deactivate unused agents/skills, suggest missing experts, generate project profile
Multi-LLM adversarial consensus loop — 3+ LLMs compete to find flaws in designs/specs until unanimous agreement is reached
Monitor Claude Code releases and auto-generate GitHub issues for each new version
Execute OpenAI Codex CLI prompts and return results
YAML-based DAG workflow engine with topological execution and failure strategies
| name | qa-lead-routing |
| description | Coordinates QA workflow across planning, writing, and execution agents. Use when user requests testing, quality assurance, or test documentation. |
| scope | core |
| user-invocable | false |
| context | fork |
Coordinates QA team activities by routing tasks to qa-planner, qa-writer, and qa-engineer agents. This skill contains the coordination logic for orchestrating the complete quality assurance workflow.
| Agent | Role | Output |
|---|---|---|
| qa-planner | Test planning | QA plans, test scenarios, acceptance criteria |
| qa-writer | Documentation | Test cases, test reports, templates |
| qa-engineer | Execution | Test results, defect reports, coverage reports |
Before routing via Agent tool, evaluate Agent Teams eligibility first:
Self-check: Does this task need 3+ agents, shared state, or inter-agent communication? If yes, prefer Agent Teams over Agent tool. See R018 for the full decision matrix.
| Scenario | Preferred |
|---|---|
| Single QA phase (plan/write/execute) | Agent Tool |
| Full QA cycle (plan + write + execute + report) | Agent Teams |
| Quality analysis (parallel strategy + results) | Agent Teams |
| Quick test validation | Agent Tool |
QA Request → Routing → QA Agent(s)
test_planning → qa-planner
test_documentation → qa-writer
test_execution → qa-engineer
quality_analysis → qa-planner + qa-engineer (parallel)
full_qa_cycle → all agents (sequential)
Permission Mode: When spawning agents, pass
mode: "bypassPermissions"in the Agent tool call if the session uses bypassPermissions. Without explicit mode, CC defaults toacceptEdits.
If get_agent_for_task MCP tool is available, call it with the original query and inject suggested_skills into the agent prompt. Skip silently on failure.
If the selected agent has soul: true in frontmatter, read and prepend .codex/agents/souls/{agent-name}.soul.md content to the prompt. Skip silently if file doesn't exist.
Full QA cycle follows sequential phases (each depends on the previous):
qa-planner → qa-writer → qa-engineer → qa-writer
(plan) (document) (execute) (report)
Parallel execution only for independent analyses (e.g., multi-module testing). See R009.
All QA agents use sonnet by default for balanced quality output.
When a QA task involves unfamiliar testing patterns or tools:
User Input → QA task with unrecognized tool/pattern
↓
Detect: Testing framework or QA methodology keyword
↓
Delegate to mgr-creator with context:
domain: detected QA tool/methodology
type: qa-engineer
keywords: extracted testing terms
skills: auto-discover from .codex/skills/
guides: auto-discover from templates/guides/
Examples of dynamic creation triggers:
This skill is NOT user-invocable. It should be automatically triggered when the main conversation detects QA intent.
Detection criteria: