Always consider agents.md and readme files

[max-tet]

When planning issues, always read all relevant agents.md file and the readme first. When implementing, do the same and update those files as needed.

[ClaydeCode]

Preliminary Plan

Overview

The prompts already mention agents.md in passing, but the issue asks for stronger, more explicit instructions to:

1. Always read agents.md and the README before planning or implementing
2. Update those files as needed after implementation

The fix is purely in the Jinja2 prompt templates:

• preliminary_plan.j2 — add explicit instruction to read README and agents.md first
• thorough_plan.j2 — same
• implement.j2 — add instruction to read README/agents.md first, and update them as needed after implementation
• address_review.j2 — add instruction to read agents.md and README before addressing review comments, and update them if review changes affect documented behavior
• update_plan.j2 — minor: mention agents.md awareness

The filename is specifically agents.md (following the Anthropic/OpenAI convention). No Python code changes needed — this is purely prompt engineering.

---

This looks like a small issue. React with 👍 to approve this preliminary plan and proceed directly to implementation.

[max-tet]

• During reviews, the files are also relevant and should be considered.
• It is the convention to use agents.md so that should be used.

[ClaydeCode]

Plan updated. Both questions are now answered. @max-tet confirmed that address_review.j2 should also be updated (agents.md and README are relevant during reviews), and that the convention is the specific filename agents.md (not a glob pattern). The plan is updated to reflect these clarifications — address_review.j2 is now explicitly included in the list of files to modify.

[ClaydeCode]

Implementation complete — PR opened: #63