SP

Enforces strict QA validation and spec compliance for story implementations.

Install

mkdir -p .claude/skills/spec-driven-qa && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13015" && unzip -o skill.zip -d .claude/skills/spec-driven-qa && rm skill.zip

Installs to .claude/skills/spec-driven-qa

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Validates code quality through spec-driven QA validation with structural anti-skip enforcement. Replicates all 6 phases of the DevForgeAI QA workflow using the Execute-Verify-Gate pattern at every step. Designed to prevent token optimization bias through lean orchestration, fresh-context subagent delegation, and binary CLI gate enforcement. Enforces test coverage (95%/85%/80% strict thresholds), detects anti-patterns, validates spec compliance, and analyzes code quality metrics. Use when validating implementations, ensuring quality standards, or preparing for release. Always use this skill when the user runs /qa or mentions QA validation, quality checks, or coverage analysis.
684 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Advanced

Key capabilities

  • Validate code quality through spec-driven QA
  • Enforce coverage thresholds (95%/85%/80%)
  • Detect anti-patterns in code
  • Validate spec compliance (AC/API/NFR)
  • Analyze code quality metrics

How it works

The skill executes a 6-phase QA workflow, enforcing coverage, anti-pattern detection, and spec compliance using an Execute-Verify-Gate pattern at each step.

Inputs & outputs

You give it
Story ID and validation mode (light or deep)
You get back
QA reports (`.md`), gaps (`.json`), and recommendations (`.md`)

When to use spec-driven-qa

  • Running QA validation
  • Checking test coverage
  • Validating spec compliance
  • Detecting anti-patterns

About spec-driven-qa

Executes a comprehensive QA workflow that includes coverage analysis, anti-pattern detection, and spec compliance checks. It enforces binary CLI gates to ensure quality standards are met before release.

>

When not to use it

  • When encountering obstacles that would lead to bypassing safety checks
  • When attempting to manually invoke hook scripts to bypass conviction gates
  • When writing placeholder content to satisfy substance checks

Limitations

  • Does not bypass conviction gates by manually invoking hook scripts
  • Does not `file edit` subagent worklog files post-hoc
  • Does not write placeholder content to satisfy substance checks

How it compares

This skill provides a structured, enforced QA workflow with binary CLI gates, contrasting with less rigorous or manual quality assurance processes.

Compared to similar skills

spec-driven-qa side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
spec-driven-qa (this skill)01moReviewAdvanced
verify66moNo flagsBeginner
code-change-verification44moReviewBeginner
springboot-verification44moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry