Back to Details

qa-start

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
<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>
<objective> 一款用于在无QA基础的场景下搭建QA体系的序列启动工具。它本身不包含QA指导内容，而是按正确顺序串联三个技能，避免工程师在确定测试内容和测试原因之前就直接开始编写测试用例。运行`qa-project-context` → `test-strategy` → `test-planning`后，你将得到一份上下文文件、一份策略文档和第一份测试计划，构成完整的QA基础。 </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 formalized. Still 
    qa-start
    , not 
    qa-project-bootstrap
    (that one is for joining a team that already has tests).
  • Rebooting QA after neglect — tests deleted, coverage collapsed, no strategy. You are rebooting QA from the foundation up.
If the codebase already has a real test suite and you are a QA engineer ramping onto the team, use 
qa-project-bootstrap
instead.
当你对“我们该从哪里开始做QA？”这个问题没有明确答案，且项目尚无任何QA基础时，请使用
qa-start
：
  • 全新项目，无任何测试基础设施。
  • 加入一个完全没有QA设置的现有代码库——代码是旧的，但从未正式开展过质量工作。这种情况仍需使用
    qa-start
    ，而非
    qa-project-bootstrap
    （后者适用于加入已有测试体系的团队）。
  • 在QA工作被忽视后重启——测试用例已删除、覆盖率骤降、无测试策略。你需要从基础开始重启QA工作。
如果代码库已有成熟的测试套件，且你是刚加入团队的QA工程师，请改用
qa-project-bootstrap
。

Quick Route

快速路径

Pick your entry point — skip any step whose artifact already exists.
SituationStart at
No QA at all (no context file, no strategy, no plan)Step 1
.agents/qa-project-context.md
already populated		Skip Step 1 — invoke 
test-strategy
(Step 2)
Context file AND strategy document both existSkip Steps 1 and 2 — invoke 
test-planning
(Step 3)
All three done — what next?After Step 3
A QA engineer ramping onto an existing team with existing testsNot this skill — see 
qa-project-bootstrap
选择你的起始点——跳过已有产出物的步骤。
场景起始步骤
完全无QA（无上下文文件、无策略、无计划）步骤1
.agents/qa-project-context.md
已填充完成		跳过步骤1——调用
test-strategy
（步骤2）
上下文文件和策略文档均已存在跳过步骤1和2——调用
test-planning
（步骤3）
三个步骤均已完成——下一步做什么？步骤3之后
QA工程师加入已有测试体系的团队并熟悉工作不适用本技能——请查看
qa-project-bootstrap

Step 1: Capture Project Context

步骤1：捕获项目上下文

Skill: 
qa-project-context
Creates 
.agents/qa-project-context.md
in your project root. That file records your tech stack, test frameworks, CI/CD pipeline, environments, coverage goals, risk areas, and team structure. Every later skill reads it, so it never asks you the same questions twice.
What to do: Invoke 
qa-project-context
and work through its discovery questions. The skill walks each section interactively, discovers what it can from the repo, and writes the file.
Done when: 
.agents/qa-project-context.md
exists in your project root with all sections filled in. It is the source of truth for everything that follows.
技能： 
qa-project-context
在项目根目录创建
.agents/qa-project-context.md
文件。该文件记录你的技术栈、测试框架、CI/CD流水线、环境、覆盖率目标、风险区域和团队结构。后续所有技能都会读取该文件，因此不会重复询问相同问题。
操作方法： 调用
qa-project-context
并完成其探索性问题。该技能会交互式引导你完成每个部分，从代码库中自动发现相关信息并写入文件。
完成标志： 项目根目录下存在
.agents/qa-project-context.md
文件，且所有部分均已填写完整。它是后续所有工作的事实依据。

Step 2: Create the Test Strategy

步骤2：创建测试策略

Skill: 
test-strategy
Produces a strategy document defining how the project approaches quality: the test pyramid (what proportion of unit, integration, and E2E tests fits your product), entry and exit criteria, tool selection, environment coverage, and quality gates for CI and release.
What to do: Invoke 
test-strategy
once Step 1 is complete. It reads the context file automatically and will not re-ask anything answered there.
Done when: You have a strategy document (e.g. 
strategy.md
) covering test-pyramid rationale, tool choices with justification, quality gates for CI and release, and entry/exit criteria per test type. One page of clear decisions beats a sprawling template.
技能： 
test-strategy
生成一份定义项目质量管控方法的策略文档：测试金字塔（单元测试、集成测试和E2E测试的占比如何适配你的产品）、准入和准出标准、工具选择、环境覆盖范围，以及CI和发布环节的质量门控。
操作方法： 完成步骤1后调用
test-strategy
。它会自动读取上下文文件，不会重复询问已在其中回答过的问题。
完成标志： 你拥有一份策略文档（例如
strategy.md
），涵盖测试金字塔的设计依据、工具选择及理由、CI和发布环节的质量门控，以及各测试类型的准入/准出标准。清晰的一页决策胜过冗长的模板。

Step 3: Build the First Test Plan

步骤3：制定第一份测试计划

