review-spec

Cross-artifact consistency checks identify contradictions, scope drift, and terminology mismatches between linked proposals, specs, and task lists. Requirement and task validation ensures testable scenarios, concrete acceptance criteria, and no unresolved placeholders remain before engineering resources are allocated.

Pre-implementation spec validation reviews multiple linked design documents to find untestable requirements, missing features, and misaligned scope. You need it when teams produce proposals, architecture documents, and implementation task lists, preventing costly rework and misaligned deliverables before coding starts.

Yes, cross-artifact alignment reviews all linked design documents in a project folder together. It catches dropped items, terminology mismatches, and contradictions between the feature proposal, technical spec, design doc, and implementation task list to ensure full scope alignment.

Requirement and task validation ensures all requirements have testable scenarios covering edge cases. It verifies that tasks are self-contained with concrete acceptance criteria and checks that no unresolved placeholders remain in the design artifacts before development begins.

Cross-artifact consistency checks compare linked design documents to identify scope drift, dropped items, and contradictions. Reviewing the feature proposal, architecture document, and task list together catches misalignments that would cause wasted implementation effort and rework later.

No specific framework is required. The review applies to standard software development workflows where teams produce multiple linked design documents like proposals, specifications, architecture documents, and implementation task lists to define feature scope and implementation plans.