writing-for-agentslisted

# Write useful agent instructions Make behavior explicit with the smallest sufficient document. Update the owning passage rather than accumulating corrective layers. A justified no-change result is valid; a template is a coverage check, not a quota of content. ## 1. Inspect the document and its authority 1. Identify the requested outcome, audience, file paths, scope, and existing owners. Read applicable instructions and surrounding documents; preserve unrelated work. 2. Inspect sources supporting facts, paths, commands, and conventions. Separate observed behavior, accepted policy, proposed policy, and unknowns. 3. Choose the relevant procedure: | Document | Procedure | | --- | --- | | Create or update project instructions or scoped rules | [Project instructions](references/project-instructions.md) | | Create or update a skill or its references | [Skill authoring](references/skill-authoring.md) | | Other agent-facing documentation | Apply the editorial rules below and preserve its owning format | 4. For a narrow correction, inspect its dependencies without turning it into a full setup or reorganization. Ask only about consequential gaps not discoverable locally. **Done:** destinations, authority, relevant facts, and missing decisions identified. ## 2. Select and structure the content For each new or existing instruction, ask: - What concrete mistake or ambiguity does it prevent? - Is it verified, current, and applicable at this scope? - Does it