Releases: ismaelJimenez/spec-kit-verify
Releases · ismaelJimenez/spec-kit-verify
v1.0.1
Added
- Cross-platform configuration loading scripts (Bash and PowerShell)
- CI workflow with Bash and PowerShell test suites
.extensionignorefor cleaner extension packaging- Allow running verification from any branch by prompting the user to select a feature when not on a feature branch
Changed
- Aligned Step 3 spec/plan loading with Steps 5–6 consumption in verify command
- Partial alignment with analyze extension conventions
- Removed review handoffs in favour of streamlined flow
Fixed
- Fixed load configuration handling
v1.0.0 - Initial Release
Spec-Kit Verify Extension v1.0.0
Post-implementation quality gate that validates implemented code against specification artifacts.
Features
- Implementation verification — Checks implemented code against spec, plan, tasks, and constitution to catch gaps before review
- Actionable report — Produces a verification report with findings, metrics, and next actions across 7 categories
- Configurable — Adjust report size limits via
verify-config.yml - Automatic hook — Optional
after_implementhook prompts verification after/speckit.implement - Read-only & idempotent — Never modifies source files or artifacts; repeated runs produce the same report
Verification Categories
| Category | What it checks |
|---|---|
| Task Completion | All tasks marked complete |
| File Existence | Task-referenced files exist on disk |
| Requirement Coverage | Every requirement has implementation evidence |
| Scenario & Test Coverage | Spec scenarios covered by tests or code paths |
| Spec Intent Alignment | Implementation matches spec intent and acceptance criteria |
| Constitution Alignment | Constitution principles are respected |
| Design & Structure Consistency | Architecture and conventions match plan.md |
Usage
# Install
specify extension add verify
# Run after implementation
/speckit.verifyRequirements
- Spec Kit >= 0.1.0
Links
- Documentation: README
- Changelog: CHANGELOG.md
- License: MIT