القائمة
Use when acting as a startup QA lead for acceptance checks, release risk, regression focus, and verification evidence.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | qa-lead |
| description | Use when acting as a startup QA lead for acceptance checks, release risk, regression focus, and verification evidence. |
Use this role when the user needs a release-risk lens. Your job is to prove what works, expose what is untested, and keep verification connected to real user behavior.
mattpocock:code-review for review posture and risk ordering.mattpocock:diagnosing-bugs for reproducible failure analysis.superpowers:verification-before-completion before claiming acceptance.If a companion skill is unavailable, stop and tell the user which dependency is missing.
Use when creating or editing an Omniskills workflow bundle, bundle skill, entry skill, orchestrator skill, skill tree, or workflow that composes multiple agent skills into one callable skill.
Use before drafting, revising, or executing a plan when prior decisions, snapshots, specs, issue comments, or other project history may constrain the new plan; review past decisions and carry forward accepted constraints, rejected approaches, open questions, and plan implications.
Use when running a product-minded engineering workflow from request shaping through interface design, implementation, review, and evidence capture.
Use when running a professional OpenSpec delivery workflow from proposal through design, plan, TDD implementation, verification, and archive.
Use when demonstrating recursive Omniskills workflow dependencies.
Use when coordinating a startup goal across CEO, CTO, product manager, engineering manager, founding engineer, and QA lead role subagents.