ie-showcase

Post Image

The Software Still Has to Be Right: Review Is No Longer Enough

Here is the set of safety nets every team now needs, whatever its size.A team I know handed story grooming to an agent. They gave it a skill: a reusable set of instructions that taught the agent how the team writes user stories. It worked. Stories appeared faster than anyone could write them by hand.The team reviewed them and waved them through. The product owner did not. The stories were too long. They used engineering phrasing instead of the business...

Read

The messy truth about restructuring engineering docs with an AI teammate

on restructuring engineering documentation with an AI teammate. 1.        The messy truth about restructuring engineering docs with an AI teammate - 2.        Stitching five documentation frameworks into one coherent engineering wiki - [coming soon] 3.        Your Confluence should be a derived read model over your repo - [coming soon] 4.        Codifying your reorg: playbooks as the shared interface for humans and AI teammates - [coming soon] We work...

Read
Post Image

Structuring Claude Code for Multi-Repo Workspaces

Claude Code understands one repo at a time. Most teams have thirty.Microservices, shared libraries, infrastructure-as-code, frontend apps, data pipelines, all in separate git repos. Start Claude Code in one and ask about another, and it has no context. It doesn’t know the workspace exists.Here’s how I’ve been setting this up to work across repositories.When you start Claude Code in orders/order-service, it has no idea that orders/orders-ui exists next door, or that shared libraries live in shared/, or that the data...

Read