qa-start
把多个 QA 步骤串成一次可重复的启动流程，适合新项目或无 QA 团队。
按顺序引导完成 QA 启动流程，生成上下文、策略和测试计划文件。
帮你在一个完全没 QA 的项目里把质量工作从头搭起来，按顺序产出项目上下文、测试策略和第一版测试计划文件。适合在新项目启动或团队说要“从零做 QA”时使用，避免没想清要测什么就急着写测试。特别之处是把 qa-project-context、test-strategy、test-planning 串成一个有向流程，结束时还能指向自动化落地。
▸ 展开 SKILL.md 英文原文
Sequenced launcher that bootstraps QA on a project with no QA in place. Chains qa-project-context → test-strategy → test-planning in one guided run, then points you at automation. Use when: "set up QA on a new project," "QA from scratch," "no QA exists yet," "/qa-start." Not for: onboarding a QA engineer to an existing team with existing tests — use qa-project-bootstrap. Not for: "which skill do I use" with no clear match — use qa-do. Related: qa-project-context, test-strategy, test-planning, qa-project-bootstrap, qa-do.
帮我安装这个 skill：https://raw.githubusercontent.com/petrkindlmann/qa-skills/main/skills/qa-start/SKILL.mdcurl -fsSL "https://raw.githubusercontent.com/petrkindlmann/qa-skills/main/skills/qa-start/SKILL.md"<objective> A sequenced launcher for bootstrapping QA where none exists. It contains no QA guidance itself — it chains three skills in the correct order so engineers don't jump to writing tests before deciding what to test or why. Run `qa-project-context` → `test-strategy` → `test-planning` and you end with a context file, a strategy document, and a first test plan: a complete QA foundation. </objective> ## When to Use This Reach for `qa-start` whenever the answer to "where do we start with QA?" is unclear and no QA foundation exists yet: - A brand-new project with no test infrastructure. - Joining an existing codebase that has **no QA setup at all** — old code, but quality work was never