straymark-audit-promptlisted

# StrayMark Audit Prompt Skill Generate the unified audit prompt for a Charter and write it to the canonical filesystem location. The operator then opens auditor-side CLIs in the same repo and invokes `/straymark-audit-execute` — the audit prompt is read directly from disk by each auditor; the operator never copies/pastes. ## When to invoke Use this skill when the developer agreed to run an external audit at the Charter checkpoint (see `.straymark/00-governance/AGENT-RULES.md` § Audit checkpoint). The Charter should be in `in-progress` or `declared` status — auditing closed Charters is allowed but atypical (warn the operator and proceed only on confirmation). > **Audit a stable state.** Generate the prompt only when the state under audit is stable: the PR's CI is green, the working tree is clean, and commits are pushed. `--prepare` embeds the git diff at generation time, so if in-flight CI later forces a fix (or uncommitted work changes the tree), the prompt goes stale and the auditors review a revision that no longer exists. Sequence: **PR → CI green → `--prepare` → launch auditors.** The CLI warns (does not block) when the tree is dirty or has unpushed commits. ## Instructions ### 1. Resolve the Charter Argument: a Charter identifier (`CHARTER-04`, `04`, or full id with slug). ```bash straymark charter status <CHARTER-ID> ``` Verify the Charter exists and capture its `status`. If `status: closed`, surface a one-line warning to the operator and ask whether to proce