DangQuangSE/team-development-skills / .agents/skills/sr-validate
sr:validate
VerifiedPhase 7 of the SRS workflow. Runs srs_validator.py --dir on the generated SRS files, reports errors and warnings, auto-fixes ERRORs, and outputs a COMPLIANT / PARTIALLY COMPLIANT / NON-COMPLIANT verdict.
sr:validate
Goal: validate the generated SRS against IEEE 830-1998. Fix all ERRORs before reporting. WARNings are captured for the improvement report.
Step 0 — Identify Project
AskUserQuestion: "Which project to validate? (slug)"
Check that projects/{slug}/srs/ exists and contains .md files.
If missing: tell user to run /sr:generate first.
Step 1 — Run Validator
Execute:
python .claude/scripts/srs_validator.py --dir projects/{slug}/srs/
Capture stdout. Display the full validation table.
Step 2 — Fix ERRORs Immediately
For each ERROR finding:
- Identify the affected SRS section file
- Fix the issue following IEEE 830 rules:
missing-section: add the section with correct heading formatfr-no-shall: rewrite the Requirement line with explicit "shall" clausefr-numbering-gap: renumber FRs to fill gaps (update all references)
- State what was fixed:
FIXED [ERROR] fr-no-shall in FR-07 → added "shall" clause
After fixing all ERRORs: re-run validator and confirm no new ERRORs.
Step 3 — Collect WARNings
List all WARN findings but do NOT fix them here — they go into the improvement report.
Format:
WARN: unresolved-tag — 3 [TBD] tags remain (NFR-03, NFR-07, §1.3)
WARN: fr-incomplete-gwt — FR-12: missing "Then:" field
WARN: nfr-no-numeric — NFR-05 Response Measure has no numeric threshold
Step 4 — Verdict
Output:
## Validation Result
Verdict: COMPLIANT | PARTIALLY COMPLIANT | NON-COMPLIANT
File: projects/{slug}/srs/ ({N} files)
ERRORs fixed: {count}
WARNings open: {count} → captured in /sr:improve report
Next: /sr:improve → improvement report + warning resolution guide
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |