dd-shared-subagent

Coordinates three parallel review subagents with direction-based division and result aggregation rules.

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/marcocpt/trae_skills --skill dd-shared-subagent-marcocpt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dd-shared-subagent
Source: https://github.com/marcocpt/trae_skills/tree/main/dd-shared-subagent
Command: npx skills add https://github.com/marcocpt/trae_skills --skill dd-shared-subagent-marcocpt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Single-agent reviews in AI workflows can miss issues due to limited coverage and LLM blind spots. This Skill defines a shared three-subagent parallel review pattern so that all check-type steps in dd-series workflows (design review, plan check, code check, documentation check) are verified by multiple independent agents instead of one. ## Core Features & Use Cases - Direction-Based Division: Three subagents split work across Coverage & Scope, Consistency & Correctness, and Verifiability & Observability, maximizing review coverage. - Redundant UI Checks: UI observability is a mandatory check item for all three agents, with N/3 vote counting to catch blind spots. - Aggregation & Graded Handling: Results are merged with a strictest-conclusion-wins rule, classified into must-fix / suggested / optional tiers, with automatic fixes and up to 3 retry rounds before escalating to the user. - Use Case: When running dd-ai-refactor-workflow or dd-feature-development-workflow, any review step dispatches three Task subagents in one message, then aggregates their findings into a summary report. ## Quick Start Apply the three-subagent parallel review rules from dd-shared-subagent to the current check step and aggregate the findings.

Frequently Asked Questions about dd-shared-subagent

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

FAQPage Schema
How do I run parallel code review with multiple AI subagents?

Dispatch three Task subagents in a single message so they run concurrently without communicating. Assign each a distinct review direction, then aggregate their findings after all three return.

How to divide review responsibilities among multiple review agents?

Split reviews into three directions: Coverage & Scope (completeness, YAGNI, spec compliance), Consistency & Correctness (standards, contradictions), and Verifiability & Observability (testability, real UI evidence). Each agent owns one direction.

How do I resolve conflicting findings from parallel review agents?

Apply a strictest-conclusion-wins rule: if any agent reports a problem, it counts as a problem. For mandatory UI checks, track N/3 vote counts, where 3/3 agreement carries the highest weight.

When should review findings be auto-fixed versus escalated to the user?

Must-fix findings are auto-applied and re-reviewed; suggested or optional items are auto-skipped unless they involve major architecture or product changes. After three failed retry rounds, escalate via AskUserQuestion.

Does the three-subagent review rule apply to lint and test commands?

No. The rule only covers subagent-based review steps such as design, plan, code, and documentation checks. Command-based checks like lint and test in step 8.1 follow their original command flow.