IMPLEMENTAUDIT
On this page
  1. The first path
  2. What to trust
  3. What to ignore at first
First-run support

For new users

Use this page when Quick Start feels too abrupt. It explains what to paste, what appears on disk, and how to tell whether the run finished honestly.

The first path

  1. Open Quick Start for the canonical first command.
  2. Install the skill in Claude Code or Codex if your host has not loaded it yet.
  3. Open the repo you want changed.
  4. Paste one concrete request such as /implementaudit fix the findings in AUDIT.md.
  5. Look for inspectable evidence: a run folder and STATE.md for phased work, or a final response that names the bound work record, cited artifacts, final audit ledger, and transcript markers for compact work.

What to trust

Trust the run only when evidence is inspectable. A good run shows AUDIT_COMPLETE before IMPLEMENTAUDIT_RUN_COMPLETE.
If it cannot close, it should leave AUDIT_HANDOFF or ANDON_HANDOFF with the blocker and next owner action.

Those markers do not authorize commit, push, tag, release, publication, provenance, host install, or sidecar setup. Each gate needs explicit owner approval.

What to ignore at first

You do not need to understand Lean vocabulary, sidecars, or release history for a first run.
Read the plain labels first: work record, run folder when phased, state file, phase checklist, before/after checks, failure log, and final audit.