sdlc-plan-audit

Audits plan.md against prose failure modes and the plan's execution contract.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? A plan that a low-judgement executor will follow literally can fail in ways nobody notices until execution breaks: untraced acceptance criteria, tasks without contracts, fake checks, broken dependency order, or a missing full-suite gate. This Skill provides a read-only audit round that catches those defects before sdlc-execute dispatches the plan's tasks. ## Core Features & Use Cases - Prose failure-mode audit: Applies the eleven shared prose failure modes loaded from the sdlc-audit-criteria skill, returning findings in four fixed evidence shapes. - Plan contract audit: Checks eleven plan-specific points including AC traceability, task contracts (Inputs/Outputs/Data mapping/Errors/Behavior), real check files with shell-safe Run commands, heading format, dependency order, and the full-suite gate. - Recorded audit trail: Registers each round via source_add as a SOURCE supporting plan.md, and returns findings as a JSON envelope to the dispatching main agent. - Use Case: After sdlc-plan produces plan.md and before sdlc-execute runs, dispatch this Skill to verify every spec AC is traced to a task and every task is executable, so undispatchable or incomplete plans are sent back for revision. ## Quick Start Dispatch a plan audit round on the current plan.md and return the findings JSON to the main agent.

Frequently Asked Questions about sdlc-plan-audit

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

FAQPage Schema
How do I audit an implementation plan before executing it?▼

Run a plan audit that checks AC traceability, per-task contracts, real check files, dependency order, and the full-suite gate. This Skill performs that audit read-only and returns findings as JSON to the dispatching agent.

What makes a plan executable by an AI agent?▼

Each task needs a five-bullet contract (Inputs, Outputs, Data mapping, Errors, Behavior), a testable technical AC traced to a business AC, unambiguous task IDs, and deterministic checks with shell-safe Run commands naming real project runners.

Does the plan audit modify or fix the plan?▼

No. The audit is strictly read-only: it registers findings via source_add and returns a JSON envelope. The plan owner and the main agent decide what to fix and whether to send the plan back to sdlc-plan.

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

It runs after sdlc-plan writes plan.md and before sdlc-execute dispatches tasks. It does not audit the spec, which was already covered by sdlc-spec-audit, except for genuine contradictions between the two documents.

What are the limitations of a read-only plan audit?▼

It cannot judge whether the spec itself was right, cannot predict implementation details, and reports unresolvable check paths or runners as unverified rather than broken. Read-only is a discipline, not an enforced tool denial.