auditing-specs

Name: auditing-specs
Availability: InStock
Author: masa-codehub

Audit specifications against Design Docs for SSOT alignment and TDD readiness.

Updated Aug 18, 2025

Search Tags:#tdd #specifications #audit #handover #ssot #design-docs

Ready to run

npx skills add https://github.com/masa-codehub/gemini_agent --skill auditing-specs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: auditing-specs
Source: https://github.com/masa-codehub/gemini_agent/tree/main/.gemini/skills/auditing-specs
Command: npx skills add https://github.com/masa-codehub/gemini_agent --skill auditing-specs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This skill audits completed specifications against SSOT (Design Docs), verifies TDD readiness, and prepares clear handovers for the implementation phase.

Core Features & Use Cases

Integration & Coverage Validation: checks that all planning-specs dependent issues are Closed and included in the integration branch.
SSOT & Integrity Audit: compares design artifacts and ensures consistency with common definitions.
TDD Readiness & Handover Prep: generates a formal handover package and guides the TDD implementation.

Quick Start

Run the auditing workflow to verify planning-specs, SSOT integrity, and prepare the TDD handover.

Frequently Asked Questions about auditing-specs

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

FAQPage Schema

How do I verify specification readiness before starting TDD implementation?▼

To verify specification readiness for TDD, audit your specs against Design Docs to check SSOT alignment, integration status, and cross-document consistency. This governance process produces a formal spec-to-tdd handover artifact to guide implementation.

What is a spec-to-TDD handover artifact and when do I need it?▼

A spec-to-TDD handover artifact is a formal package generated by auditing specifications against Design Docs. You need it when transitioning from planning to TDD implementation to ensure SSOT integrity, verify dependent issues are closed, and guide the coding phase.

How do I audit design docs for SSOT integrity and cross-document consistency?▼

Auditing design docs for SSOT integrity involves comparing design artifacts to ensure consistency with common definitions. This process validates that all planning-specs dependent issues are closed and included in the integration branch before TDD handover.

Can I use this specification audit for integration status checks on dependent issues?▼

Yes, you can use this specification audit for integration status checks. It validates that all planning-specs dependent issues are Closed and included in the integration branch, ensuring governance and SSOT alignment before proceeding to the TDD phase.

What's the best way to prepare a formal handover package for TDD implementation?▼

The best way to prepare a formal handover package for TDD implementation is to run an auditing workflow that verifies planning-specs, checks SSOT integrity, and validates integration status to produce a comprehensive spec-to-tdd handover artifact.

Why does my TDD phase fail due to inconsistent specifications and design docs?▼

Your TDD phase may fail due to inconsistent specifications and design docs because SSOT integrity was not verified. Auditing specs against Design Docs enforces governance and cross-document consistency, ensuring a reliable handover artifact for implementation.