Problem Statement
Problem Statement:
Developers already describe requirements in GitHub Issues — user stories, acceptance criteria, labels,
discussions. But when starting SDD, they rewrite everything from scratch in spec.md. The information
exists; it just needs transformation. This creates duplicate work and context loss between issue
tracking and specification.
Proposed Solution
Proposed Solution:
A community extension with 3 commands:
/speckit.issue.import — Read a GitHub Issue (title, body, labels, comments) and generate spec.md
with structured requirements, scenarios, and acceptance criteria
/speckit.issue.sync — Keep spec artifacts updated when the source issue is modified
/speckit.issue.link — Add bidirectional traceability between spec artifacts and their source issue
Alternatives Considered
Alternatives Considered:
Manually copying issue content into spec.md — but this loses structure, is error-prone, and doesn't
stay in sync when the issue is updated.
Component
Other
AI Agent (if applicable)
None
Use Cases
No response
Acceptance Criteria
No response
Additional Context
No response
Problem Statement
Problem Statement:
Developers already describe requirements in GitHub Issues — user stories, acceptance criteria, labels,
discussions. But when starting SDD, they rewrite everything from scratch in spec.md. The information
exists; it just needs transformation. This creates duplicate work and context loss between issue
tracking and specification.
Proposed Solution
Proposed Solution:
A community extension with 3 commands:
/speckit.issue.import— Read a GitHub Issue (title, body, labels, comments) and generate spec.mdwith structured requirements, scenarios, and acceptance criteria
/speckit.issue.sync— Keep spec artifacts updated when the source issue is modified/speckit.issue.link— Add bidirectional traceability between spec artifacts and their source issueAlternatives Considered
Alternatives Considered:
Manually copying issue content into spec.md — but this loses structure, is error-prone, and doesn't
stay in sync when the issue is updated.
Component
Other
AI Agent (if applicable)
None
Use Cases
No response
Acceptance Criteria
No response
Additional Context
No response