Skip to content
Skills Library
Programming · Review & audit

quality-validation

/quality-validation

Score ResearchPacks (>=80) and Implementation Plans (>=85) against quality gates. TRIGGER when: gating research or a plan before implementation. SKIP: writing or running tests (use testing-strategy); security threat review (use security-review-checklists); verifying finished work by executing it (use verification-before-completion).

Repository
scaffolding ↗
Licence
MIT
Last repository change
27.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Score ResearchPacks (>=80) and Implementation Plans (>=85) against quality gates. TRIGGER when: gating research or a plan before implementation. SKIP: writing or running tests (use testing-strategy); security threat review (use security-review-checklists); verifying finished work by executing it (use verification-before-completion).

Original author description

Score ResearchPacks (>=80) and Implementation Plans (>=85) against quality gates. TRIGGER when: gating research or a plan before implementation. SKIP: writing or running tests (use testing-strategy); security threat review (use security-review-checklists); verifying finished work by executing it (use verification-before-completion).

How it works

  1. Auto-Invoke Triggers
  2. Quality Gates
  3. ResearchPack Validation (100 pts, pass: 80)
  4. Implementation Plan Validation (100 pts, pass: 85)
  5. Validation Commands
  6. Common Failures
  7. Validation Output Format
Original SKILL.md headings · 129 lines, 584 words
SKILL.md preview
---
name: quality-validation
description: "Score ResearchPacks (>=80) and Implementation Plans (>=85) against quality gates. TRIGGER when: gating research or a plan before implementation. SKIP: writing or running tests (use testing-strategy); security threat review (use security-review-checklists); verifying finished work by executing it (use verification-before-completion)."
---

# Quality Validation Skill

Systematic validation ensuring ResearchPacks and Implementation Plans meet quality standards before implementation.

## Auto-Invoke Triggers

- ResearchPack completion requires validation
- Implementation Plan requires validation before coding
- User requests quality check
- Proceeding to next workflow phase (quality gate)

## Quality Gates

### Gate 1: Research → Planning
- **Trigger**: ResearchPack completion
- **Pass**: Score ≥ 80
- **Fail**: Block, return defects

### Gate 2: Planning → Implementation
- **Trigger**: Implementation Plan completion
- **Pass**: Score ≥ 85 AND APIs match
- **Fail**: Block, return defects
- Note: the ≥ 85 plan gate / design review may run on the opus tier (architect/analyst on `model: opus`, `effort: high`) for higher rigor. See `docs/model-tiers.md`.

### Gate 3: Implementation → Completion
- **Trigger**: Code complete
- **Pass**: your project's validate/lint/test command passes (e.g. `npm run validate`, `pytest`, `make check`, `cargo test`)
- **Fail**: Trigger self-correction (max 3 attempts)

## ResearchPack Validation (100 pts, pass: 80)

### Completeness (40 pts)
- Library/API with version: 10 pts
- 3+ key APIs documented: 10 pts
- Setup/configuration steps: 10 pts
- 1+ complete code examples: 10 pts

### Accuracy (30 pts)
- API signatures match official docs: 15 pts
- Version numbers correct: 5 pts
- All URLs valid, official sources: 10 pts

### Citation (20 pts)
- Every API has source URL: 10 pts
- Version/section references: 5 pts
- Confidence level stated: 5 pts

### Actionability (10 pts)
- Implementation checklist: 5 pts
- Open questions identified: 5 pts

## Implementation Plan Validation (100 pts, pass: 85)

### Completeness (35 pts)
- All file changes listed: 10 pts
- Step-by-step sequence: 10 pts
- Verification per step: 10 pts
- Test plan included: 5 pts

### Safety (30 pts)
- Rollback plan complete: 15 pts
- Risk assessment (3+ risks): 10 pts
- Minimal changes: 5 pts

### Clarity (20 pts)
- Actionable steps: 10 pts
- Success criteria defined: 5 pts
- Time estimates: 5 pts

### Alignment (15 pts)
- Plan matches ResearchPack: 10 pts
- Addresses all requirements: 5 pts

## Validation Commands

Run your project's own validate/lint/type-check/test command at the completion
gate. The exact command depends on your stack — substitute the equivalents below.

| Step | Generic intent | Example (Node/TS) | Example (Python) |
|------|----------------|-------------------|------------------|
| Type check | Static type safety | `npm run type-check` | `mypy .` |
| Lint | Style / static analysis | `npm run lint` | `ruff check .` |
| Build | Compile / package | `npm run build` | `python -m build` |
| Tests | Behavioral verification | `npm test` | `pytest` |
| Full gate | One command runs all | `npm run validate` | `make check` |

```bash
# Example (Node/TypeScript): full validation
npm run validate

# Example (Python): full validation
pytest && ruff check . && mypy .
```

## Common Failures

| Failure | Description |
|---------|-------------|
| Hallucinated APIs | APIs not in official docs |
| Version mismatch | Wrong version in research |
| Missing citations | No source URLs |
| No rollback plan | Missing reversion procedure |
| Ambiguous steps | Non-actionable instructions |
| API misalignment | Plan uses undocumented APIs |

## Validation Output Format

```markdown
## Validation Report

**Artifact**: [ResearchPack|ImplementationPlan]
**Score**: XX/100
**Result**: [PASS|FAIL]

### Scoring Breakdown
- Completeness: XX/40
- Accuracy: XX/30
- Citation: XX/20
- Actionability: XX/10

### Defects Found
1. [Defect description]
2. [Defect description]

### Recommendations
- [Fix suggestion]
```

Versions

RepositoryScoreLicence
This page · komluk/scaffolding100MIT
microsoft/aibast-agents-library85MIT

Database snapshot: 13.11.2026 · package version bfa5e3f1d235 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90verification-before-completion
    Verify claims by executing, not asserting, before declaring work done. TRIGGER when: about to report a task complete, confirming a fix/build/deploy works, or delegating work to another agent or tool. SKIP: scoring research/plan quality pre-implementation (use…
  • 100review-plan
    Use after writing implementation plans (superpowers:writing-plans output) or when the user says "review plan", "check my plan", "sanity check the plan", "validate plan", "review before executing". Also use before superpowers:executing-plans if a plan has not been reviewed yet.
  • 100quality-review
    Use when reviewing code changes against AGENTS.md implementation quality standards, or when asked to do an implementation quality review
  • 95verification-loop
    Comprehensive 6-check verification framework for validating implementation quality across build, types, lint, tests, security, and diff review. This skill ensures code meets all quality gates before phase completion. Triggers on "verify implementation", "run verification",…
  • 100writing-plans
    Use when you have a spec, design doc, or requirements and need a detailed implementation plan before coding. Triggers: 'write a plan', 'create implementation plan', 'plan this out', 'break this down into steps', 'convert design to tasks', 'implementation order'. Also invoked by…
  • 100testing-strategy
    Test pyramid, coverage targets, and unit/integration/E2E patterns. TRIGGER when: planning tests, writing test code, or reviewing coverage. SKIP: quality-gate scoring of plans (use quality-validation); root-causing a failing test (use systematic-debugging); proving a fix works…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.