Spec Validation & Repair FAQs

Question 1

How does this skill handle complex dependency issues like circular loops?

Accepted Answer

The skill performs deep dependency analysis to detect cycles, deadlocks, and bottlenecks. While it can auto-fix simple mismatches, it provides detailed Markdown reports and 'analyze-deps' findings to help you manually resolve complex logical loops that require human judgment.

Question 2

What types of issues can this skill automatically fix?

Accepted Answer

The skill can automatically repair 13 common issue types, including incorrect task count rollups, missing metadata blocks, orphaned nodes, parent/child hierarchy mismatches, malformed timestamps, and inconsistent status values.

Question 3

When is the best time to use the sdd-validate command?

Accepted Answer

You should use it whenever you create a new spec, after making manual edits, or before running execution-heavy SDD tasks. It's a critical safety check to ensure your specification is logical and free of circular dependencies before Claude begins development.

Question 4

What is the Spec Validation & Repair skill?

Accepted Answer

This is a specialized Claude Code skill designed to maintain the structural integrity of Spec-Driven Development (SDD) JSON files. It identifies structural errors, calculates complexity metrics, and provides an automated 'fix' command to resolve common specification issues.

Question 5

How do I know if my specification is fully repaired?

Accepted Answer

By following the 'validate-fix' cycle. If the error count decreases after running 'sdd fix', you should re-validate. Once the error count plateaus (remains the same for 2+ passes), use the '--verbose' flag to identify the final issues requiring manual intervention.

Spec Validation & Repair

Spec Validation & Repair

主な機能

ユースケース

主な機能

ユースケース