overlap-detector

To detect duplicate requirements, compare the new requirement against existing specs and tasks using weighted overlap analysis of titles, tags, user stories, components, and domains. The analysis classifies results as full-duplicate, partial-overlap, related, or none, and returns actionable recommendations to merge or proceed.

Overlap analysis in requirements planning is the process of comparing a new requirement against existing specs and tasks to identify duplicate work. It computes weighted similarity scores across metadata fields like titles, tags, and user stories, then classifies the relationship to prevent redundant efforts.

You can check for task overlaps by reading the task index file and analyzing titles, tags, user stories, components, and domains. The system calculates weighted overlap scores and classifies the new task against existing entries as a full-duplicate, partial-overlap, related, or none.

Yes, overlap analysis reads the spec index and task index files to compare new requirements against existing entries. It analyzes titles, tags, user stories, components, and domains to generate similarity scores and classify the overlap level.

The best way to prevent duplicate work is to run an overlap detection analysis during spec creation and task planning. This flags duplicates, partial overlaps, and related efforts by computing weighted similarity scores across requirement metadata, providing recommendations to merge or coordinate.

Yes, overlap detection works with both spec and task planning. It reads the respective index files for specs and tasks, analyzes their metadata fields, and flags duplicates, partial overlaps, and related work to prevent redundant efforts across both planning stages.