Skill: 
test-planning
Translates the strategy into an actionable plan for the first sprint or release. Maps features to test cases, assigns effort, and decides what gets covered first versus deferred.
What to do: Invoke 
test-planning
after Step 2. It consumes the strategy from Step 2 and the context from Step 1. Provide the feature list or sprint scope when prompted.
Done when: You have a test plan (e.g. 
plan.md
) with features mapped to test cases, coverage priorities set, effort estimated, and scope boundaries clear. This is the artifact your team executes against.
技能： 
test-planning
将测试策略转化为适用于首个迭代或版本的可执行计划。将功能映射到测试用例，评估工作量，并确定优先覆盖内容和延后内容。
操作方法： 完成步骤2后调用
test-planning
。它会使用步骤2的策略和步骤1的上下文信息。在提示时提供功能列表或迭代范围。
完成标志： 你拥有一份测试计划（例如
plan.md
），其中包含功能到测试用例的映射、覆盖优先级设置、工作量评估和范围边界定义。这是团队执行测试工作的依据。

After Step 3

步骤3之后

You now hold the foundation: context, strategy, and a first plan. Next actions depend on your stack — this launcher is not the final step.
  • First automated tests: Use 
    playwright-automation
    or 
    cypress-automation
    to write the first E2E tests against your highest-risk flows.
  • CI integration: Use 
    ci-cd-integration
    to get tests running on every pull request.
  • Tracking quality: Use 
    qa-metrics
    once the suite runs to define what health looks like and how to measure it over time.
你现在已拥有QA基础：上下文、策略和第一份计划。后续操作取决于你的技术栈——本启动工具并非最终步骤。
  • 编写首批自动化测试： 使用
    playwright-automation
    或
    cypress-automation
    针对高风险流程编写首批E2E测试。
  • CI集成： 使用
    ci-cd-integration
    实现每次拉取请求时自动运行测试。
  • 质量跟踪： 测试套件运行后，使用
    qa-metrics
    定义健康指标及长期测量方法。

qa-start vs qa-project-bootstrap vs qa-do

qa-start vs qa-project-bootstrap vs qa-do

The single most common routing confusion, answered in one place:
  • qa-start
     — bootstrap QA where none exists. New project, or QA was deleted and you are rebooting it. Sequence: context → strategy → first plan. Output is the QA foundation.
  • qa-project-bootstrap
     — a 30-day ramp for a QA engineer joining an existing team with existing tests. Covers team processes, onboarding timeline, and an audit of the test suite already in place. Use it after a foundation exists, not to create one.
  • qa-do
     — last-resort router for "which skill do I use?" when nothing clearly matches. If you already know you have no QA, skip it and run 
    qa-start
    .
A brand-new project with no QA — even on an old codebase — is always 
qa-start
, never 
qa-project-bootstrap
.
最常见的路由困惑，一次性解答：
  • qa-start
     —— 在完全无QA基础的场景下搭建QA体系。适用于新项目，或QA工作被删除后需重启的情况。流程：上下文 → 策略 → 第一份计划。产出物是QA的基础体系。
  • qa-project-bootstrap
     —— 为加入已有测试体系团队的QA工程师提供30天快速上手方案。涵盖团队流程、入职时间表，以及对现有测试套件的审计。适用于已有QA基础的场景，而非创建基础。
  • qa-do
     —— 当没有明确匹配的技能时，作为最后的路由工具。如果你已确定项目无QA基础，请跳过它直接运行
    qa-start
    。
全新项目（即使是旧代码库）且无QA基础时，始终使用
qa-start
，而非
qa-project-bootstrap
。

Pin as a Manual Command

固定为手动命令

Re-run anytime from the Claude Code 
/skills
menu.
To pin this skill as a manual-only command, add 
disable-model-invocation: true
to the frontmatter, or set it via 
skillOverrides
in 
.claude/settings.local.json
.
Caveat: in some Claude Code builds 
disable-model-invocation: true
also suppresses the manual slash command (ref anthropics/claude-code#26251). If you still want to invoke 
/qa-start
by hand, set the 
skillOverrides
state to 
user-invocable-only
instead.
可随时从Claude Code的
/skills
菜单重新运行。
要将此技能固定为仅手动调用的命令，请在前置内容中添加
disable-model-invocation: true
，或在
.claude/settings.local.json
中通过
skillOverrides
进行设置。
注意：在部分Claude Code版本中，
disable-model-invocation: true
也会禁用手动斜杠命令（参考anthropics/claude-code#26251）。如果你仍想手动调用
/qa-start
，请将
skillOverrides
设置为
user-invocable-only
。

Related Skills

相关技能

  • qa-project-context — Step 1. Captures project setup, tech stack, and quality goals into 
    .agents/qa-project-context.md
    .
  • test-strategy — Step 2. Defines the testing approach, pyramid, tools, and quality gates.
  • test-planning — Step 3. Builds the first test plan with features mapped to test cases.
  • qa-project-bootstrap — go here instead when a QA engineer is ramping onto an existing team with existing tests; this skill creates the foundation, bootstrap onboards onto one.
  • qa-do — last-resort router when no skill clearly matches; not needed if you already know there is no QA.
  • playwright-automation / cypress-automation — after the plan, write the first E2E tests against your highest-risk flows.
  • qa-project-context —— 步骤1。将项目设置、技术栈和质量目标捕获到
    .agents/qa-project-context.md
    中。
  • test-strategy —— 步骤2。定义测试方法、测试金字塔、工具和质量门控。
  • test-planning —— 步骤3。制定第一份测试计划，将功能映射到测试用例。
  • qa-project-bootstrap —— 当QA工程师加入已有测试体系的团队时使用；本技能用于创建QA基础，而bootstrap用于快速融入现有体系。
  • qa-do —— 无明确匹配技能时的最后路由工具；若已确定无QA基础，则无需使用。
  • playwright-automation / cypress-automation —— 完成计划后，针对高风险流程编写首批E2E测试。