Parallel DAG-plan implementation skill. Reads a v-planning plan directory (root.md + step- .md files), topologically schedules ready steps, and fans them out as parallel sub-agents. Use whenever the user invokes /v-implement, points at a plan directory produced by /v-plan, or asks to "run the parallel plan"…
Vertical / parallel implementation planning skill. Creates DAG-structured plan directories where each step is an independent, QA-able vertical slice that sub-agents can pick up and implement in parallel. Use whenever the user wants a plan that fans out (multiple independent features), invokes /v-plan, or asks for a…
Personal knowledge management expert for the brain CLI. Use when users want to capture notes, search their knowledge base, or manage their second brain.
Simplified CLI-integrated plugin for E2E testing with essential slash commands plus dynamic API CLI workflows (qa-use api). Provides AI-first feature verification, browser automation, and test management. All CLI operations documented in SKILL.md and accessible via qa-use docs for harness compatibility.
Autonomous browsing agent for multi-step web tasks. Use when: (1) User describes a browsing goal (e.g., "find the pricing page"), (2) Complex navigation requires multiple snapshot-action cycles, (3) AI-powered element discovery is needed.
Record browser interactions and generate test definitions. Use when: (1) By feature-verify skill after exploration to generate test YAML, (2) By test-authoring skill for assisted test creation, (3) By user for "record this flow" requests.
Single agent that verifies all PR frontend changes. Use when: (1) verify-pr command is invoked, (2) Complete PR verification with visual report is needed, (3) Running verification in background while user continues working.
Generate test steps from natural language descriptions. Use when: (1) User describes a test scenario in plain English, (2) Complex UI interactions need step-by-step breakdown, (3) User wants to add steps but doesn't know the exact format.
Deep analysis of E2E test failures and results. Use when: (1) A test has failed and needs root cause analysis, (2) User wants to understand why a step failed, (3) Complex multi-step failures need investigation.