skills.rest
Tschonsen
TschonsenCOMMUNITY
Explore all skills by this author →
GitHub

audit

Audit cross-plan trace links and contradictions, outputting AUDIT.md with a GO/NO-GO verdict.

Updated Apr 19, 2026
Search Tags:#audit#risk-management#design-system#go-no-go#cross-plan#trace-link
One-click install
npx skills add https://github.com/Tschonsen/spec-driven-claude-development --skill audit-tschonsen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/Tschonsen/spec-driven-claude-development/tree/main/plugin/sdcd/skills/audit
Command: npx skills add https://github.com/Tschonsen/spec-driven-claude-development --skill audit-tschonsen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-plan auditing ensures all relevant plans are aligned and ready before implementation, reducing drift and rework.

Core Features & Use Cases

  • Cross-plan trace checks verify that every design decision anchors to a higher-level plan and that all required plans are present.
  • Contradiction detection surfaces conflicts between Ur-Plan, Data-Plan, Backend-Plan, and Frontend-Plan.
  • Open questions aggregation collects all open questions into a single rollup for fast resolution.

Quick Start

Run the audit to validate all applicable plans before starting implementation.

Frequently Asked Questions about audit

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

FAQPage Schema
How do I check for contradictions across multiple design and implementation plans before coding?▼

Cross-plan auditing traces relationships across Ur-Plan, Data-Plan, Backend-Plan, Design-System, and Frontend-Plan to surface contradictions and verify all required plans are present before implementation starts.

What is a cross-plan trace check and when do I need it?▼

A cross-plan trace check validates that every design decision anchors to a higher-level plan. You need it when multiple design and implementation plans exist to reduce drift and rework before coding begins.

How do I aggregate open questions from separate plans into a single rollup?▼

Cross-plan auditing collects open questions from Ur-Plan, Data-Plan, Backend-Plan, and Frontend-Plan into a single rollup within a formal AUDIT.md output for fast resolution before development.

Can I generate a go-no-go verdict for implementation readiness across design plans?▼

Yes, cross-plan auditing outputs a formal AUDIT.md containing trace-link findings, contradictions, and rolled-up open questions, concluding with a GO/NO-GO verdict to validate overall readiness.

What should I do if my design decisions are not anchoring to a higher-level plan?▼

Perform a cross-plan audit to identify missing trace links. The audit validates that every design decision anchors to a higher-level plan and highlights unanchored decisions in the AUDIT.md findings.

Related Skills

Explore More Software Engineering Skills→
TschonsenTschonsen

frontend-plan

Generate a frontend architecture plan from approved Ur-Plan and Backend-Plan documents.

Community
Advanced
91zgaoge91zgaoge

create-plan

Generate structured coding task plans with intent, scope, and action items.

Community
Basic
txema-puchtxema-puch
1

plan-design-review

Evaluate design plan documents for gaps and actionable fixes.

Community
Advanced
jnPiyushjnPiyush

code-review-and-audit

Automate code review, security audits, and compliance verification in CI/CD pipelines.

Community
Advanced