Split product requirements into traceable technical requirements, API needs, data model changes, and rollout constraints. Classifies each product statement, derives numbered technical requirements with acceptance checks, specifies API changes by resource, operation, compatibility class, and error behavior, plans data changes with an expand-and-contract migration path, records rollout ordering, flags, and rollback limits, and keeps a requirement-to-work traceability matrix with open questions. Use when someone asks to turn a PRD, user stories, or a feature brief into technical requirements, what API or schema changes a feature needs, or what constrains its rollout. Do not use for sizing the result (use project-estimator), writing Jira epics and stories from it (use jira-epic-writer), or choosing the system architecture (use technical-architecture).