Detailed Analysis
A Reddit post in r/ClaudeAI surfaces a practical architecture question that is becoming increasingly common as Claude Code moves from single-script novelty to a tool orchestrating real production infrastructure. The poster runs three semi-independent automations built with Anthropic's CLI: an IAM lifecycle tool that deprovisions employees through JumpCloud, a Jira-mining tool that drafts runbooks from historical ticket patterns, and a reusable Confluence-to-Notion migration skill. Each lives in its own repository by deliberate choice, with the IAM automation isolated specifically because it touches production credentials and shouldn't share a blast radius with the still-experimental ticket miner. The question is no longer "does Claude Code work" but "how do you structure and govern multiple Claude Code projects once they start depending on each other and touch real systems" — a maturity signal for the tool and its user base.
The technical substance of the question is notable for what it reveals about emergent best practices around Claude Code. The poster describes a convention set that has apparently become somewhat standard among heavy users: a CLAUDE.md file per repo providing persistent context/instructions to the model, a HANDOFF.md tracking session state (mirrored to cloud storage for continuity between machines), and checksum manifests to keep multi-machine environments in sync. This is essentially an informal, community-invented layer of infrastructure-as-documentation built to compensate for the fact that Claude Code sessions are stateless between invocations and need external scaffolding to maintain continuity across a long-running, multi-repo project. None of this is prescribed by Anthropic; it's user-generated tooling convention filling a gap, similar to how early Docker or Kubernetes users invented folder and file conventions before official patterns solidified.
The deeper question — how to wire together independent AI-assisted automations once they need to call each other's outputs — points to a genuine and largely unsolved problem in the broader "agentic AI" ecosystem. The poster explicitly wants to avoid hand-rolling something that "already has a name," implicitly asking whether concepts like a shared skill registry, service-style API calls, or a package/library pattern map cleanly onto Claude Code's model of Skills and subagents. This echoes Anthropic's own recent moves: the introduction of "Skills" as portable, reusable capability packages in Claude and Claude Code, and MCP (Model Context Protocol) as a standardized way for Claude to reach out to external tools and data sources. The poster's doc-migration "skill" language suggests they're already leaning toward Anthropic's own abstraction, but the question of whether skills should be composed via direct invocation, a registry, or MCP-style tool-calling remains genuinely open, even among sophisticated users.
More broadly, this thread reflects a shift in how developers relate to Claude Code: from single-session pair-programming assistant to a persistent, semi-autonomous actor embedded in production workflows with real security stakes (IAM deprovisioning, sensitive content sanitization during migrations). That shift raises stakes around isolation, credential handling, and blast-radius containment that didn't matter when Claude Code was mostly used for one-off scripting or refactoring. As more organizations deploy multiple Claude Code-driven agents that need to interoperate — mirroring the general industry move toward multi-agent systems and agent orchestration frameworks — questions about repo topology, state handoff, and inter-agent communication protocols will increasingly determine whether "vibe coded" automation scales into something enterprises can actually trust to run unattended. The absence of authoritative Anthropic guidance on this specific pattern, and the community's need to invent its own conventions (CLAUDE.md, HANDOFF.md, checksum manifests), also signals an opportunity — and a gap — for Anthropic to formalize multi-repo, multi-agent orchestration guidance as Claude Code matures beyond individual developer tooling into something resembling infrastructure.
Read original article →