tech-to-pm-translatorlisted

# Tech-to-PM Translator Converts technical developer documentation into structured, code-free knowledge base documents that PMs, designers, and other non-engineers can use to understand systems without reading code. ## Philosophy This is a **translation** skill, not a **summarization** skill. - **Summarization** loses detail. A PM reading a summary still can't answer questions. - **Translation** reframes the same information for a different audience. A PM reading a translated doc can understand what breaks, why, and who to talk to. The output preserves technical accuracy while stripping implementation detail and adding decision-support framing. ## When to Activate - User says "translate docs for PMs", "make this PM-friendly", "convert tech docs" - User says "create PM context from these docs", "non-engineer version" - User says "explain this system for PMs/designers", "create onboarding docs" - User has technical markdown files and wants them accessible to non-coders - After a team writes architecture docs and wants broader org understanding ## Input Required: - **Source path**: Directory or glob pattern containing technical docs (e.g., `.claude/ref/`, `docs/architecture/`, `**/*.md`) Optional: - **Output path**: Where to write the translated docs (default: alongside source or user-specified) - **Audience**: "pm" (default), "designer", "stakeholder", "new-hire" (adjusts framing depth) - **Project name**: For context-specific terminology and ownership mapping - **Exi