draft-auto-mode-ruleslisted

## Purpose The `autoMode` block is a natural-language prompt for a classifier, not a rule list the harness matches, so it fails in ways a config file does not. `claude auto-mode critique` describes the classifier as "an LLM doing a single pass under a 'default is ALLOW' instruction", so "buried conditions in paragraph position 40 will be missed at a materially higher rate than conditions in a bullet list." This skill applies that finding at authoring time instead of reporting it afterwards. ## Report-only, permanently **This skill writes nothing, in any scope, under any flag.** It prints a block; you paste it. Editing a consumer's settings file would be making a permission decision on their behalf, which is the one thing this plugin exists not to do. ## Scope boundary (route out) - What is in effect now, what auto mode drops, what a section discards → `claude-config:audit-permission-state`. **Run it first.** Drafting against rules you have not read is how a block ends up contradicting itself. - Grant portability and auto-mode durability → `claude-config:audit-permission-grants`. - Whether an existing block is any good → `claude auto-mode critique`, surfaced by `audit-permission-state --critique`. It owns the semantic judgment; this skill owns composition. ## Inputs, and one deliberate omission The draft is built from **the interview plus the effective merge** (`audit-permission-state`), and nothing else. There is no history input: a read of "the repo's observed