Spec Conformance Review FAQs

Question 1

Can I target the review at a specific folder?

Accepted Answer

Yes, you can provide an optional path argument to focus the review on a specific subdirectory or module, rather than scanning the entire repository.

Question 2

Does this skill automatically modify my source code?

Accepted Answer

No, the Spec Review skill is strictly non-destructive. it focuses on analysis and reporting, ensuring that your code remains untouched while providing clear paths for manual fixes.

Question 3

Which files does the Spec Review skill require to run?

Accepted Answer

The only mandatory requirement is a spec.md file within the feature directory. It can also optionally use plan.md and constitution.md to perform more comprehensive architectural and principle-based audits.

Question 4

How does the skill prevent duplicate issue reporting?

Accepted Answer

The skill performs a deduplication step by checking both open and closed beads (issues). It skips creating new beads for issues that are already tracked or have been intentionally resolved.

Question 5

What happens if I haven't initialized the beads system yet?

Accepted Answer

The skill includes a prerequisite check. If beads are not initialized, it will stop and provide instructions on how to run the 'bd onboard' command first.

Spec Conformance Review

Key Features

Use Cases

Spec Conformance Review

Key Features

Use Cases