Claude Skills
CollectionsCompareWorkflowsNominate
Sign inSign up
© 2026 Curated Agent Skills·Learn more about Agent Skills
Back to repository

requirement-validator

verified

Validate pseudo-code completeness and identify gaps

View on GitHub

Marketplace

pseudo-code-prompting-plugin

EladAriel/pseudo-code-prompting-plugin

Plugin

pseudo-code-prompting-plugin-v2

development

Repository

EladAriel/pseudo-code-prompting-plugin
2stars

skills/requirement-validator/SKILL.md

Last Verified

February 3, 2026

Install Skill

Select agents to install to:

Scope:
npx add-skill https://github.com/EladAriel/pseudo-code-prompting-plugin/blob/main/skills/requirement-validator/SKILL.md -a claude-code --skill requirement-validator

Installation paths:

Claude
.claude/skills/requirement-validator/
Powered by add-skill CLI

Instructions

# Requirement Validator

Check pseudo-code for completeness and identify missing requirements.

## WHAT THIS DOES

Analyzes pseudo-code and generates a validation report with:

- ✓ PASSED CHECKS (what's good)
- ⚠ WARNINGS (nice-to-have improvements)
- ✗ CRITICAL ISSUES (must-fix problems)
- 📋 EDGE CASES (scenarios to consider)

## VALIDATION CHECKLIST

### Check 1: Required Parameters

Are core parameters present?

```text
✓ PASS: Function name descriptive, type specified, core params present
✗ FAIL: Missing required parameter: [name]
```

### Check 2: Security Requirements

Is authentication/authorization specified?

```text
✓ PASS: Auth type specified, permissions defined
✗ FAIL: Security not addressed (auth/permissions missing)
⚠ WARN: Auth mentioned but flow undefined
```

### Check 3: Error Handling

Are error scenarios covered?

```text
✓ PASS: Error handling strategy defined
✗ FAIL: No error handling specified
⚠ WARN: Only happy path covered, error cases missing
```

### Check 4: Validation Rules

Are inputs validated?

```text
✓ PASS: Input validation rules specified
✗ FAIL: User input not validated
⚠ WARN: Validation incomplete (missing [field])
```

### Check 5: Edge Cases

Are boundary conditions addressed?

```text
✓ PASS: Edge cases considered (null, empty, overflow)
⚠ WARN: Edge case not addressed: [scenario]
```

## OUTPUT FORMAT

```text
═══════════════════════════════════════
Validation Report
═══════════════════════════════════════

✓ PASSED CHECKS
- [Check 1 passed]
- [Check 2 passed]
- [Check 3 passed]

⚠ WARNINGS (Medium Priority)
- [Warning 1: what's missing]
- [Warning 2: what could be better]

✗ CRITICAL ISSUES (Must Fix)
- [Critical 1: what's broken]
- [Critical 2: what's missing]

📋 EDGE CASES TO CONSIDER
- [Edge case 1: scenario not covered]
- [Edge case 2: boundary condition]

## Summary

Passed: [N] | Warnings: [N] | Critical: [N] | Edge Cases: [N]

Overall: [READY FOR IMPLEMENTATION | NEEDS FIXES | MAJOR GAPS]
```

## EXAMPLE

### Inp

Validation Details

Front Matter
Required Fields
Valid Name Format
Valid Description
Has Sections
Allowed Tools
Instruction Length:
3591 chars