VSCode Icon

File

Edit

View

Go

Run

Terminal

Help

Javier Benitez Marin - Visual Studio Code

Explorer

portfolio
README.md

README.md

AGENTS.md

AGENTS.md

skills
README.md

README.md

hard
document-intelligence
multimodal-fraud-detection
rag-systems
multi-agent-orchestration
soft
communication
ownership-reliability
mentoring
adaptability
ideation-workflow
experience.md

experience.md

projects
blog
contact.config

contact.config

settings.json

settings.json

portfolio/skills/communication/SKILL.md
name:communication
description:Explain technical work clearly to whoever is in the room, and keep everyone aligned. Use when presenting to stakeholders, giving status, or translating between technical and non-technical people.

Communication

Treat communication as part of the engineering, not an afterthought. Most project failures are alignment failures, not code failures.

Approach

  • Match the room. An exec, a PM, and an engineer need the same truth told three different ways. Change the framing, not the facts.
  • Lead with the point. Say the decision or the ask first, then back it up. People are busy.
  • No surprises. Flag a risk early even if it turns out to be nothing, rather than staying quiet and being right too late.
  • Prepare the presentation. How a project is shown matters, especially to non-technical stakeholders. Put real effort into the story and the visuals; do not wing it.

Defaults

  • Alignment beats heroics. A team on the same page moves faster than a lone expert.
  • If the listener did not get it, that is the sender's problem, not theirs.

Stack

Stakeholder communication · Technical storytelling · Presentations & visuals