Spec Reviewer FAQs

Question 1

How does it handle complex features spanning multiple domains?

Accepted Answer

For specs involving 10 or more files or multiple architectural layers, it checks the .claude/context/ directory to ensure corresponding context documents exist for proper planning.

Question 2

What kind of feedback does the skill provide?

Accepted Answer

If successful, it returns a simple 'PASS'. If issues are found, it provides numbered plaintext feedback focusing on scope, edge cases, architecture, and pattern compatibility.

Question 3

Can it identify outdated coding patterns?

Accepted Answer

Yes, the skill is designed to flag outdated patterns or deprecated library approaches by verifying idiomatic usage against the current codebase stack.

Question 4

What files does this skill examine to validate my spec?

Accepted Answer

It reads the spec file itself, CLAUDE.md (project root and .claude/), any rules in .claude/rules/, and any specific files referenced as 'Related files' in the spec.

Question 5

When should I use the Review Spec skill?

Accepted Answer

Use it immediately after creating a feature specification and before starting the implementation phase to catch design flaws and architectural inconsistencies early.

Spec Reviewer

主要功能

使用场景

Spec Reviewer

主要功能

使用场景