| name | build-product-service |
| description | Use when implementing or changing the Product service from its PRD: products, schemas, OpenAPI metadata, product flow templates, template-backed flows, invocations, waterfalls, reports, SMS, email, widgets, blobs, and operational telemetry. Read reference/PRD.md first; combine with conkeldurr, machamp, and apply-engineering-guidelines. |
Build Product Service
This skill is intentionally thin. Use it as a loader for reference/PRD.md, not as a requirements copy.
Required Reading
- Read
reference/PRD.md before planning or coding.
- Read
../apply-engineering-guidelines/SKILL.md for Golden Path constraints.
- Read Connect, Translate, Persist, Marketplace, and Deployer PRDs whenever Product work touches partner flow calls, translation, graph persistence, catalog validation, or marketplace deployment.
Use With Plugin Agents
- Use
conkeldurr first for platform product classification, existing-deployment checks, and build-vs-integrate decisions.
- Use
machamp for Product Flow Template compilation, Step Functions workflows, reports, waterfalls, retries, idempotency, and workflow verification.
- Use
regigigas only when Product must be packaged, released, subscribed, or deployed through the marketplace ecosystem.
Implementation Rules
- Treat the PRD as the single source of truth for routes, template contracts, product-flow contracts, data contracts, resource shapes, IAM scopes, env vars, error tags, workflows, and verification.
- Do not implement from this
SKILL.md alone.
- For an existing Product deployment, integrate through the PRD's public API, webhook, widget, report, SMS, email, and invocation contracts instead of provisioning a duplicate service.
- If any old skill or rule file conflicts with the PRD, the PRD wins; update stale guidance instead of layering compatibility shims.
Expected Output
Return the product fit, existing-vs-new deployment verdict, PRD sections used, files/stacks/contracts to change, companion agents/skills loaded, and the PRD verification path.
