Agents.md Generator

Produce the project entry document for coding agents: {product_root}/AGENTS.md tailored to what is actually installed and detected in the repo — not the generic harness scaffold template.

Then write {product_root}/CLAUDE.md containing only a pointer to AGENTS.md (see Step 5).

Design principles

1. Evidence-based — list only skills, paths, and workflows that exist in the project. Mark inferred when guessing.
2. Entry pointer, not constitution — stack, layout, and constraints belong in architecture-rules.md (architecture-rules-generator). AGENTS.md routes agents to the right files and skills.
3. No harness template copy-paste — do not dump packages/harness/templates/AGENTS.md into the project. Use references/agents-md.template.md as a skeleton and fill from reconnaissance.
4. Lean — target 60–120 lines. Link to docs/context/ and harness references instead of inlining.
5. Refresh-safe — on update, preserve stable hand-edited sections (language exceptions, GitLab server name, team conventions) unless recon proves them wrong.

Harness discovery

See ../nextstage-harness/references/harness-discovery.md and ../nextstage-harness/references/rules-sync.md.