Topic archive
8 published stories filed under Claude Code.
The one use case where spawning a sub-agent always pays off. It is not parallelism. It is triage for your main context window.
We use the word parallelism when we talk about sub-agents. Most of the time we are not actually running in parallel. We are protecting the main context from heavy reading. That is the move.
Eli Wood
CEO, Black Flag Design
What Claude Code actually is, why it changes how work gets done, and where it fits in a business (and where it doesn't).
If your engineers keep mentioning Claude Code and the name alone does not tell you much, this is the plain-English explanation. What it is, why it is different from a chatbot, and where it actually fits.
Eli Wood
CEO, Black Flag Design
Starter paths from a solo developer trying it over lunch to a full company rollout with billing, auth, and audit in place.
Getting Claude Code into your team doesn't have to start with a committee. Here are the paths we've watched work, from a single dev with a free trial to a company-wide rollout with governance and audit, plus the first 30 days we'd actually run.
Eli Wood
CEO, Black Flag Design
Spawning a sub-agent looks like the obvious move for any multi-step task. Half the time it is the wrong one, and the signals are quieter than you think.
Sub-agents feel like leverage: one call, many workers, results in parallel. But most of the time we reach for one, the work was never parallel to begin with. Here is how to spot the trap before you fall in.
Eli Wood
CEO, Black Flag Design
Hooks, skills, CLAUDE.md, MCPs, sub-agents, plan mode. A practical decision framework for picking the piece of the harness that actually earns its keep on the task in front of you.
Claude Code gives you six different ways to shape a session. Most teams reach for the wrong one and wonder why the loop feels slow. Here's how we decide, task by task, which piece of the harness is worth the setup cost.
Eli Wood
CEO, Black Flag Design
Skills are the new unit of institutional knowledge. Here's how we package, share, and govern them across a studio that runs on Claude Code.
Claude Code skills are reusable slash-command workflows. Once they exist, the question is who gets to use them: you, your team, your org, or a specific client. Here's the sharing model we run at Black Flag and the disciplines that keep it from rotting.
Eli Wood
CEO, Black Flag Design
Claude Code isn't just an engineering tool. For designers, it's the fastest path we've found from a Figma frame to a production-quality build, if you know what to feed it.
Designers asking whether Claude Code is for them: the answer is yes, but not the way engineers use it. Here's what a year of design work in Claude Code taught us: the habits that translate polished intent into shipped UI without losing the craft.
Eli Wood
CEO, Black Flag Design
Claude Code leaves evidence — sessions, commits, PRs, review notes. Read it like a logbook and you'll find what devs actually need to know before they go deeper.
After a year of shipping with Claude Code across real client work, the signal isn't in any single session — it's in the trails. Here's what those trails told us about where Claude Code shines, where it drifts, and the habits devs should build before they lean in harder.
Eli Wood
CEO, Black Flag Design
