pitfall-verification

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.

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.

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.

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.

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.