spec-review-en

You can review markdown specifications for inconsistencies and code drift by running a targeted check that compares specs against routes, handlers, migrations, and components. The review presents findings one by one for your approval before applying any fixes.

Code drift in spec review identifies mismatches between your specs and actual routes, handlers, migrations, models, and directory structures. Consistency checks scan for cross-document contradictions across your markdown files to ensure alignment.

Yes, you can target a specific spec markdown file path for review. While it automatically locates files under docs/spec/specs/design directories, you can provide a custom path to restrict consistency, code-drift, or quality checks to that location.

You fix spec quality defects like ambiguous wording, broken links, and table formatting issues using quality mode. It presents each finding individually, letting you choose Fix, Modify, Skip, or Fix all remaining, while editing only existing files and updating revision history.

Yes, the spec review process updates revision history automatically after fixes. When you approve a correction, it edits only existing files and appends execution-date entries to the revision history to maintain an accurate change log.

A limitation of automated spec review is that it edits only existing files and requires interactive confirmation for each finding. It cannot create new documents and focuses strictly on consistency, code drift, diagram validity, and quality checks within detected markdown paths.