[!NOTE] After reading this SKILL.md, say: 🧭 I read shunk031-manage-agent-guidance.

Manage Agent Guidance

Keep each durable instruction in one source of truth and expose it through thin adapters.

Workflow

1. Read the applicable guidance before proposing a change.
2. Classify the requested 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 until higher-level instructions, managed sources, symlinks, imports, wrappers, and adapters confirm it.
3. Inspect the affected consumers and search for an existing owner. Build a consumer map when ownership or overlap is ambiguous; for a self-contained edit, record only the sources and readers that can be affected.
4. Edit one authoritative source. Put shared behavioral rules at user scope, repository procedures at repository scope, subtree rules at subtree scope, and reusable specialized procedures in an existing skill. Keep adapters thin and do not duplicate a rule merely because wording matches.
5. Before editing, state the evidence for scope, source of truth, existing ownership, and any unresolved consumer. Create a skill only when no existing owner fits and the procedure is substantial and reusable.
6. Review the final diff for scope mismatch, duplicate ownership, secrets, transient facts, and adapter drift. Run the actual gates of the affected repository; do not invent a hook, skip variable, or model gate.

Do not draft or edit until scope, source of truth, existing ownership, and affected consumers are confirmed. When evidence is unavailable, report the missing sources and propose the investigation instead of defaulting to the named file.

Persistence Quality