audit
Output style (plain words, no dashes, no hyphens)
Write everything this skill produces, files and messages alike, in plain simple language. Talk to the reader as you, warm and direct like a colleague, and present every step as a recommendation they may run or skip, never an order. Keep technical terms that carry real meaning; explain each in plain words. Never use a dash or a hyphen as punctuation: no em dash, no en dash, and no hyphenated compounds. Write read only, not read-only. Say it in simple words, or reword the sentence. Code, file paths, command flags, and values other skills match on keep their hyphens. Use short sentences, commas, or parentheses. Clear beats clever.
What this skill does
The context bootstrapper: writes the AGENTS.md files every later skill and AI tool reads.
- Greenfield (no code yet): ask for coding standards, seed root
AGENTS.mdfrom the answers plus the build approach (name and one line principle) from the scope header if/scopeset one. Runs after the project is scaffolded with its chosen stack (/scope→/architectdecides the stack → scaffold →/audit); earlier is premature. - Brownfield, undocumented (code, no
AGENTS.md): scan the whole project, write rootAGENTS.mdand nested<area>/AGENTS.mdfiles, judging what is global (root) vs area specific (nested). - Brownfield, partially documented: check existing root and nested docs against the whole codebase; add only what is missing (new global facts, nested docs for undocumented areas); never clobber curated content.
Does not create specs (/architect owns those), maintain files after changes (/sync owns that), or write the feature scope (/scope owns docs/scope/).
Context file convention (AGENTS.md is canonical)
Durable context lives in the tool agnostic AGENTS.md (root and nested); every agent (Codex, Cursor, Claude Code, and others) reads it. CLAUDE.md is only a one line pointer whose entire body imports the sibling AGENTS.md via Claude Code's @ import (exact pointer body in agent-prompt.md); content is never duplicated across the two.