pitfall-verificationlisted

# Pitfall verification Use this skill after finishing any PRD, spec, plan, or code artifact — before declaring the work done. It is NOT a generic review. It is a targeted check that *typical pitfalls for this type of artifact, in this domain, do not apply here*. Invoke with: `/superpowers-gstack:pitfall-verification` ## When to invoke Automatically after completing: - A PRD, spec, or design document - An implementation plan - A code change (feature, refactor, bug fix) - Output from `writing-specs`, `writing-plans`, `executing-plans`, `verification-before-completion`, or any GStack planning/review skill Run **twice max**. Two rounds catch almost everything; a third round has sharply diminishing returns. ## Sequence 1. **Self-check first** (~30 seconds): placeholders, scope drift, internal consistency, ambiguity. This is the standard sanity pass. Fix anything obvious. 2. **Pitfall verification** (this skill): targeted check for the pitfalls below, adapted to the artifact type and domain. Do not skip step 1 — self-check and pitfall verification are different lenses. ## Pitfall lists per artifact type These are **starting points, not exhaustive checklists**. Always ask: *what typically goes wrong with this kind of artifact, in this specific domain?* Infer additional pitfalls from the actual code/spec under review. ### PRD - Unclear user story or missing success metric - Hidden stakeholder assumptions (who signs off? who blocks?) - Unspecified non-functional requireme