User Story Writer
deanpeters/Product-Manager-Skills
Writes user stories in Mike Cohn's format with Gherkin acceptance criteria, turning user needs into development-ready work with testable conditions.
Runs multi-stage validation gates with per-step scoring, pass/fail verdicts, and aggregate quality reports.
Install Validation Pipeline
$ npx skills add proffesor-for-testing/agentic-qe --skill validation-pipeline -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install proffesor-for-testing/agentic-qe validation-pipeline --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/proffesor-for-testing/agentic-qe.git skills-src && mkdir -p .claude/skills && cp -r skills-src/assets/skills/validation-pipeline .claude/skills/validation-pipeline && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "validation-pipeline" agent skill from https://github.com/proffesor-for-testing/agentic-qe/tree/main/assets/skills/validation-pipeline into .claude/skills/validation-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validation-pipeline", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/proffesor-for-testing/agentic-qe/tree/main/assets/skills/validation-pipelineType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add proffesor-for-testing/agentic-qe --skill validation-pipeline -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install proffesor-for-testing/agentic-qe validation-pipeline --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/proffesor-for-testing/agentic-qe.git skills-src && mkdir -p .agents/skills && cp -r skills-src/assets/skills/validation-pipeline .agents/skills/validation-pipeline && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "validation-pipeline" agent skill from https://github.com/proffesor-for-testing/agentic-qe/tree/main/assets/skills/validation-pipeline into .agents/skills/validation-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validation-pipeline", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add proffesor-for-testing/agentic-qe --skill validation-pipeline -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install proffesor-for-testing/agentic-qe validation-pipeline --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/proffesor-for-testing/agentic-qe.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/assets/skills/validation-pipeline .cursor/skills/validation-pipeline && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "validation-pipeline" agent skill from https://github.com/proffesor-for-testing/agentic-qe/tree/main/assets/skills/validation-pipeline into .cursor/skills/validation-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validation-pipeline", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/proffesor-for-testing/agentic-qe.git --path assets/skills/validation-pipeline--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add proffesor-for-testing/agentic-qe --skill validation-pipeline -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install proffesor-for-testing/agentic-qe validation-pipeline --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/proffesor-for-testing/agentic-qe.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/assets/skills/validation-pipeline .gemini/skills/validation-pipeline && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "validation-pipeline" agent skill from https://github.com/proffesor-for-testing/agentic-qe/tree/main/assets/skills/validation-pipeline into .gemini/skills/validation-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validation-pipeline", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install proffesor-for-testing/agentic-qe validation-pipelineInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add proffesor-for-testing/agentic-qe --skill validation-pipeline -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/proffesor-for-testing/agentic-qe.git skills-src && mkdir -p .github/skills && cp -r skills-src/assets/skills/validation-pipeline .github/skills/validation-pipeline && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "validation-pipeline" agent skill from https://github.com/proffesor-for-testing/agentic-qe/tree/main/assets/skills/validation-pipeline into .github/skills/validation-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validation-pipeline", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add proffesor-for-testing/agentic-qe --skill validation-pipeline -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install proffesor-for-testing/agentic-qe validation-pipeline --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/proffesor-for-testing/agentic-qe.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/assets/skills/validation-pipeline .opencode/skills/validation-pipeline && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "validation-pipeline" agent skill from https://github.com/proffesor-for-testing/agentic-qe/tree/main/assets/skills/validation-pipeline into .opencode/skills/validation-pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validation-pipeline", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
validation-pipeline- GitHub stars
- 494
- Token cost
- ~1.6k tokens
- SKILL.md length
- 445 words
- Files
- 4 (incl. scripts)
- Skills in repo
- 95
- Repo updated
- First seen
- Licence
- MIT
At a glance
Runs multi-stage validation gates with per-step scoring, pass/fail verdicts, and aggregate quality reports.
- Works in 5 steps: Read the Target Document → Select Pipeline → Execute Pipeline → …
- Validating requirements
- SKILL.md covers Purpose, Activation, Quick Start and Workflow, plus 4 more sections
- Artifacts through structured gate enforcement before merge
What it does
Validation Pipeline is an agent skill from proffesor-for-testing/agentic-qe. Runs multi-stage validation gates with per-step scoring, pass/fail verdicts, and aggregate quality reports. Use when validating requirements, code, or artifacts through structured gate enforcement before merge or release.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts (for example `evals/validation-pipeline.yaml`, `schemas/output.json` and `scripts/validate-config.json`).
It sits in Product & Project Management. The repository describes itself as: Agentic QE Fleet is an open-source AI-powered QA/QE platform designed for use with Coding Agents (works best with Claude Code) featuring specialized agents and skills to support… The licence is MIT.
When your agent uses it
- Validating requirements
- Artifacts through structured gate enforcement before merge
Example prompts
- “/validation-pipeline”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 829d030. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/, which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Validation Pipeline loads about 1.6k tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 445 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from proffesor-for-testing/agentic-qe at commit 829d030, republished under its MIT licence (© proffesor-for-testing). 445 words, ~1,569 tokens.
Download SKILL.mdSave it as
.claude/skills/validation-pipeline/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- validation-pipeline
- description
- Runs multi-stage validation gates with per-step scoring, pass/fail verdicts, and aggregate quality reports. Use when validating requirements, code, or artifacts through structured gate enforcement before merge or release.
- trust_tier
- 3
- validation.schema_path
- schemas/output.json
- validation.validator_path
- scripts/validate-config.json
- validation.eval_path
- evals/validation-pipeline.yaml
Validation Pipeline
Purpose
Run structured validation pipelines that execute steps sequentially, enforce gates at blocking failures, and produce scored reports. Uses .claude/helpers/validation-pipeline.cjs with 13 requirements validation steps (BMAD-003).
Activation
- When validating requirements documents
- When running structured quality gates
- When assessing document completeness, testability, or traceability
- When invoked via
/validation-pipeline
Quick Start
# Validate a requirements document (all 13 steps)
/validation-pipeline requirements docs/requirements.md
# Validate with specific steps only
/validation-pipeline requirements docs/requirements.md --steps format-check,completeness-check,invest-criteria
# Continue past blocking failures
/validation-pipeline requirements docs/requirements.md --continue-on-failure
# Output as JSON
/validation-pipeline requirements docs/requirements.md --jsonWorkflow
Step 1: Read the Target Document
Read the file specified by the user. If no file is provided, ask for one.
Read the target document using the Read tool.
Store the content for pipeline execution.Step 2: Select Pipeline
Choose the appropriate pipeline based on the user's request:
| Pipeline | Steps | Use Case |
|---|---|---|
requirements | 13 | Requirements documents, PRDs, user stories |
Additional pipelines can be added to .claude/helpers/validation-pipeline.cjs.
Step 3: Execute Pipeline
The pipeline helper (.claude/helpers/validation-pipeline.cjs) handles execution:
- Sequential execution — steps run in order, each receiving results from prior steps
- Gate enforcement — blocking steps that fail halt the pipeline (unless
--continue-on-failure) - Per-step scoring — each step produces a 0-100 score with findings and evidence
- Weighted rollup — overall score uses category weights (format=10%, content=30%, quality=25%, traceability=20%, compliance=15%)
Requirements Pipeline Steps (13 total)
| # | Step ID | Category | Severity | What It Checks |
|---|---|---|---|---|
| 1 | format-check | format | blocking | Headings, required sections, document length |
| 2 | completeness-check | content | blocking | Required fields populated, acceptance criteria present |
| 3 | invest-criteria | quality | warning | Independent, Negotiable, Valuable, Estimable, Small, Testable |
| 4 | smart-acceptance | quality | warning | Specific, Measurable, Achievable, Relevant, Time-bound |
| 5 | testability-score | quality | warning | Can each requirement be tested? |
| 6 | vague-term-detection | content | info | Flags "should", "might", "various", "etc." |
| 7 | information-density | content | info | Every sentence carries weight, no filler |
| 8 | traceability-check | traceability | warning | Requirements-to-tests mapping exists |
| 9 | implementation-leakage | quality | warning | Requirements don't prescribe implementation |
| 10 | domain-compliance | compliance | info | Alignment with domain model |
| 11 | dependency-analysis | traceability | info | Cross-requirement dependencies identified |
| 12 | bdd-scenario-generation | quality | warning | Can generate Given/When/Then for each requirement |
| 13 | holistic-quality | compliance | blocking | Overall coherence, no contradictions |
Show full SKILL.md (154 more words)Show less
Step 4: Report Results
Format the pipeline result as a structured report:
# Validation Report: Requirements Pipeline
**Overall**: PASS/FAIL/WARN | **Score**: 85/100 | **Duration**: 42ms
## Step Results
| # | Step | Status | Score | Findings | Duration |
|---|------|--------|-------|----------|----------|
| 1 | Format Check | PASS | 100 | 0 | 2ms |
| 2 | Completeness | WARN | 60 | 2 | 5ms |
...
## Blockers
- (blocking findings listed here)
## All Findings
- [HIGH] Missing acceptance criteria: Requirement US-104 has no AC
- [MEDIUM] Vague term: "should" used 5 times without specifics
...Step 5: Record Learning
After pipeline execution, record the outcome for learning:
// Store validation pattern
memory store --namespace validation-pipeline --key "req-validation-{timestamp}" --value "{score, findings_count, halted}"Parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
pipeline | string | requirements | Pipeline type to run |
file | string | required | Path to document to validate |
--steps | string | all | Comma-separated step IDs to run (e.g., format-check,completeness-check) |
--continue-on-failure | boolean | false | Skip blocking gates |
--json | boolean | false | Output as JSON instead of markdown |
--metadata | object | {} | Additional context for steps |
Integration Points
- qe-requirements-validator agent — delegates structured validation to this pipeline
- qe-quality-gate agent — uses pipeline for gate evaluation
- YAML Pipelines — can invoke validation steps as workflow actions
- MCP — accessible via
pipeline_validatetool
Output Schema
The pipeline produces a PipelineResult object (see schemas/output.json):
{
pipelineId: string;
pipelineName: string;
overall: 'pass' | 'fail' | 'warn';
score: number; // 0-100 weighted average
steps: StepResult[]; // per-step details
blockers: Finding[]; // blocking findings
halted: boolean;
haltedAt?: string; // step ID where halted
totalDuration: number;
timestamp: string;
}Error Handling
- Step throws exception — captured as a FAIL with critical finding, pipeline continues or halts per severity
- File not found — report error, do not run pipeline
- Empty document — format-check step will catch this as a blocking failure
© proffesor-for-testing, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (scripts) in assets/skills/validation-pipeline of proffesor-for-testing/agentic-qe.
- SKILL.md
- evals/validation-pipeline.yaml
- schemas/output.json
- scripts/validate-config.json
Open the folder on GitHubat commit 829d030
Compare with similar skills
Validation Pipeline next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Validation Pipeline this skillproffesor-for-testing/agentic-qe | 494 | — | ~1.6k | Automated safety check: Pass | MIT | |
| User Story Writerdeanpeters/Product-Manager-Skills | 7.2k | 2 repos | ~2.9k | Automated safety check: Pass | Custom licence | |
| Game Changing FeaturesopenstatusHQ/data-table-filters | 2.3k | 3 repos | ~2.1k | Automated safety check: Pass | MIT | |
| CCPM Project Managementautomazeio/ccpm | 8.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Convex Create Componentspokvulcan/poker-planning | 114 | 8 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Self Improving Agentfarm-fe/farm | 5.6k | 2 repos | ~3.3k | Automated safety check: Notes | MIT |
Similar skills
Game Changing Features
openstatusHQ/data-table-filters
Find 10x product opportunities and high-leverage improvements.
CCPM Project Management
automazeio/ccpm
Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.
Convex Create Component
spokvulcan/poker-planning
Builds reusable Convex components with isolated tables and app-facing APIs.
Self Improving Agent
farm-fe/farm
A universal self-improving agent that learns from ALL skill experiences.
Weekly Engineering Retro
garrytan/gstack
Builds a weekly engineering retrospective from git history: commit counts, per-person contributions, work patterns and code quality numbers over a chosen window.
More from proffesor-for-testing/agentic-qe
All 95 skills in this repoContract Testing
proffesor-for-testing/agentic-qe
Consumer-driven contract testing for microservices using Pact, schema validation, API versioning, and backward compatibility testing.
Mutation Testing
proffesor-for-testing/agentic-qe
Test quality validation through mutation testing, assessing test suite effectiveness by introducing code mutations and measuring kill rate.
Performance Testing
proffesor-for-testing/agentic-qe
Profiles application performance under load using k6, Artillery, or JMeter to measure latency, throughput, and error rates.
Code Review Quality
proffesor-for-testing/agentic-qe
Conduct context-driven code reviews focusing on quality, testability, and maintainability.
Security Testing
proffesor-for-testing/agentic-qe
Scans for security vulnerabilities including XSS, SQL injection, CSRF, and auth flaws using OWASP Top 10 methodology.
Database Testing
proffesor-for-testing/agentic-qe
Database schema validation, data integrity testing, migration testing, transaction isolation, and query performance.
Related
Categories
Questions about Validation Pipeline
What does Validation Pipeline do?
Runs multi-stage validation gates with per-step scoring, pass/fail verdicts, and aggregate quality reports. Validation Pipeline is an agent skill from proffesor-for-testing/agentic-qe. Runs multi-stage validation gates with per-step scoring, pass/fail verdicts, and aggregate quality reports.
When should I use Validation Pipeline?
Validation Pipeline fits situations like: validating requirements; artifacts through structured gate enforcement before merge.
How do I install Validation Pipeline in Claude Code?
Run `npx skills add proffesor-for-testing/agentic-qe --skill validation-pipeline -a claude-code`. Or copy the skill folder (assets/skills/validation-pipeline in proffesor-for-testing/agentic-qe) into .claude/skills/validation-pipeline in your project. Claude Code loads it when a task matches its description.
How do I install Validation Pipeline in Codex?
Run `npx skills add proffesor-for-testing/agentic-qe --skill validation-pipeline -a codex`. Or copy the skill folder (assets/skills/validation-pipeline in proffesor-for-testing/agentic-qe) into .agents/skills/validation-pipeline in your project. Codex loads it when a task matches its description.
Can I use Validation Pipeline in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add proffesor-for-testing/agentic-qe --skill validation-pipeline -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/validation-pipeline, .gemini/skills/validation-pipeline, .github/skills/validation-pipeline and .opencode/skills/validation-pipeline in your project.
What does Validation Pipeline need to run?
SKILL.md names no scripts, command-line tools or credentials: Validation Pipeline is instructions for the agent only.
Does Validation Pipeline access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Validation Pipeline safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Validation Pipeline use?
Validation Pipeline is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Validation Pipeline use?
About 1.6k tokens (SKILL.md is roughly 6.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Validation Pipeline?
Skills that share tags, products or a category with Validation Pipeline: User Story Writer (deanpeters/Product-Manager-Skills, 7.2k stars), Game Changing Features (openstatusHQ/data-table-filters, 2.3k stars), CCPM Project Management (automazeio/ccpm, 8.4k stars) and Convex Create Component (spokvulcan/poker-planning, 114 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Validation Pipeline?
proffesor-for-testing (a GitHub user) maintains it in proffesor-for-testing/agentic-qe, which has 494 GitHub stars. The repository holds 95 skills in this directory. The repository was last updated on October 4, 2026.
Source: proffesor-for-testing/agentic-qe on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.