audit-impl

Implementation Audit Skill

Audit a completed implementation against its plan(s) before merge. Identifies gaps, missed requirements, scope creep, and unexpected changes. Produces a GO or NO GO verdict.

When to Use

• After implementation completes and tests pass, as the last step before merging
• In single-plan pipelines: audit the worktree against the plan
• In multi-group pipelines: audit the feature branch against all group plans via manifest
• Standalone: /autoskillit:audit-impl {plans_input} {branch_name} {base_branch}

Arguments

{plans_input} {branch_name} {base_branch} [conflict_report_paths]

• plans_input — one of:
  • A single plan .md file path
  • A comma-separated list of .md plan file paths (no spaces around commas)
  • A directory containing *_plan_*.md files
  • A manifest_*.json from /autoskillit:make-groups
• branch_name — commit SHA of the pre-implementation base ref (preferred from pipeline, stable after merge_worktree destroys named refs); a branch name is also accepted for standalone invocations. A live worktree path is accepted for legacy use (Step 0 extracts the branch name automatically).
• base_branch — branch to diff against (default: develop)
• conflict_report_paths (optional) — comma-separated list of absolute paths to conflict resolution reports produced by resolve-merge-conflicts. When provided and non-empty, cross-reference resolution decisions against plan intent in Step 2.5.

Critical Constraints

NEVER:

• Modify source files, plan files, or any other files — read-only audit only
• Run tests — this skill audits, it does not fix
• Create files outside {{AUTOSKILLIT_TEMP}}/audit-impl/
• Emit a GO verdict when any MISSING or CONFLICT finding exists
• Run subagents in the background (run_in_background: true is prohibited)

ALWAYS:

• Use Explore subagents for all file reads and diff retrieval
• Use model: "sonnet" when spawning all subagents via the Task tool
• Resolve all plan files before starting (abort early if any are missing)
• Write Dry-walkthrough verified = TRUE as the absolute first line of any remediation file
• On a NO GO verdict, after writing the remediation file, emit the absolute path as a structured output token as your final output. Resolve the relative temp/audit-impl/... save path to absolute by prepending the full CWD:

  verdict = NO GO
  remediation_path = /absolute/cwd/temp/audit-impl/{filename}.md
  

  On a GO verdict, emit only verdict = GO (no remediation_path token). The remediation_path token is MANDATORY on NO GO — the pipeline cannot proceed without it.