Review Spec

Review design artifacts for internal consistency, cross-artifact alignment, and obvious gaps. Accept requirements as written — flag conflicts between artifacts, not disagreements with product decisions.

Flow

1. Discover and Classify

Read all *.md files recursively in the provided directory. Classify each by role using the following path-based heuristics (applied in order; first match wins):

1. proposal.md or motivation.md (anywhere in the path) → Motivation / proposal
2. design.md or architecture.md (anywhere in the path) → Design / architecture
3. spec.md, or any file matching specs/**/spec*.md → Requirements / specs
4. tasks.md, or any file matching tasks/*.md → Tasks / plan
5. Fallback: infer role from content (headings, structure). If ambiguous, assign the closest matching role and note the ambiguity.

An artifact may combine roles; assign the primary role first. Missing artifacts are not errors.

2. Review Checks