engineering-lead

To generate technical specifications from a PRD, provide the product requirements as input and the skill produces engineering-ready deliverables like system design specs, data models, UX flows, and API contracts.

Creating API contracts and data models from product requirements involves processing domain inputs and gap analyses to output structured documentation files like api-contracts.md and data-model.md for engineering teams.

Yes, you can use this to produce architecture decision records and system design specs, as it applies structured documentation frameworks to translate product requirements into engineering-ready artifacts.

Ensuring traceability and alignment with non-functional requirements in system design is achieved by validating generated technical specifications and engineering artifacts against the original product requirements and constraints.

You do not strictly need a full PRD to generate UX flows and engineering documentation; you can also apply domain models and gap analyses as inputs to produce the specification set.

Using a dedicated framework for engineering documentation instead of manual system design accelerates architecture decisions by automatically generating structured, traceable deliverables from product requirements.