Turn technical PRs, architecture changes, incident reports, cost optimizations, and security/compliance changes into boss-readable decision briefs.
🌐 中文 · English
exec-translate is an Agent Skill for translating engineering detail into executive decision language: impact, risk, cost, urgency, fallback, and whether leadership should approve, delay, reject, escalate, or ask for more information.
It is built for the awkward but common moment when a technical document is accurate, but still not useful for a decision maker. It is not a summarizer; it turns the source into a decision-ready readout with a recommended action, confidence level, red flags, and missing facts that would change the decision.
Technical updates often say:
Refactor checkout inventory validation to use cached availability snapshots.
Executives need:
Approve the rollout if oversell tolerance is acceptable. It should reduce checkout latency, but inventory may be stale for up to 45 seconds. Rollback is available through a feature flag.
exec-translate keeps the technical truth, removes unnecessary implementation detail, and refuses to invent missing metrics.
Input from examples/incident-report.md: login failed for some users from 10:04 to 10:21, rollback restored the error rate, root cause verification is still in progress, customer impact is unknown, and recurrence prevention has no owner.
exec-translate does not stop at "rollback completed." It surfaces the decision leadership needs to make:
| Item | Readout |
| --- | --- |
| Recommended action | Escalate |
| Urgency | Today |
| Confidence | Low |
| Decision red flags | Unknown impact, unverified root cause, no recurrence-prevention owner |See more output examples: Markdown brief · HTML brief · PPT outline.
- Translates PRs, code changes, architecture proposals, release notes, incident reports, cost optimizations, security/compliance changes, and postmortems.
- Produces decision briefs with business impact, risks, fallback, cost, benefit, and missing decision-critical information.
- Separates
Confirmed,Inferred, andUnknownfacts so the output stays auditable. - Supports CEO, CTO, CFO, product, customer success, and legal/compliance audience lenses.
- Adds decision verbs, confidence rules, and red flag detection so the brief can support an actual decision.
- Supports compact chat/email versions, leadership readiness reviews, polished standalone HTML briefs, and PPT-ready presentation structures.
- Includes HTML templates and presentation patterns for more polished executive-facing outputs.
- Does not generate PPTX itself; it can hand off a clean outline to
ppt-masterwhen you explicitly ask for an actual deck file. - Use it from natural language. No extra CLI, API key, or app server required.
exec-translate follows the open Agent Skills format and can run in skills-compatible AI agent runtimes.
Open your current agent, such as Codex, Claude Code, Cursor, OpenClaw, Gemini CLI, or another skills-compatible runtime, and say:
Install this skill: https://github.com/luanluan1/exec-translate
Chinese works too:
帮我安装这个 skill: https://github.com/luanluan1/exec-translate
Use the open skills installer:
npx skills add luanluan1/exec-translateThe installer detects the current agent runtime. If you need to target a runtime explicitly:
npx skills add luanluan1/exec-translate --skill exec-translate --agent codexOther agent names may include claude-code, cursor, or any agent supported by your installed skills CLI.
If your runtime does not support automatic Agent Skill installation, copy or paste the content of skills/exec-translate/SKILL.md into your agent context. The Skill is plain Markdown with YAML frontmatter.
Ask naturally:
Use exec-translate to translate this PR for my boss.
Turn this incident report into a management version.
Use exec-translate to turn examples/incident-report.md into an executive decision brief.
Use exec-translate and make a PPT outline for leadership.
You can also use Chinese trigger phrases such as:
把这个事故报告翻译成老板看得懂的版本。
这个架构变更怎么汇报给老板？
The default output is a boss-readable decision brief:
Default structure:
# Executive Decision Brief
> One-sentence conclusion: what happened, why it matters, and what leadership should do next.
## Decision Snapshot
## Facts and Uncertainty
## What Happened
## Why It Matters
## Risk and Fallback
## Decision Red Flags
## Cost / Benefit / Cost of Doing Nothing
## What Leadership Should Do
## Missing Decision-Critical InformationExample decision block:
## Decision Snapshot
| Item | Readout |
| --- | --- |
| Recommended action | Request more information |
| Urgency | This week |
| Confidence | Medium |
| Leadership involvement | Needs awareness now; decision only if SLA/customer impact is confirmed |
| Audience lens | Mixed leadership |
| Decision type | Request more information |
| Primary risk | The service has recovered, but recurrence prevention is not yet owned |
## Facts and Uncertainty
- Confirmed: Rollback completed and error rate returned to normal.
- Inferred: Customer impact likely existed during the 17-minute login failure window.
- Unknown: Affected user count, support tickets, SLA exposure, and recurrence owner.
## Decision Red Flags
- Recurrence prevention owner is not assigned.exec-translate can directly generate a standalone HTML executive brief:
Use exec-translate to turn this incident report into a single-page HTML brief.
exec-translate can directly generate a PPT-ready management outline:
Use exec-translate to turn this architecture change into a leadership PPT outline.
exec-translate can work with PPT generation, but it does not vendor a PPT engine.
If you explicitly ask for an actual PPT, PPTX, deck, or presentation file, a compatible agent can first use exec-translate to create the executive decision content and then hand the structured outline to ppt-master when that Skill is installed.
Use exec-translate to turn this incident report into a boss-readable PPTX.
If ppt-master is available, generate the deck.
skills/
exec-translate/
SKILL.md
agents/
openai.yaml
references/
decision-framework.md
html-templates.md
output-formats.md
presentation-patterns.md
ppt-handoff.md
examples.md
examples/
pr-change.md
incident-report.md
architecture-change.md
cost-optimization.md
security-compliance.md
incomplete-input.md
readiness-review.md
ppt-outline-request.md
html-brief-request.md
pptx-request.md
output/
incident-brief.md
incident-brief.html
ppt-outline.md
executive-brief-preview.svg
See examples/ for sample PR, incident, architecture-change, cost-optimization, security/compliance, readiness-review, incomplete-input, HTML, PPT-outline, and PPTX handoff requests.
Output previews:
- Translate technology into business consequences.
- Give a clear recommendation when the source supports one.
- Mark uncertainty instead of hiding it.
- Ask only for missing information that would change the decision.
- Do not invent ROI, losses, SLA impact, customer counts, root cause, owners, dates, or guarantees.
MIT