docs(bluecraft-agentic-docs): refine documentation structure terminology and patterns

Update skill definition and templates to use "references" instead of "routing"
throughout, clarify the root AGENTS.md as the entry document for agent-docs, and
add explicit linking patterns guidance. Improve template wording to emphasize
directional, explicit references and minimal reference depth.

- Rename and expand linking patterns reference
- Update SKILL.md trigger conditions and core rules
- Refine child doc template compatibility note
- Update refactor checklist to focus on reference depth
- Simplify root AGENTS.md template structure

skills/bluecraft-agentic-docs/SKILL.md

@@ -7,7 +7,7 @@ description: Use when creating, updating, splitting, merging, reviewing, auditin
 
 ## Overview
 
-Use this skill to maintain agent-facing documentation trees centered on the `AGENTS.md` at the root of the current Git working tree and child instruction documents in `agent-docs/`.
+Use this skill to maintain agent-facing documentation trees centered on the `AGENTS.md` at the root of the current Git working tree and the applicable `agent-docs/` documents.
 
 Treat covered documents as instruction documents. If one applies in scope, it must be followed, not treated as optional background reading.
 
@@ -17,7 +17,7 @@ Use this skill when a task involves any of the following:
 
 - creating or editing the `AGENTS.md` at the root of the current Git working tree
 - creating, editing, splitting, merging, or deleting Markdown files inside any `agent-docs/` directory
-- changing routing between `AGENTS.md` and `agent-docs/` files
+- changing explicit references between `AGENTS.md` and `agent-docs/` files
 - auditing whether an agentic documentation tree is coherent, minimal, and fully connected
 
 Do not use this skill for end-user documentation, product manuals, README content that is not part of the agentic documentation tree, or project-specific business rules that do not govern agent-facing docs.
@@ -33,19 +33,19 @@ Do not use this skill for end-user documentation, product manuals, README conten
 - When referencing repository files from `AGENTS.md` or `agent-docs/`, prefer plain repository-relative paths in backticks such as `agent-docs/example.md`, not Markdown links.
 - Do not embed machine-local absolute filesystem paths such as `/home/...`.
 - Do not mix general agentic-documentation rules with project-specific business rules, product instructions, media planning, or end-user documentation guidance in the same general-purpose file.
-- Treat the `AGENTS.md` at the root of the current Git working tree as the primary routing entrypoint.
+- Treat the `AGENTS.md` at the root of the current Git working tree as the root entry document for the repository's `agent-docs`.
 - Keep common, repository-wide constraints in that root `AGENTS.md`.
 - In monorepos, keep common constraints in the root `AGENTS.md` and place subproject-specific constraints in the relevant `agent-docs/` directory near that subproject.
 - Put project-specific or topic-specific constraints in the relevant child documents under `agent-docs/`.
-- The root `AGENTS.md` should reference only the instruction documents that are actually needed as next-step routing targets.
+- The root `AGENTS.md` should reference only the `agent-docs` documents that are actually required for the next editing decision.
 - The combined set of the root `AGENTS.md` and active `agent-docs/` files should form a connected documentation tree.
 - Each active instruction document must be reachable through explicit references from the root entrypoint.
 - Do not leave orphan instruction documents.
 - Keep one authoritative home for each rule; link instead of duplicating.
-- When a file, path, or rule is obsolete, remove or update it in the same change instead of leaving stale routing behind.
+- When a file, path, or rule is obsolete, remove or update it in the same change instead of leaving stale references behind.
 - Prefer stable, semantic filenames.
 - Unless a specific instruction explicitly defines another base path, treat every path mentioned in the conversation or in agentic documentation as relative to the root of the current Git working tree, not relative to the current file.
-- Make routing directional and explicit: a parent document should point to the child documents that refine it.
+- Keep references directional and explicit: a parent document should point to the child documents that refine it.
 - Match the child document shape to the document's job. Do not force inventory or registry documents into the same structure as rule or policy documents.
 
 ## Workflow
@@ -54,7 +54,7 @@ Do not use this skill for end-user documentation, product manuals, README conten
 
 Choose the smallest accurate category:
 
-- root routing change
+- root entry or cross-reference change
 - repository-wide constraint change
 - child instruction document change
 - documentation-tree refactor
@@ -73,19 +73,19 @@ If a document spends most of its space enumerating items to maintain, do not for
 
 Use this placement standard:
 
-- Root `AGENTS.md`: routing entrypoint and repository-wide constraints
+- Root `AGENTS.md`: root entry document and repository-wide constraints
 - `agent-docs/` child docs: scoped instructions for a topic, project area, or workflow
 
 If a rule only matters within one child topic, do not keep it in the root file.
 
-4. Update routing explicitly.
+4. Update explicit references.
 
 - Add or adjust references from the root file to the necessary child files.
-- If a child file introduces narrower subtopics, route to them explicitly.
-- Avoid extra routing layers unless they materially reduce ambiguity.
-- When moving project-specific constraints out of the root `AGENTS.md`, replace them with an explicit route to the new child document instead of leaving the route implicit.
+- If a child file introduces narrower subtopics, point to them explicitly.
+- Avoid extra reference layers unless they materially reduce ambiguity.
+- When moving project-specific constraints out of the root `AGENTS.md`, replace them with an explicit reference to the new child document instead of leaving the reference implicit.
 
-See `references/routing-patterns.md` for routing patterns and anti-patterns.
+See `references/agent-docs-linking-patterns.md` for reference patterns and anti-patterns.
 
 5. Remove stale structure.
 
@@ -102,7 +102,7 @@ See `references/routing-patterns.md` for routing patterns and anti-patterns.
 - Use standard Markdown headings and lists unless a narrower instruction requires another structure.
 - Treat inventory entry fields as a recommended starter shape, not a fixed schema. Keep only the fields that materially help maintainers scan and update the inventory.
 
-Adapt the wording to the repository, but preserve the routing and scope model.
+Adapt the wording to the repository, but preserve the explicit-reference and scope model.
 
 7. Verify.
 
@@ -120,7 +120,7 @@ Use `references/refactor-checklist.md` as the final pass.
 - Rule child template: `references/rule-doc-template.md`
 - Inventory child template: `references/inventory-doc-template.md`
 - Child template chooser: `references/child-doc-template.md`
-- Routing patterns: `references/routing-patterns.md`
+- Linking patterns: `references/agent-docs-linking-patterns.md`
 - Refactor checklist: `references/refactor-checklist.md`
 
 Read only the reference files needed for the current task.
@@ -130,7 +130,7 @@ Read only the reference files needed for the current task.
 - Does each covered document own one clear topic?
 - Does the filename clearly express the document's purpose?
 - Does the opening explain the document's purpose, trigger, and in-scope follow requirement?
-- Is the `AGENTS.md` at the root of the current Git working tree still the primary routing entrypoint?
+- Is the `AGENTS.md` at the root of the current Git working tree still the root entry document?
 - Is every active `agent-docs/` file reachable from the root through explicit references?
 - Are obsolete paths, filenames, and documents removed?
 - Were obsolete index layers removed?