business-literacy

Translate business financial terms into engineering manager–ready language.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/imsus/cto --skill business-literacy-imsus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: business-literacy
Source: https://github.com/imsus/cto/tree/main/.agents/skills/business-literacy
Command: npx skills add https://github.com/imsus/cto --skill business-literacy-imsus

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Explains business financial terms and frameworks so engineering managers can confidently translate engineering work into business outcomes and stakeholder-ready reasoning.

Core Features & Use Cases

  • Plain-English definitions of key metrics like ARR, COGS, CAC, LTV, gross margin, burn rate, EBITDA, and AARRR.
  • Engineering-to-business translation formulas and guidance for connecting roadmap, reliability, staffing, and cost decisions to financial impact.
  • Three-layer credibility framework (product impact → business economics → industry/domain positioning) to help EMs build trust with leaders and P&L owners.
  • Use when decoding business-language discussions (e.g., EBITDA, burn rate, CAC/LTV) or making the case for platform/tech-debt work in business terms; avoid when the goal is specifically tying engineering productivity metrics (e.g., DORA, velocity) to business outcomes.

Quick Start

Use the business-literacy skill to translate the term "burn rate" from a leadership conversation into what it means for engineering priorities and how to discuss it with the P&L owner.

Frequently Asked Questions about business-literacy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I translate engineering work into business metrics like ARR and EBITDA for leadership discussions?

Business financial terms like CAC, LTV, gross margin, and burn rate are decoded into operational, plain-English definitions with why-it-matters context and engineering translation guidance. This helps engineering managers connect technical decisions to growth impact and discuss them confidently with P&L owners.

What is the best way to explain gross margin and COGS impact when making a case for tech debt resolution?

The best way to explain gross margin and COGS impact for tech debt is using an engineering-to-business translation framework that connects reliability and staffing decisions to financial outcomes. It provides example stakeholder wording and caveats about metric interpretation to ensure credible communication.

How does the AARRR framework map to engineering priorities and platform decisions?

The AARRR framework maps to engineering priorities by translating growth metrics into engineering manager-ready language. It provides operational definitions and engineering translation guidance, helping you connect platform, reliability, and tech-debt work to acquisition, activation, retention, referral, and revenue impact.

Can I use business financial translation to tie DORA metrics and engineering velocity to business outcomes?

No, you should not use this business financial translation approach for tying engineering productivity metrics like DORA or velocity to business outcomes. It is designed specifically for decoding financial terms and making the case for engineering work in business language, not for productivity metric correlation.

When do I need to decode burn rate and CAC for engineering planning meetings?

You need to decode burn rate and CAC when participating in business-language discussions or planning meetings where engineering priorities must align with financial constraints. This provides why-it-matters context and stakeholder-ready reasoning to support business-aligned communication with P&L owners.