How I Became My Team’s Bottleneck
I delegated the work, but too many small decisions still came back to me. What changed when I stopped being my team’s default path through uncertainty.
ENGINEERING · PRODUCT · PRACTICAL AI · LEADERSHIP
From ambiguous problems to
solutions that work.
Notes on building products and systems under real-world constraints — engineering, AI, data, leadership, and the decisions behind them.
Evidence over claims
Selected work
Personal projects, each shown through the constraint, the decision, and the artifact it leaves behind.
Select a project
skills-manager
Rust TUI. See every agent skill and where it is exposed.
RustRatatui TUIHomebrewmacOS
- Context
- Agent skills quickly spread across tools, repositories, and local folders. It becomes hard to tell what each agent can actually use — and reusing a skill often means manually copying it into another agent-specific location.
- Decision
- Treat skills as managed sources and agent access as explicit exposure. Build one local inventory, import internal or external skill sources, and expose selected skills to Claude, Codex, or Copilot through managed symlinks.
- Outcome
- One terminal workflow to see what each agent can use, add a skill once, and expose or revoke it per agent without duplicating files.
skills-manager selected.
Engineering notes & architecture
Latest writing
The Engineering Manager's Depth Problem
You don’t need to know everything. You need to recover the context that matters, intervene at the right depth, and step back again.
About & Principles
About
buildsolution.net is a place where I share what I learn from building software, leading teams, and connecting technology with product.
I'm Jakub, an engineering manager working in one of Poland’s leading e-commerce companies