Validate spec and plan adversarially
superpower-validateworkflowsetup L3★0
CDDing/dding-marketplace ↗What it does
Validate spec/plan against requirements
Best for
Spec/plan validation before build when requirements are vague or dependencies cross multiple systems.
Inputs
- · args envelope (task/contract/spec path)
- · context files if provided
Outputs
- · structured result per phase schema
- · markdown report/findings
Requires
- · MCP tools (WebFetch/Playwright/etc)
Preconditions
- · args envelope valid
- · required paths accessible
Failure modes
- · Refutation quorum failure (false positive)
- · Finding threshold not met
Trust signals
- · Canonical reference implementation
- · Phase gates documented
- · Error handling guards