Decomposes feature requests into concrete, parallelizable tasks for the agent team. Identifies file domains, defines API contracts via Apidog MCP, creates dependency-aware task lists, and determines optimal spawn order. Automatically loaded by the team-lead agent during planning.
From ennam-dev-agent-teamnpx claudepluginhub en-nam/ennam-claude-agent-team --plugin ennam-dev-agent-teamThis skill uses the workspace's default tool permissions.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Guides idea refinement into designs: explores context, asks questions one-by-one, proposes approaches, presents sections for approval, writes/review specs before coding.
When the team-lead receives a feature request, follow this protocol to break it into parallel-safe tasks before spawning any workers.
Scan the feature requirements and map every piece of work to a domain:
| Domain | Owner | Directories |
|---|---|---|
| Backend | backend-dev | src/app/api/, src/services/, src/lib/server/, prisma/ |
| Web Frontend | web-dev | src/app/ (non-api), src/components/, src/hooks/, src/lib/client/, src/styles/ |
| Mobile | mobile-dev | lib/, android/, ios/, test/, integration_test/, pubspec.yaml |
| Tests | test-worker | tests/, __tests__/, **/*.test.*, **/*.spec.* |
| Shared | team-lead | src/types/, package.json, tsconfig.json, next.config.*, pubspec.yaml (coordinated) |
If a feature only touches ONE domain, consider using a single worker instead of a full team deployment.
Before spawning workers, detect which domains are relevant:
# Check for web project
test -f tsconfig.json && echo "WEB"
# Check for mobile project
test -f pubspec.yaml && echo "MOBILE"
# Check for backend project (implied by web or standalone)
test -d src/app/api/ && echo "BACKEND"
Only spawn workers for domains that the feature actually touches.
Before spawning ANY workers, if both backend and frontend are involved:
Query Apidog MCP for existing endpoint specifications
If endpoints don't exist yet, define them in Apidog first
Create shared types/models appropriate to the detected stack:
Web/TypeScript Projects (tsconfig.json exists):
src/types/ for request/response shapes, entity types, shared enums and constantsFlutter/Dart Projects (pubspec.yaml exists):
lib/core/models/ for entity types, DTOs, enums and constantsOther Projects:
This ensures backend and frontend code against the SAME contract.
If design artifacts exist (docs/designs/DES-<NNN>/), read the design README
to extract the Screen → Node ID Mapping:
docs/designs/DES-<NNN>/README.md — find the "Screen → Node ID Mapping" tabledocs/requirements/REQ-<NNN>.md section 8 "Design References" (if exists)batch_get(nodeIds: ["<id>"]) to read exact design specsIf the project-owner included the mapping in the spawn template, use that directly.
For each task, specify ALL of these fields:
Task ID: TASK-001
Title: [Clear one-line description]
Assignee: [backend-dev | web-dev | mobile-dev | test-worker | team-lead]
Domain: [Exact directory paths this task touches]
Design: [Pencil node ID, e.g., "F2P7Z" — for UI tasks only, or "N/A"]
Dependencies: [List of task IDs this is blocked by, or "none"]
Done when: [Specific, verifiable acceptance criteria]
Batch 1 — Independent tasks (Dependencies: none)
Batch 2 — Dependent tasks (blocked by Batch 1)
Batch 3 — Tests (depends on implementation)
Batch 4 — Review (depends on everything)
| # | Task | Assignee | Domain | Depends On |
|---|---|---|---|---|
| 1 | Add Comment model to Prisma schema | backend-dev | prisma/ | none |
| 2 | Create shared types: Comment, CreateCommentInput, CommentListResponse | team-lead | src/types/ | none |
| 3 | Implement GET/POST /api/items/[id]/comments | backend-dev | src/app/api/, src/services/ | 1, 2 |
| 4 | Create CommentCard, CommentList, CommentForm components | web-dev | src/components/ | 2 |
| 5 | Add comments section to item detail page | web-dev | src/app/items/ | 4 |
| 6 | Write API endpoint tests | test-worker | tests/ | 3 |
| 7 | Write component + E2E tests | test-worker | tests/ | 4, 5 |
| 8 | Review all branches | reviewer | (all, read-only) | 3, 5, 6, 7 |
Spawn order: Batch 1: tasks 1, 2 → Batch 2: tasks 3, 4, 5 → Batch 3: tasks 6, 7 → Batch 4: task 8