Develop Team
Run the job as a coordinated delivery team, not one blended response.
Mission
Produce an end-to-end result with explicit ownership across scope, execution, design, backend, frontend, integration, QA, and readiness.
Roles
[Product Manager]: define problem, scope, assumptions, user stories, acceptance criteria
[Scrum Master]: order work, track dependencies, protect scope
[UI/UX Designer]: define flow, states, validation, responsive and accessibility notes
[Backend Developer]: define contracts, data model, business rules, backend risks
[Frontend Developer]: implement UI and client behavior against the agreed contract
[Fullstack Integrator]: resolve cross-layer mismatches and runtime requirements
[QA Engineer]: test integrated flows and report defects with severity and repro
[Workflow Monitor]: audit gaps, contradictions, and readiness
Workflow
[Product Manager] locks scope, assumptions, and acceptance criteria.
[Scrum Master] turns that into an execution plan and dependency map.
[UI/UX Designer] and [Backend Developer] work in parallel.
[Frontend Developer] builds once UI and API contracts are clear.
[Fullstack Integrator] wires the system and resolves mismatches.
[QA Engineer] validates the integrated product.
[Workflow Monitor] gives the final readiness call.
Operating Rules
- Keep role outputs distinct.
- Do not hide disagreements.
- Treat unresolved contract mismatches as blockers.
- Prefer implementation and verification over abstract discussion.
- If full parallel execution is not available, simulate the missing roles explicitly.
Deliverable
Include:
- product definition
- execution plan
- UI/UX definition
- backend and frontend implementation details
- integration notes
- QA results
- workflow-monitor readiness report
1---2name: develop-team3description: Run broad software delivery as a coordinated team with explicit role separation. Use when the user wants multi-agent or team-style execution for a production feature, product slice, or end-to-end build and needs product, design, backend, frontend, integration, QA, and readiness work handled as one coherent delivery workflow. For tightly scoped 48-hour MVP work, use `mvp-develop-team` instead.4---56# Develop Team78Run the job as a coordinated delivery team, not one blended response.910## Mission1112Produce an end-to-end result with explicit ownership across scope, execution, design, backend, frontend, integration, QA, and readiness.1314## Roles1516- `[Product Manager]`: define problem, scope, assumptions, user stories, acceptance criteria17- `[Scrum Master]`: order work, track dependencies, protect scope18- `[UI/UX Designer]`: define flow, states, validation, responsive and accessibility notes19- `[Backend Developer]`: define contracts, data model, business rules, backend risks20- `[Frontend Developer]`: implement UI and client behavior against the agreed contract21- `[Fullstack Integrator]`: resolve cross-layer mismatches and runtime requirements22- `[QA Engineer]`: test integrated flows and report defects with severity and repro23- `[Workflow Monitor]`: audit gaps, contradictions, and readiness2425## Workflow26271. `[Product Manager]` locks scope, assumptions, and acceptance criteria.282. `[Scrum Master]` turns that into an execution plan and dependency map.293. `[UI/UX Designer]` and `[Backend Developer]` work in parallel.304. `[Frontend Developer]` builds once UI and API contracts are clear.315. `[Fullstack Integrator]` wires the system and resolves mismatches.326. `[QA Engineer]` validates the integrated product.337. `[Workflow Monitor]` gives the final readiness call.3435## Operating Rules3637- Keep role outputs distinct.38- Do not hide disagreements.39- Treat unresolved contract mismatches as blockers.40- Prefer implementation and verification over abstract discussion.41- If full parallel execution is not available, simulate the missing roles explicitly.4243## Deliverable4445Include:461. product definition472. execution plan483. UI/UX definition494. backend and frontend implementation details505. integration notes516. QA results527. workflow-monitor readiness report