sdlc-audit-criteria

Applies eleven prose failure modes to audit SDLC documents and returns structured JSON findings.

Updated Sep 11, 2026
One-click install
npx skills add https://github.com/zhixuan312/zz-stack --skill sdlc-audit-criteria-zhixuan312
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdlc-audit-criteria
Source: https://github.com/zhixuan312/zz-stack/tree/main/catalog/sdlc/sdlc-flow/skills/sdlc-audit-criteria
Command: npx skills add https://github.com/zhixuan312/zz-stack --skill sdlc-audit-criteria-zhixuan312

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Documents like specs and plans are executed by literal-following workers who get stuck on ambiguity, contradictions, and missing acceptance criteria. This Skill provides the shared audit standard — eleven failure modes, four evidence shapes, and severity calibration — so spec and plan audits apply one consistent bar instead of diverging copies. ## Core Features & Use Cases - Eleven sequential failure-mode passes: recommendation-coherence, internal contradiction, duplication, unsupported independence, argument soundness, constraint completeness, fix actionability, drift, scope creep, structural consistency, and metadata completeness. - Strict evidence grounding: every finding must use a doc quote, absence reference, wrong-claim, or internal-coherence shape, prefixed with its source heading or file path. - Immutable round recording: findings are registered via source_add against the audited document revision, and a JSON block is returned as the final response — never a written document. - Use Case: Dispatched as one round of sdlc-spec-audit, load this Skill first, read the stored spec revision with document_present, run the eleven passes, and register the round as a source the next spec revision must cite. ## Quick Start Load the sdlc-audit-criteria skill, then audit the stored revision of the given spec or plan through all eleven failure modes and return the findings JSON.

Frequently Asked Questions about sdlc-audit-criteria

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit a spec document for contradictions and ambiguity?▼

Run the eleven failure modes sequentially, reading the document through only one lens at a time, then consolidate findings into the JSON envelope. Each finding needs one of four evidence shapes — doc quote, absence reference, wrong-claim, or internal-coherence — prefixed with its source heading.

What failure modes does an SDLC document audit check?▼

It checks recommendation-coherence, internal contradiction, cross-item duplication, unsupported independence claims, argument soundness, completeness against constraints, fix actionability, drift and staleness, scope creep, structural consistency, and metadata completeness.

Can this audit skill run on its own?▼

No. It is loaded by sdlc-spec-audit or sdlc-plan-audit and supplies the shared half of the audit — the failure modes, evidence shapes, and output format. The dispatching auditor skill carries what differs about the specific document being audited.

Does the audit modify the document it reviews?▼

No. The audit is strictly read-only by discipline; editing the document would destroy the caller's ability to decide which findings to accept. Findings go to an immutable source via source_add and a JSON response, never into the document itself.

How are audit findings recorded and tracked across rounds?▼

Each round calls source_add with the findings, the supported document, and the audit stage, creating a new immutable source per round. The platform refuses the next document revision until that source is cited, so the answering version acknowledges the round on its face.