Alternatives
phoenix-verification-matrix alternatives for AI agents.
Compare similar skills by workflow fit, trust score, quality, GitHub adoption, maintenance, and install readiness.
Current skill
phoenix-verification-matrix
Role 08 of the Phoenix Security spec pipeline. Maps every MUST/MUST NOT to a concrete proof method using Phoenix's proof type hierarchy: unit-test, integration-test, contract-test, static-analysis, infra-check, load-test, manual-review. Enforces that security requirements use static-analysis + unit-test minimum, multi-tenancy requirements use integration-test, AI agent requirements use manual-review + unit-test, and all API contracts use contract-test. Includes negative test cases for auth, tenant isolation, and input validation requirements. Use this skill when you need to verify a spec is provable end-to-end, when someone says "how do we test this", "map the proofs", "verification plan", "how do we know this works", or "create the test matrix". Always run after phoenix-contract-architect and before phoenix-batch-planner.