bluecraft/skills/bluecraft-agentic-docs/SKILL.md

---
name: bluecraft-agentic-docs
description: Use when creating, updating, splitting, merging, reviewing, auditing, or deleting the AGENTS.md at the root of the current Git working tree, or Markdown files inside any agent-docs/ directory
---

# Agentic Docs

## 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/`.

Treat covered documents as instruction documents. If one applies in scope, it must be followed, not treated as optional background reading.

## When To Use

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
- 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.

## Core Rules

- Each covered document should own one clear topic.
- Titles and filenames should state purpose directly.
- The opening section should explain what the document governs, when it applies, and that it must be followed in scope.
- Rules should be actionable, not slogan-like.
- Prefer standard Markdown headings and lists over wrapper tags for structure.
- Write for maintainers. State actions, constraints, and decision criteria directly.
- 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.
- 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 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.
- 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.
- 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

1. Identify the change type.

Choose the smallest accurate category:

- root routing change
- repository-wide constraint change
- child instruction document change
- documentation-tree refactor

2. Identify the child document type.

Use the smallest fitting type:

- rule doc: instructions, constraints, decision rules, policy, or workflow guidance
- inventory doc: maintained list, registry, media plan, page-by-page backlog, or cleanup queue
- hybrid doc: only when one short inventory is inseparable from the governing rules; otherwise split it

If a document spends most of its space enumerating items to maintain, do not force it into the rule-doc shape.

3. Decide rule placement.

Use this placement standard:

- Root `AGENTS.md`: routing entrypoint 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.

- 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.

See `references/routing-patterns.md` for routing patterns and anti-patterns.

5. Remove stale structure.

- Delete obsolete files, references, and filenames in the same change.
- If a split removes the need for an intermediate layer, remove that layer.
- If a new file is added, ensure it is reachable from the root entrypoint.

6. Apply the standard document shape.

- For a root file update, use `references/root-agents-template.md`.
- For a rule or policy child doc, use `references/rule-doc-template.md`.
- For an inventory or registry child doc, use `references/inventory-doc-template.md`.
- Use `references/child-doc-template.md` only as the compatibility entrypoint when you need help choosing between child templates.
- 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.

7. Verify.

- Check that the root `AGENTS.md` still acts as the primary entrypoint.
- Check that every active child doc is reachable from the root through explicit references.
- Check that no rule is duplicated across multiple active files without a clear reason.
- Check that rule docs and inventory docs are not mixed together without a clear reason.
- Run the validation command actually used by the repository if the change affects rendered documentation or project checks.

Use `references/refactor-checklist.md` as the final pass.

## Templates And References

- Root file template: `references/root-agents-template.md`
- 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`
- Refactor checklist: `references/refactor-checklist.md`

Read only the reference files needed for the current task.

## Completion Checklist

- 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 every active `agent-docs/` file reachable from the root through explicit references?
- Are obsolete paths, filenames, and documents removed?
- Were obsolete index layers removed?
- Does each rule live in one authoritative place?
- Is the default path basis still the root of the current Git working tree unless an instruction explicitly overrides it?
- Are repository-wide rules still in the root file?
- Are topic-specific rules still in child files?
- Are project-specific rules still kept in project-specific documents rather than the general rules layer?
- Was the relevant repository validation command run if needed?