So for anyone who's missed it, Claude Code has shaped up to be one of the biggest industry challengers to our engineering ways of working. You simply tell it what you want, and it does it - kinda.

Not only is it fast, it's pretty good... if you prompt well!

It's a fairly simple process too, you open up your Terminal app, run claude and very quickly you're in the wonderful land of TUI (Terminal User Interface, not to be mistaken for the travel agents).

Before long, Claude starts asking you for permission to edit files and run commands, which leaves you two options:

• You start curating a list of safe commands for Claude to run

• You quit and run claude --dangerously-skip-permissions, which is what most people I've met do.

There are a number of models which Anthropic publish, each has different training, reasoning and capabilities.

Now that's a lot of information, and which model to use is a good question.

When I'm working on smaller tasks what I usually do is flip Claude Code into /plan mode and use Opus to reason about my ask, and then once we've got a solid plan, flip over to Sonnet to execute the plan as I don't need as much reasoning.

Ultimately model choice comes down to the task you're doing, and a lot of people neglect the smaller models in favour of picking the biggest baddest model because it might be smarter.

Through the 2025 Festive Period, my Twitter X feed was taken up with posts about how to get the most out of Claude Code, whether it's BMAD Spec Driven Design, Ralph Wiggum, or a plethora of other techniques which pop up and very quickly drop off.

To support this, the team at Anthropic have built the ability to install plugins into Claude Code, so after a quick command such as /plugin install ralph-loop@claude-plugins-official you can get started using these powerful capabilities.

In the Ralph Wiggum example, there are a load of skills presented backed by shell commands to help get Claude in a task list completion loop.

You can also install Skills, which you can then execute using /skill-name. I find it easiest to think of skills as template prompts explaining to LLMs specifically how to do things.

One of my favourite Claude Code plugin types is Personas, in reality these are just skills, but they're used when creating Subagents / Team Members with specific skill sets.

It's not that Claude needs any extra knowledge here, but it's helpful to tell an LLM what job it's doing so it can rule out all that extra knowledge it's learned and doesn't need to know.

Occasionally Claude Code will decide to spin up a sub-agent to complete a task, this is an agent in its own right which Claude Code prompts, the benefit of which is that a Subagent runs within its own token context window keeping all that minutia of how to do a task was achieved out of your main context window.

The downside of Subagents is that they're lone wolves, this is where Teams come into play.

As the name suggests, Teams is where the Claude Code instance you're interacting with (the Team Lead) decides it needs to create a number of highly specialised Claude Code instances to complete a task.

I absolutely LOVE LOVE LOVE Teams, each agent is an expert at what they do and the Team Lead keeps them on-task. What I love the most however is their ability to communicate between themselves, and that both you the user, or the Team Lead can steer them at any time.

Now putting these features together we can start thinking about how we can model engineering team behaviours where you need multiple people ... in my innovation world, I need different Personas... To quote my colleague Paul "It takes a village".

By using Personas we can ensure that we're getting exactly the output we want from each individual member, by modelling an Agile Squad.

We can get high quality documentation in the form of Jira, and Solution Architecture. Supported by design artefacts for high quality.

Whilst in reality, I'm not going to run that prompt, that would simply burn a vast number of tokens and yield a moderate yet uninspiring blog... that wasn't the point of this prompt.

This was designed to share how we can communicate with an Agent Team Lead who can delegate tasks to autonomous Agents in somewhat of a familiar setting.

The last time I ran a prompt like this, I spent $500 or so on Claude and got something that needed a further day of fine tuning through Cursor to get a somewhat shippable MVP... which may sounds expensive, but if you compare that to the human cost to get that outcome, we start seeing the efficiencies.