vibe-qalisted

# Vibe QA ## Purpose Review the project for readiness before handoff. This skill exists to determine whether the system has earned the right to move forward. It should verify that: - major risks are visible - measurement remains credible - execution detail is coherent enough - unresolved assumptions are still visible - the system is not pretending readiness it has not earned ## When to Use Use this skill when: - detail design has been completed - the project has trusted blueprint and detail artifacts - the system needs a formal readiness review - the next decision is whether the project may move toward handoff ## When Not to Use Do not use this skill when: - no trusted project state exists - detail work is incomplete - the task is still planning, research, blueprinting, or detail design - the request is only to inspect status or resume context - the system is attempting to use QA as a shortcut around missing upstream artifacts ## Required Context Minimum required context: - technical detail - validation plan - execution notes - architecture baseline - assumptions log Helpful optional context: - decision records - analytics outline - prior gate results - visible mitigation notes - known tradeoffs If required context is missing, this skill must halt or surface the gap clearly. ## Assumptions Rules This skill may use limited assumptions only when they do not fabricate readiness or hide blocking risk. Allowed assumptions: - a neutral QA reporting structure - pr