Version
spec-kit v1.0.1 (.claude/skills/speckit-taskstoissues/SKILL.md, dedup step around the list_issues flow)
Description
Task IDs like T001 are local to one feature's tasks.md and restart from T001 in every feature. The dedup step, however, matches repository issues by task ID without scoping to the current feature: if feature 001-auth already produced an issue titled with T001, then running /speckit-taskstoissues for feature 002-billing sees "T001 exists" and skips creating the issue for billing's T001 — a silent gap in the tracker, in exactly the multi-feature repos this command targets.
This is the inverse of #2968 (which was about creating duplicates): the fix direction there makes the matching aggressive enough to now suppress valid tasks.
Expected behavior
- Include a stable feature identifier (the
NNN-name spec dir) in each created issue's title or a label, and require both the feature identity and the task ID to match before skipping.
- Re-check for existing feature+task issues immediately before creation so two concurrent invocations don't race the fetch-then-create sequence.
Version
spec-kit v1.0.1 (
.claude/skills/speckit-taskstoissues/SKILL.md, dedup step around thelist_issuesflow)Description
Task IDs like
T001are local to one feature'stasks.mdand restart from T001 in every feature. The dedup step, however, matches repository issues by task ID without scoping to the current feature: if feature001-authalready produced an issue titled withT001, then running/speckit-taskstoissuesfor feature002-billingsees "T001 exists" and skips creating the issue for billing's T001 — a silent gap in the tracker, in exactly the multi-feature repos this command targets.This is the inverse of #2968 (which was about creating duplicates): the fix direction there makes the matching aggressive enough to now suppress valid tasks.
Expected behavior
NNN-namespec dir) in each created issue's title or a label, and require both the feature identity and the task ID to match before skipping.