qa-start

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.

Quick Route

Pick your entry point — skip any step whose artifact already exists.