pitfall-verification

Verify artifact-specific pitfalls across PRDs, specs, plans, and code.

2|1|Updated Apr 6, 2026

Search Tags:#quality-gate #risk-assessment #code-review #prd-review #spec-verification #pitfall-verification #artifact-quality

Ready to run

npx skills add https://github.com/Paretofilm/superpowers-gstack --skill pitfall-verification

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pitfall-verification
Source: https://github.com/Paretofilm/superpowers-gstack/tree/main/skills/pitfall-verification
Command: npx skills add https://github.com/Paretofilm/superpowers-gstack --skill pitfall-verification

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use after completing any PRD, spec, plan, or code implementation — verifies that artifact-specific pitfalls (security, idempotency, integration contracts, edge cases, LLM output) do not apply before declaring work done. Two rounds max.

Core Features & Use Cases

Self-check pass to surface placeholders, scope drift, internal consistency issues, and ambiguity.
Targeted pitfall verification across artifact types (PRD, spec/plan, code) with a two-round approach.
Actionable verdicts and remediation guidance before handoff.

Quick Start

Run pitfall verification on the latest artifact (PRD, spec, plan, or code) to ensure all domain-specific pitfalls are addressed.

Frequently Asked Questions about pitfall-verification

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I verify code and spec artifacts for common pitfalls before handoff?▼

Pitfall verification identifies artifact-specific issues like security gaps and integration contracts across PRDs, specs, plans, or code. It applies a two-round self-check process to surface placeholders and scope drift before declaring work done.

What is the best way to check a PRD for scope drift and integration contract risks?▼

A targeted pitfall verification pass checks PRDs for internal consistency, ambiguity, and integration contracts. It runs a self-check to surface placeholders and scope drift, ensuring requirements are solid before implementation begins.

Does pitfall verification work on both planning documents and implemented code?▼

Yes, pitfall verification works across PRD, spec, plan, and code artifacts. It targets domain-specific risks like idempotency in code and scope drift in planning, applying a consistent two-round verification approach before handoff.

How do I ensure idempotency and edge cases are addressed after code implementation?▼

Run a post-implementation pitfall verification to check code artifacts for idempotency, edge cases, and security. It provides actionable remediation guidance and a final verdict to guide safe handoff after two verification rounds.

What limitations does the two-round pitfall verification process have?▼

The pitfall verification process is capped at two rounds maximum. It focuses on surfacing specific risks like LLM output issues and edge cases, delivering a final verdict rather than performing continuous or open-ended iterative testing.