Create Test Plan

Overview

Create a structured test plan using the test pyramid (Mike Cohn), boundary value analysis, and risk-based testing. Every test case traces back to an acceptance criterion, covers the right level of the pyramid, and explicitly addresses edge cases and error states.

Workflow

1. Read project context -- Read .chalk/docs/ for PRDs, user stories, acceptance criteria, and architecture docs. Read existing test plans to understand conventions and coverage gaps.

2. Determine the next test plan number -- List files in .chalk/docs/engineering/ matching the pattern *_test_plan_*.md. Find the highest number and increment by 1. If none exist, start at 1.

3. Identify acceptance criteria -- From $ARGUMENTS, conversation context, and project docs, extract every acceptance criterion or expected behavior. If no formal acceptance criteria exist, derive them from the feature description and confirm with the user.

4. Map criteria to test pyramid levels -- For each acceptance criterion, determine the appropriate test level:

   • Unit: Pure logic, calculations, data transformations, validation rules
   • Integration: Component interactions, API contracts, database queries, external service calls
   • E2E: Critical user journeys, cross-feature workflows, deployment verification