sdlc-spec-audit

Audit spec.md against eleven prose failure modes and a seven-point specification contract.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? A specification that reads well can still fail downstream: missing components, untraceable requirements, or ambiguous scope become ordering guesses when someone plans from it. This Skill audits spec.md read-only, one round at a time, so a reader who did not write the document catches what breaks before planning begins. ## Core Features & Use Cases - Prose failure-mode audit: Applies the eleven shared failure modes from sdlc-audit-criteria, with every finding in one of four evidence shapes (doc quote, absence reference, wrong-claim, internal-coherence). - Spec contract checks: Verifies the eight canonical components, FR-to-AC traceability, the deliverable contract, inlined frozen values, exhaustive scope, blocking prerequisites, and separated workstreams. - Recorded, structured output: Registers the round as a SOURCE supporting spec.md via source_add and returns findings as a JSON envelope to the dispatching agent. - Use Case: After a team finalizes a specification with sdlc-spec and before anyone builds a plan, dispatch this audit to confirm every FR-N maps to a testable AC-N.N and no component is a heading with nothing under it. ## Quick Start Dispatch a spec audit round on the agreed spec.md and return the findings JSON to the main agent.

Frequently Asked Questions about sdlc-spec-audit

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

FAQPage Schema
How do I audit a software specification before planning?▼

Run a spec audit that checks the eight canonical components, FR-to-AC traceability, the deliverable contract, inlined frozen values, and exhaustive scope. Each finding must cite evidence as a doc quote, absence reference, wrong-claim, or internal-coherence note.

What makes a specification ready to plan from?▼

A plannable spec has all eight components written rather than named, every FR-N mapped to a testable AC-N.N, frozen values inlined verbatim, and in-scope and out-of-scope both enumerated. Blocking prerequisites must name the artifact and unblocking condition.

Does the spec audit modify the specification document?▼

No, the audit is strictly read-only. It records findings as a SOURCE supporting spec.md via source_add and returns a JSON envelope; the document's owner decides which findings to act on.

When should a spec audit run in the SDLC flow?▼

It runs after sdlc-spec, once the spec is written and agreed by the person, and before sdlc-plan. The main agent dispatches it one round at a time, with the number of rounds routed by evidence.

What are the limitations of a specification audit?▼

The audit does not judge whether the team should build the feature or which alternative was right; those decisions were settled with a person earlier. It only checks whether the document coherently says what was decided.