What problem does it solve? When a feature spans multiple repositories, teams often duplicate spec content across repos or lose track of which repo owns the authoritative spec. This Skill creates a lightweight pointer (spec-link.md plus a minimal spec.json) in the repo that does NOT own the spec, so multi-repo work stays traceable without copying requirements, design, or tasks content. ## Core Features & Use Cases - Satellite links: In a light child repo, create a parent: pointer with source-of-truth references derived from the parent spec's actual artifacts. - Peer links: In a heavy multi-repo split, create a peers: + contract cross-reference alongside the repo's own full spec. - Safety guarantees: Enforces branch-parity rules, blocks slug collisions with existing real specs, refreshes idempotently, and never writes into the other repository. - Use Case: A notification feature is specified in your backend repo but requires changes in the mobile app repo. Run this Skill in the mobile repo to create a spec-link.md pointing at the backend spec, so status tooling and reviewers can trace ownership. ## Quick Start Ask the agent to run the kiro-spec-link skill with --from pointing to the parent repo path and --spec set to the owning spec's category/date-slug to create a satellite link in this repository.
