Every requirement, traced to the evidence behind it.
SpecThread links each requirement to the issues, pull requests, commits, checks, and releases that implement it. A reviewer reads one thread and makes the call.
Acme/billing-serviceRequirements connected to the evidence that implements them.
SpecThread connects software requirements to inspectable implementation evidence: GitHub issues, pull requests, commits, automated checks, and releases.
The problem
A board can show that a task moved to “Done”, but not which code implemented the requirement, which checks ran, or whether it reached a release.
Who it is for
Small software teams, the project managers and clients who need a readable view of progress, and the developers and reviewers who need direct links to evidence.
People decide
SpecThread keeps the evidence inspectable in one thread. Links can be suggested, but an authorized reviewer makes every acceptance decision.
“Done” on a board is a status. SpecThread shows the work.
Write the requirement
State what was requested and the acceptance criteria that would show it works.
Link the work
Connect a GitHub repository. Link the issue and pull requests; commits and checks that reference them come along.
Review the thread
Evidence lands in one chronological thread. A reviewer accepts, rejects, or asks for more.
Scattered across tools. Read in one line.
A person makes the acceptance decision.
An authorized reviewer accepts, rejects, or requests more evidence. The decision is recorded with a note and a timestamp.
- Linked
- An explicit or confirmed relationship to the requirement.
- Check passed
- A recorded automated check reported success.
- Evidence complete
- The project's evidence policy is satisfied.
- Accepted
- An authorized person approved it.
Start a thread for your next requirement.
Connect one GitHub repository. Free for small teams.
Sign up