
Speci5 Check
- 1 installs
- 2 repo stars
- Updated April 12, 2026
- davidnguyen/speci5
Validates specifications and requirements compliance through automated checking.
About
Tool for specification validation and compliance checking against requirements. QA automation.
- Spec validation
- Compliance checking
Speci5 Check by the numbers
- 1 all-time installs (skills.sh)
- Ranked #1,750 of 2,153 Testing & QA skills by installs in the Skillselion catalog
- Data as of Jul 8, 2026 (Skillselion catalog sync)
npx skills add https://github.com/davidnguyen/speci5 --skill speci5-checkAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1 |
|---|---|
| repo stars | ★ 2 |
| Last updated | April 12, 2026 |
| Repository | davidnguyen/speci5 ↗ |
What it does
Validates specifications and requirements compliance through automated checking.
Files
Check
Verify implementation progress by inspecting source code against a story's plan.
Triggers
Activate this skill when the user wants to:
- Verify if planned tasks have been implemented
- Check progress on a story
- Update task checkboxes based on current code state
- Get a status report on implementation progress
Rules
1. Do NOT modify source code — this is a read-only verification skill. 2. Do NOT modify story.md or feature.md. 3. Only modify plan.md to toggle task checkboxes and add brief inline notes. 4. Be conservative — only mark a task complete if there is clear evidence in the code. 5. If a task is partially done, leave it unchecked and note what's missing.
Steps
1. Read the plan — Load .spec/features/<feature>/<story>/plan.md. 2. Read the story — Load story.md to understand acceptance criteria context. 3. Verify each task — For each task in the plan:
- Search the codebase for the specific files, functions, routes, components, or tests mentioned.
- Evaluate whether the implementation satisfies the task's intent, not just that a file exists.
4. Update plan.md — Toggle checkboxes:
- Completed:
- [ ]→- [x] - Regressed (removed/broken):
- [x]→- [ ] - Uncertain: leave unchecked, add a note.
5. Report summary — Present results to the user.
Output
See output template.
After updating plan.md, print a summary:
## Check Summary: <Story Title>
Progress: X/Y tasks complete
### Completed
- ✅ Task description
### Remaining
- ⬜ Task description — (reason or what's missing)