Set up project

Scaffold and audit the per-repo configuration the skills assume:

• Rules file: AGENTS.md, which every harness reads. CLAUDE.md is either the single line @AGENTS.md or a symlink to AGENTS.md. Claude Code skips a project's AGENTS.md when a CLAUDE.md exists, and both of those forms give it the same text.
• Issue tracker: where issues live (GitHub by default; local markdown is also supported out of the box)
• Triage labels: the strings used for the five canonical triage roles
• Domain docs: where GLOSSARY.md and ADRs live, and the consumer rules for reading them
• Folder standard: the .gitignore lines of orchestrating/folder-standard.md
• Allow-only project permissions: the global rules are the machine's safety rails, and a project's own harness files only add convenience. The audit flags every project file that weakens a global rule.

You explore, present what you found, confirm with the user, then write. Running it again is the audit.

Steps

1. Check the machine

Run set-up-machine's verifier, python3 <set-up-machine skill>/scripts/verify.py, from the set-up-machine skill installed beside this one. A pass is exit code 0. When the exit code is not 0, run the set-up-machine skill first, then come back. Done when the verifier exits 0.