Init agent docs

Produce documentation a future agent can act on. Two things make it worthless: placeholders, which look authoritative and say nothing, and restated discoverables — stack, commands, and directory layout that any agent finds in thirty seconds by reading the package manifest and listing the tree. Restated discoverables cost context on every turn, and they rot the moment the repo moves. AGENTS.md carries only what exploration cannot reach: intent, enforced convention, external constraint, and the specific traps of this repo.

Phase 1 — Survey

Read the repository before writing a word about it — not to transcribe it, but to know what to leave out and what to ask.

• Discoverables — stack, package manifests, task-runner scripts, CI workflows, directory layout. Learn them so you can recognise and exclude them, and so your questions are informed.
• Contradictions — where a documented rule and the actual code disagree. Each one is an interview question: which is true?
• Existing prose — README, CONTRIBUTING, any current AGENTS.md, CLAUDE.md, or docs/. Note what is authoritative and what has rotted.
• Collisions — every file this skill would create that already exists. Note existing directories separately; they are not collisions.

Done when you can describe the repo's shape and build surface in one paragraph without writing any of it into a document, and can list every contradiction and every colliding file.

Phase 2 — Interview

Ask only what the repository cannot tell you, and keep asking until nothing is left open. Surface one question at a time, highest impact first, using each answer to shape the next. Do not stop after the first answer, and do not settle for the questions listed below if the survey raised others.