What problem does it solve? Teams managing Claude Code configuration across multiple repositories end up with scattered, hand-edited .claude/ directories and duplicated skills. This Skill bootstraps a single canonical monorepo (a "harness") that holds skills, MCP servers, sub-agents, and a knowledge vault, then projects everything into Claude Code via a generated bin/harness sync CLI. ## Core Features & Use Cases - Interview-first scaffolding: Collects the harness location, contemplated repositories, MCP servers, plugins, and vault preferences before writing any file, then generates the full topology (harness.config.yaml, bin/harness, bin/render_mcp.py, bin/render_plugins.py, mcp/servers.json, workspace/workspace.yaml, vault/). - Canonical-to-projection sync: Generates CLAUDE.md as a symlink to AGENTS.md, symlinks active skills and sub-agents into .claude/, and renders .mcp.json and .claude/settings.json from canonical sources. - Graphify knowledge graphs: Clones the contemplated repos into workspace/, builds per-repo graphify graphs, and merges them into a federated graphify-out/federated-graph.json for cross-repo architectural queries. - Use Case: A platform engineer asks to "create a harness" for a team with five product repos; the Skill interviews for the repo list, scaffolds the monorepo, clones the repos, runs harness sync and harness graph, and verifies the federated graph answers queries. ## Quick Start Ask the agent to create a new Claude Code harness at a chosen path, providing the list of repositories to contemplate, and let it interview you for MCP servers, plugins, and vault options before scaffolding.