What problem does it solve? In a multi-repo agentic workflow, dev teams can silently import code across architectural lane boundaries, violating the separation rules defined in ADR-001. This Skill automates the audit so lane-creep is caught before a sprint accept instead of discovered later as tangled dependencies. ## Core Features & Use Cases - Lane-boundary linting: Runs lane-boundary-lint.sh against each repo's declared docs/architecture/lane-rules.txt and reports violations with file, line, lane, and the RACI rule broken. - Single-repo or fleet-wide audits: Check the current repo, a specified repo path, or fan out across every active project registered in .cto/projects.yaml with --all. - Actionable routing: Violations are routed to the owning dev team to either fix the import or open a CTO/ADR conversation to formally move the boundary. - Use Case: Before accepting a sprint, run the check across all active repos to confirm no team introduced a forbidden cross-lane dependency, then assign each violation to its owning team. ## Quick Start Ask the agent to run a lane check across all active project repos before the sprint accept.