diff --git a/plugins/spec-anchored-development/skills/spec-anchored-development/references/golang.md b/plugins/spec-anchored-development/skills/spec-anchored-development/references/golang.md
index 6b4ee81..aa674c2 100644
--- a/plugins/spec-anchored-development/skills/spec-anchored-development/references/golang.md
+++ b/plugins/spec-anchored-development/skills/spec-anchored-development/references/golang.md
@@ -29,4 +29,4 @@ Use Go-native anchors and ownership boundaries.
 - spec -> `cmd/api/`, `internal/service/`, `internal/store/`
 - spec -> `pkg/client/` when there is a supported library surface
 - spec -> `migrations/`, `api/`, `test/`
-- code breadcrumb -> package comment, doc.go, or nearby design README
+- code back-link -> `// Spec:` comment per the [canonical back-link format](../SKILL.md#code-to-spec-back-link-format); for package-level ownership, place it in `doc.go`
diff --git a/plugins/spec-anchored-development/skills/spec-anchored-development/references/python.md b/plugins/spec-anchored-development/skills/spec-anchored-development/references/python.md
index 149b45b..6fbb5c3 100644
--- a/plugins/spec-anchored-development/skills/spec-anchored-development/references/python.md
+++ b/plugins/spec-anchored-development/skills/spec-anchored-development/references/python.md
@@ -28,4 +28,4 @@ Use Python-native anchors in specs instead of generic pseudocode.
 - spec -> `src/package/subsystem/`
 - spec -> `app/api/routes.py`
 - spec -> `package/services/`, `package/models/`, `tests/`
-- code breadcrumb -> package docstring, module header comment, or adjacent README if the repo already uses those patterns
+- code back-link -> `# Spec:` comment per the [canonical back-link format](../SKILL.md#code-to-spec-back-link-format); for package-level ownership, place it in `__init__.py`
diff --git a/plugins/spec-anchored-development/skills/spec-anchored-development/references/typescript.md b/plugins/spec-anchored-development/skills/spec-anchored-development/references/typescript.md
index 064f5f7..1dd8b9b 100644
--- a/plugins/spec-anchored-development/skills/spec-anchored-development/references/typescript.md
+++ b/plugins/spec-anchored-development/skills/spec-anchored-development/references/typescript.md
@@ -27,4 +27,4 @@ Use TypeScript-native anchors across backend, frontend, or full-stack repos.
 
 - spec -> `packages/*`, `apps/*`, `src/server/`, `src/lib/`, `src/routes/`
 - spec -> `openapi/`, `prisma/`, `migrations/`, `workers/`
-- code breadcrumb -> package README, file header, route module comment, or generated doc index already used by the repo
+- code back-link -> `// Spec:` comment per the [canonical back-link format](../SKILL.md#code-to-spec-back-link-format)