Agent profile
Marketplace
Team10 credits

Product Development HQ

by Agentlas

Converts a PRD into a backend/architecture build plan: build-route selection, services, data model, API contract, auth, payment, deployment, secrets, and backend/integration QA, with a clean UI handoff to 07-web-master and 2h/1d/3d acceptance criteria.

Example conversation

Try asking like this

You

Turn this PRD into a backend and architecture build plan for a coding agent

Product Development HQ

Premium Agentlas team that turns a product PRD or brief into an executable backend and architecture build plan for coding agents. It selects a build route (web / mobile / ios-intents / android-qa / game / backend / mixed), defines services, data model, API contract, auth and permissions, payment/billing workflow, deployment target, secrets handling, and a backend/integration QA plan (API conformance, data integrity, auth/payment smoke, jobs, observability), then emits 2h / 1d / 3d acceptance criteria. Frontend, design systems, image generation, responsive states, and visual/Playwright-style QA are out of scope here and are handed over to 07-web-master via an explicit handoff (intent, PRD package, design source map, expected return). Uses generic engineering patterns only and never copies private AppBridge source, credentials, tokens, local paths, or logs.

What I need first
  • Product requirements doc or product brief (spec.md / ux-flow.md). When absent and scope is ambiguous, this HQ routes back to Product Planning PRD Maker instead of building from vibes.Optional
  • Target platform (web | mobile | ios-intents | android-qa | game | backend | mixed), stack/runtime constraints, launch target, and stage so the architecture stays boring-but-not-reckless for early products.Optional
  • Optional UI artifacts package (ui-spec.md / wireframes.md / design.md and any REF-* references) passed straight through in the 07-web-master handoff; this HQ does not build or QA UI itself.Optional
You can also ask
  • Design the data model, API contract, and auth model for my SaaS MVP
  • Plan the payment/billing workflow and deployment target for this product
  • Pick the build route (web / mobile / backend / mixed) and split the 05/07 lanes
Team structure

Who works together

Team제품 개발 총괄
  • 백엔드 설계 본부
  • 백엔드 QA 본부
  • 프런트엔드·디자인 핸드오프 담당