Skip to content
Back to skills

Sr Validate

ASecurity

Phase 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.

  • 19 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 11, 2026
toolspythongobash

Security analysis

A100/100

Scanned September 11, 2026

npx -y skills add DangQuangSE/team-development-skills --skill sr-validate --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Sr Validate?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Sr Validate
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/dangquangse-sr-validate/badge)](https://www.skillsdirectory.com/skills/dangquangse-sr-validate)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: sr:validate
description: >
  Phase 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.
user-invocable: true
metadata:
  input:  projects/{slug}/srs/ directory (from /sr:generate)
  output: validation verdict + fixes applied inline
  next:   /sr:improve
---

# 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:
```bash
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:
1. Identify the affected SRS section file
2. Fix the issue following IEEE 830 rules:
   - `missing-section`: add the section with correct heading format
   - `fr-no-shall`: rewrite the Requirement line with explicit "shall" clause
   - `fr-numbering-gap`: renumber FRs to fill gaps (update all references)
3. 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
```

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…