Stop discovering gaps in a specification during development. SpecLint validates a normalized spec format, detects critical missing pieces and finally makes reliable analysis possible before coding.
The problem
Today, teams write specifications in Confluence, Notion or Google Docs with inconsistent structures and uneven levels of detail. The result: uncovered business rules, forgotten error cases, blurry impacts and ambiguities discovered too late.
SpecLint introduces a simple framework: a clear spec format, then a validation engine that checks what can be verified formally.
What SpecLint does
SpecLint checks that a specification contains the expected sections, traceability links and the elements required for an actionable read.
Uncovered business rules, missing acceptance criteria, forgotten edge cases, poorly documented impacts: the report highlights where the spec is fragile.
Once the spec is normalized, you can unlock backlog generation, impact mapping and more reliable automation.
Key checks
SpecLint does not claim to judge business truth. It checks formal quality, expected completeness and traceability between spec elements.
Required sections are present
Unique IDs and valid references
Business rule coverage by acceptance criteria
Scenarios linked to the right actors
Missing error cases and edge cases
Expected UI artifacts when visual impact exists
How it works
A Markdown spec with required and optional sections: Scope, Actors, Rules, Scenarios, AC, Impacts, Artifacts…
The engine analyzes completeness, traceability and structural coherence. It does not pretend to judge the business domain, it judges the formal quality of the spec.
You get an actionable report with errors, warnings and suggestions to strengthen the spec before development kickoff.
Product vision
Once the spec is normalized and validated, new capabilities become possible: Feature and User Story generation, impact mapping, coverage analysis and more reliable automation. SpecLint is the first building block.
FAQ
No. It acts like a specification linter: it helps verify structure, coverage and traceability, but it does not replace business judgment or human review.
Yes. SpecLint relies on a normalized spec template. That is precisely what makes the analysis reliable and actionable.
The starting point is a simple Markdown format, easy to version and integrate into existing workflows.
Not directly. However, the spec can reference visual artifacts and SpecLint can verify their presence when they are expected.
Early access
Join the waitlist to follow the release of SpecLint v0.1 and see the first lintable spec examples.