g-bastianelli acid-prophet:audit-spec
Identify what would force an implementing engineer to guess, and what evidence resolves it. The requested audit is read-only unless the user also authorized specific metadata repairs.
Voice
Read ../../persona.md; it is canonical for this skill's user-facing output, and its scope ends at the final report.
Review
- Resolve the requested spec and project root. Use the explicit path when supplied; ask if selection is ambiguous. Verify the file is readable. Outside a git repository, use the available project directory and report missing repository context.
- Resolve
PLUGIN_ROOTfrom this skill's../..directory. Read../../shared/spec-format.mdfor source identities and Audit readiness, then read${CLAUDE_PLUGIN_ROOT}/shared/agent-runtime-map.md(substitutePLUGIN_ROOToutside Claude Code). Dispatchacid-prophet:spec-auditorwithSPEC_PATH,PROJECT_ROOT,PLUGIN_ROOT, andMODE: report-only. - Read the full returned report using the Audit readiness rules. Check its completeness, findings, and verdict together; preserve the actual report. Request one correction if it is incomplete or contradictory. If that fails, report the unresolved discrepancy with its evidence and keep readiness blocked.
- Lead with behavioral blockers, affected criteria, and decisions needed. Link the
complete report or include it if short. Distinguish an implementation blocker from
a transport/metadata repair and from an optional improvement. Report
ready for ratification | blocked; audit readiness never changes spec status.
Authorized follow-up
If the user requested fixes, apply only metadata repairs whose values are established by
the document or its history. Identify the frontmatter block, then use normal file-edit
tools to change only those keys. Preserve the body and unrelated metadata, and re-read
the diff to confirm the scope. If the frontmatter is ambiguous, report that problem
instead of guessing its boundaries or values. Reject a proposed repair to
spec-version, status, verified-by, linear-project, or an acceptance id. Those
fields carry version, approval, or external-link state and require their owning workflow.
An audit may flag missing sections; auto-fixing metadata cannot supply their meaning.
Re-audit after repairs and use only the new verdict. Leave changes uncommitted unless a
commit was requested. Never turn a fix suggestion into an unsolicited mutation.
For requested behavioral revisions, pass the source and findings to
acid-prophet:write-spec, preserving accepted ids and the user's stated intent.
When a Linear handoff is already requested, the current report is eligible, the spec is
ratified, and linear-project is _none_:
REQUIRED SUB-SKILL: Use linear-devotee:create-project with the absolute spec path.
A draft that audits cleanly still goes through ratification before that handoff. For an already linked spec, report the existing project rather than creating another one. Otherwise finish the audit without a mandatory menu or commit prompt.
Completion
Report the spec path, readiness verdict, blocker/warning/info counts, any repairs actually applied, and the next action taken. An unreadable file or malformed report is reported as blocked, never as an empty successful review.