manage-agent-guidance

# Manage Agent Guidance Keep each durable instruction in one source of truth and expose it through thin adapters. ## Workflow 1. Read all applicable guidance before proposing a change. 2. Classify each rule as user-level, repository-level, subtree-level, task-only, custom-agent, or skill guidance. Treat a filename named in the request as a hypothesis, not as the confirmed target. 3. Locate the source of truth by inspecting higher-level instructions, managed sources, symlinks, imports, wrappers, and adapters. 4. Search current guidance and skills for an existing owner. Strengthen that owner instead of adding a duplicate. 5. Before drafting or editing, report the evidence for scope, source of truth, and existing ownership. Name the inspected files, adapters, and matching owner rule; if none exists, state where you searched. 6. Put concise cross-task invariants in the applicable `AGENTS.md` and specialized repeatable procedures in an existing relevant skill. Create a skill only when no existing owner fits and the procedure is substantial and reusable. 7. Review the final diff for scope mismatch, duplication, secrets, transient facts, and adapter drift. Do not draft or edit until steps 2–5 are complete. When evidence is unavailable, report the missing sources and propose the investigation instead of defaulting to the named file. ## Instruction Migrations 1. Inventory every atomic rule in the source before deleting or compressing any section. 2. Record one destination for ev...