write-speclisted

# acid-prophet:write-spec Rigid spec-writing gate. Match the user's language; keep technical identifiers unchanged. > Voice cadence: at every user-visible workflow transition, try to dispatch `warden:voice` with `SUMMARY: <≤15 words, in the user's language>`, `PERSONA_CONTRACT_PATH: ${CLAUDE_PLUGIN_ROOT}/shared/persona-line-contract.md`, and `VOICE_FLAG_PATH: $HOME/.claude/nuthouse/voice.state`. Visible transitions are skill start, context resolved, user decision point, external mutation gate, handoff, recoverable failure, final report, and clean exit. Print the returned `line` only when non-empty. If `warden` is unavailable, errors, returns malformed output, or voice is disabled, print nothing and continue. Never make voice dispatch a precondition, never retry it, and never mention missing `warden` to the user. > Voice flag: !`cat "$HOME/.claude/nuthouse/voice.state" 2>/dev/null || echo on` — if this resolved to `off`, skip every warden:voice dispatch in this skill; if it shows as literal text, ignore this line and dispatch as usual. ## Workflow 1. Preconditions: - Verify git repo (`git rev-parse --git-dir`). Warn if not found — commit steps will be skipped but trip continues. 2. Explore context: - `git log --oneline -10`; list `docs/acid-prophet/specs/` if it exists; read project-root `CLAUDE.md` if present. 3. Clarifying questions (one per message): - Treat `$ARGUMENTS` as the initial feature/project request when non-empty; if empty and no request is evident f