Craft
7 current practices.
StandardCraftCR-001Start with workflows, not agentsPrefer the simplest thing that works — a single call, then a fixed workflow of composable steps, and only a fully autonomous agent when flexibility genuinely demands it.
Reviewed Aug 2026CraftCR-002Plan before implementation, and review the planHave the agent produce a written plan or spec first, review that, then let it implement.Reviewed Aug 2026CraftCR-003Have a second agent review, in a fresh contextUse a separate agent session, unbiased by having written the code, to review it.
Reviewed Aug 2026CraftCR-004Run parallel agents in separate git worktreesGive each concurrent agent an isolated checkout so they never collide.Reviewed Aug 2026StandardCraftCR-005Standardise the layer beneath the tools, not the toolsBuild a shared internal platform — access layer, LLM routing, MCP servers, standards — rather than letting every engineer's agent be a private artifact.
Reviewed Aug 2026CraftCR-006Turn repeated workflows into commands, skills and pluginsAnything you prompt more than once a day should become a reusable command or skill checked into git.Reviewed Aug 2026WatchCraftCR-007Encode engineering standards as agent-retrievable rules, enforced in CIPut your standards into a governed, agent-readable corpus and have an AI reviewer check every merge request against them.One source · a little soon to recommend
Reviewed Aug 2026CraftCR-002Plan before implementation, and review the planHave the agent produce a written plan or spec first, review that, then let it implement.Reviewed Aug 2026CraftCR-003Have a second agent review, in a fresh contextUse a separate agent session, unbiased by having written the code, to review it.Reviewed Aug 2026CraftCR-004Run parallel agents in separate git worktreesGive each concurrent agent an isolated checkout so they never collide.Reviewed Aug 2026StandardCraftCR-005Standardise the layer beneath the tools, not the toolsBuild a shared internal platform — access layer, LLM routing, MCP servers, standards — rather than letting every engineer's agent be a private artifact.Reviewed Aug 2026CraftCR-006Turn repeated workflows into commands, skills and pluginsAnything you prompt more than once a day should become a reusable command or skill checked into git.Reviewed Aug 2026WatchCraftCR-007Encode engineering standards as agent-retrievable rules, enforced in CIPut your standards into a governed, agent-readable corpus and have an AI reviewer check every merge request against them.One source · a little soon to recommend