# Dev Test Parallel

> Dev-Test Parallel Team

- Skill: `openjiuwen-ai/dev-test-parallel` (Agent Skill, multi-file: 6 files)
- Install (CLI): `npx skillmds@latest add openjiuwen-ai/dev-test-parallel`
- Raw SKILL.md: https://api.skillmd.com/api/skills/openjiuwen-ai/dev-test-parallel/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: openJiuwen-ai (https://skillmd.com/u/openjiuwen-ai)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/openjiuwen-ai/dev-test-parallel

---


# Dev-Test Parallel Team

Two people in parallel: developer implements code, tester writes tests, invisible to each other, leader consolidates both outputs at the end. This is the **minimal example of the Parallel Decomposition pattern**, used as a reference sample when team-skill-creator generates new team skills.

## Workflow

The team follows this workflow (see [workflow.md](workflow.md) for details):

1. **Pre-flight** — Check python3 availability
2. **Parallel Execution** — developer writes code, tester writes tests, invisible to each other
3. **Final Report** — leader consolidates both outputs

## Role Responsibilities

| Role | Responsibility | Output |
| --- | --- | --- |
| developer | Implement functional code | .team/reports/T1_developer.md |
| tester | Write test cases | .team/reports/T2_tester.md |

## File List

- `SKILL.md` — This file, team metadata
- `roles/developer.md` — Developer role definition (with inline persona)
- `roles/tester.md` — Test engineer role definition (with inline persona)
- `workflow.md` — Complete execution script
- `bind.md` — Resource constraints and failure handling
- `dependencies.yaml` — External dependency declarations

