🔌

create-qa-list

🔌Plugin

2ykwang/agent-skills

Installation

Add marketplace in Claude Code:

$/plugin marketplace add 2ykwang/agent-skills

Step 2. Install plugin:

$/plugin install create-qa-list@2ykwang-agent-skills

What it does

Turn code, specs, a PR, or the current conversation into a QA test-case list a non-developer can read and run, exported as CSV, a shareable HTML report, or both. Trigger when the user wants QA test cases, a test plan, a QA checklist, or a test-case CSV/HTML (e.g. "write test cases for this", "make a QA list"). Output uses behavior-and-scenario language, never code symbols like function names or file paths. Not for writing or running automated test code (pytest/jest), code review, or test-strategy docs.

🏪

Part of

2ykwang/agent-skills

productivity

AddedJul 14, 2026

View on GitHub Back to Plugins

More from this repository10

🎯

html-visual🎯Skill

Agent skills including html-visual for generating interactive single-file HTML visualizations (UI mockups, ERDs, flowcharts, data charts) and ralph-loop-template for iteration checklists.

🎯

write-pr🎯Skill

Agent skills including html-visual for generating interactive single-file HTML visualizations (UI mockups, ERDs, flowcharts, data charts) and ralph-loop-template for iteration checklists.

🎯

ralph-loop-template🎯Skill

A Ralph Loop template skill for autonomous agent iteration, part of an agent skills collection that includes HTML visualization and interactive single-file generation capabilities.

Skill

Skill

django-ticket-triage🎯Skill

Skill

🎯

django-triage🎯Skill

Skill

🔌

ralph-loop-template🔌Plugin

Generates iterable checklist PROMPT files for Ralph Loop from plan files or current context, and provides the /ralph-loop execution command.

🔌

write-pr🔌Plugin

Analyzes git diff and commit history to write PR title and description based on the project's PR template.

🔌

worth-building🔌Plugin

Decide how elaborate to build something (simple vs. robust) and return a concrete, PoC-shaped proposal at that level — not over- or under-engineered, but right-sized. Use whenever someone is building something and the investment level is unclear: "quick or proper?", "MVP vs. real product", "is this over-engineering?", "how should I approach X?", "quick script vs. robust system", "how much architecture?", "how much do I build here?". Fires even without "poc" or "right-size" — any time effort and complexity of what to build are being weighed.