Auditor Selection
Evaluate and select audit firms for "$ARGUMENTS" based on industry expertise, regulation experience, cost, and timeline to find the best fit for the organization's certification goals.
Arguments. $ARGUMENTS may contain the project name and optional flags. Take the first token as <project> and treat --skip-checks as a flag; never include flags in file paths. All paths below use <project>. If --skip-checks is present, skip the prerequisite check and, before writing any artifact, append one line to .singularskills/log.jsonl: {"ts":"<ISO timestamp>","skill":"compliance-auditor-selection","workflow":"compliance","phase":3,"project":"<project>","event":"skipped","artifact":"03-certify.md","note":"<reason or \"none given\">"}.
Prerequisites
Part of a workflow. This skill is phase 3 (Certify) of the GRC Lifecycle workflow (compliance); cross-domain workflows run it too. First check .singularskills/log.jsonl for an open run for this project: a run-started line with "project":"<project>" and no later run-finished line for the same workflow and project. If one exists, the conductor is running you: continue here. Otherwise, if the user asked to start, run, continue or resume a process or workflow rather than this one step, do not continue here: invoke the workflow skill with the workflow the user asked for, or compliance when they named none, followed by <project>; it runs this phase in order, asks before it writes and records the run. Otherwise continue here: a later phase runs on its own, behind its gate.
Run this skill's gate before writing: sh <this skill's folder>/scripts/gate.sh <project> <project root>, where <project root> is the folder that contains .singularskills/ (use . when you are already there). If it exits non-zero, stop and tell the user what it printed, unless --skip-checks was given (see Arguments). On a refusal, before you stop, append this line to .singularskills/log.jsonl (create the folder and file if missing): {"ts":"<ISO timestamp>","skill":"compliance-auditor-selection","workflow":"compliance","phase":3,"project":"<project>","event":"refused","artifact":"03-certify.md","note":"<what the gate printed>"}. Once the gate has passed, or under --skip-checks once you have appended the skipped line, append this line before you start work: {"ts":"<ISO timestamp>","skill":"compliance-auditor-selection","workflow":"compliance","phase":3,"project":"<project>","event":"started","artifact":"03-certify.md","note":""}.
Read .singularskills/compliance/<project>/00-scope.md. If this file does not exist, tell the user:
Phase 0 (Scope) has not been completed for "". Run
/compliance-regulatory-landscape <project>first, or use--skip-checksto bypass.
Process
Read context files:
- Read
references/grc-lifecycle-guide.mdfor GRC methodology reference - Read
.singularskills/compliance/<project>/00-scope.mdfor scope and applicable regulations - Read
.singularskills/compliance/<project>/03-certify.mdfor audit readiness status
- Read
Define selection criteria:
- Industry expertise — experience with organization's sector
- Regulation experience — certifications the firm can audit (SOC 2, ISO 27001, HIPAA, etc.)
- Geographic coverage — can they audit all relevant locations?
- Team size and availability — can they staff the engagement in the desired window?
- Cost — engagement fees, travel costs, additional charges
- Timeline — availability for desired audit window
- References — client references in similar industry/size
- Combined audit capability — can they audit multiple standards simultaneously?
Create shortlist:
- Identify 3-5 candidate audit firms
- Research firm reputation, specializations, and recent engagements
- Consider Big 4, mid-tier, and boutique firms based on organization size and needs
- Check for conflicts of interest
Prepare RFP:
- Define scope — regulations, locations, systems in scope
- Define timeline — desired audit window, report delivery date
- Define deliverables — audit report, management letter, certificate
- Request pricing structure — fixed fee vs. hourly, payment terms
- Request team qualifications — lead auditor experience, certifications held
- Request references — 2-3 comparable clients
Evaluation framework:
- Score each firm against selection criteria (weighted scoring)
- Evaluate RFP responses for completeness and quality
- Check references — ask about responsiveness, thoroughness, communication
- Negotiate terms — scope, timeline, pricing, re-audit clauses
- Consider combined audits (SOC 2 + ISO 27001 with same firm for efficiency and cost savings)
Write the artifact — append to
.singularskills/compliance/<project>/03-certify.mdunder a## Auditor Selectionsection. Create the file with a# Certify — <project>heading if it does not exist; if a## Auditor Selectionsection already exists, replace only that section. The section contains:- Selection Criteria — weighted criteria with scoring methodology
- Candidate Shortlist — firms under consideration with profiles
- RFP Template — prepared RFP for distribution
- Evaluation Matrix — scoring framework for comparing responses
- Combined Audit Opportunities — multi-standard audit possibilities
- Recommended Next Steps — timeline for RFP distribution, evaluation, and selection
Output
The auditor selection plan appended to .singularskills/compliance/<project>/03-certify.md. Present a summary to the user highlighting:
- Selection criteria and weights
- Recommended number of firms to evaluate
- Combined audit opportunities identified
- Suggested timeline for selection process
Record the run. After you have written your section, append this line to .singularskills/log.jsonl (the started line of Prerequisites, with "event":"finished"): {"ts":"<ISO timestamp>","skill":"compliance-auditor-selection","workflow":"compliance","phase":3,"project":"<project>","event":"finished","artifact":"03-certify.md","note":""}.
This artifact is shared by every skill of phase 3 (Certify). The frontmatter is written once, by whoever creates the file: if you create it, open it with the block below (skill is the phase title, started the time of that first write; gate is passed when the gate ran clean and skipped under --skip-checks); if it already exists, leave the block alone except to update finished and to set gate to the worst value among the sections (skipped over passed).
---
skill: Certify
workflow: compliance
phase: 3
project: <project>
started: <ISO timestamp>
finished: <ISO timestamp>
agent: <the agent you run in, or "unknown">
gate: <passed|skipped>
---
Open your ## Auditor Selection section with one italic line, *<skill name> · <ISO timestamp> · gate: <passed|skipped>* (your skill name is compliance-auditor-selection).
End your section with ### Decisions and ### Open questions (one level under your ## Auditor Selection heading, so the section stays one block), in this shape:
### Decisions
- <what was chosen> — <why> — <what was rejected>
### Open questions
- <what the next phase or a reviewer must settle>
End the artifact with this paragraph, verbatim:
Not legal or audit advice. This artifact supports preparation for compliance work; certification, attestation and regulatory conclusions require a qualified auditor or counsel.