technical-translator

Provide the file path to the technical document, such as an RFC or architecture doc. The Skill reads it, identifies core technical decisions and trade-offs, and produces a structured summary covering product impact, user impact, decisions, risks, and questions for engineering.

The Skill handles API specs, architecture documents, RFCs, and engineering proposals. Any markdown or text-based technical document at a given file path can be read and translated into product-focused language.

No. The Skill translates rather than simplifies, preserving nuance while making content actionable. It clearly separates what the PM must understand for decisions from nice-to-know context, and frames trade-offs in user, timeline, or cost terms.

The output is a markdown file saved as translated-[original-filename].md in the current working directory. It contains a TL;DR, product impact, user impact, key decisions, questions for engineering, risks, and an optional glossary.

The Skill never invents product implications unsupported by the source document and flags ambiguity instead of guessing. It does not reproduce code, only explains what code does and why it matters, so deep implementation review still requires the original document.