# Validate Project Requirements Before Work Starts

Unclear requirements cause wasted generation cycles and rework. This skill checks inputs against saved standards before a coding or content pipeline continues.

## Install

```bash
npx skillstore add abejitsu/validate-requirements
```

## Metadata

- - Status: approved
- - Slug: abejitsu-validate-requirements
- - Version: 1.0.0
- - Author: AbeJitsu
- - GitHub username: AbeJitsu
- - License: MIT
- - Repository: https://github.com/AbeJitsu/Game-Settings-Panel/tree/main/.claude/skills/validate-requirements
- - Ref: main
- - Supported tools: Claude, Codex, Claude Code
- - Risk level: low
- - Risk factors: filesystem
- - Quality score: 79
- - Quality tier: bronze
- - Public page: https://skillstore.pages.dev/skills/abejitsu-validate-requirements
- - Manifest: https://skillstore.pages.dev/api/skills/abejitsu-validate-requirements/manifest

## Capabilities

- Checks whether user input is complete enough to begin work.
- Compares requirements with saved project validation rules.
- Identifies missing context, unclear goals, and conflicting requirements.
- Returns a structured validation result with issues and recommendations.
- Suggests specific clarification questions when input is incomplete.

## Use Cases

- Screen Component Requests: Check whether a component request includes purpose, behavior, props, and constraints before generation starts.
- Validate Content Briefs: Confirm that a writing prompt includes topic, audience, format, and success criteria before drafting begins.
- Gate Automation Pipelines: Use a validation step before build, refactor, or documentation workflows continue.

## Prompt Templates

### Check Basic Requirements

```
Validate these requirements against the project standards. Tell me what is missing and what I should clarify before work begins: [paste requirements].
```

### Review a Feature Brief

```
Review this feature brief for completeness, clarity, format, and standards alignment. Return the blocking issues first: [paste brief].
```

### Prepare Clarification Questions

```
Validate this request and produce only the most important clarification questions needed to proceed safely: [paste request].
```

### Run Pipeline Gate Review

```
Act as the first quality gate for this workflow. Load the relevant project standards, validate the input, and recommend whether to proceed or pause: [paste workflow input].
```

## Limitations

- Requires saved standards to apply project-specific validation rules.
- Does not create or modify the final implementation.
- Cannot verify external links or unavailable source material by itself.
- Uses general validation when no project standards exist.

## Best Practices

- Run validation before generation, refactoring, or drafting starts.
- Keep project standards current so checks reflect the team's real expectations.
- Ask one or two specific clarification questions when input is close to valid.

## Anti Patterns

- Using the skill after implementation work is already complete.
- Treating vague requirements as valid because they mention a broad topic.
- Rejecting near-complete input without suggesting concrete clarification questions.

## Security Audit

- - Safe to publish: true
- - Audited at: 2026-06-28T04:32:41.385\+00:00
- - Summary: Static analysis reported command execution and weak cryptography, but the cited lines are Markdown fences, prose, and JSON examples. No shell execution, network access, secret handling, or cryptographic code is present. The skill does instruct the assistant to read saved project standards, so publication is acceptable with a low filesystem-access note.

## Stats

- - Views: 214
- - Downloads: 6
- - Favorites: 0
- - Popularity score: 0