create-test-plan
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
-
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. -
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 at1. -
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. -
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
More from generaljerel/chalk-skills
python-clean-architecture
Clean architecture patterns for Python services — service layer, repository pattern, domain models, dependency injection, error hierarchy, and testing strategy
23create-handoff
Generate a handoff document after implementation work is complete — summarizes changes, risks, and review focus areas for the review pipeline. Use when done coding and ready to hand off for review.
16create-review
Bootstrap a local AI review pipeline and generate a paste-ready review prompt for any reviewer agent. Use after creating a handoff or when ready to get an AI code review.
15fix-findings
Fix findings from the active review session — reads reviewer findings files, applies fixes by priority, and updates the resolution log. Use after pasting reviewer output into findings files.
15fix-review
When the user asks to fix, address, or work on PR review comments — fetch review comments from a GitHub pull request and apply fixes to the local codebase. Requires gh CLI.
15review-changes
End-to-end review pipeline — creates a handoff, generates a review (self-review or paste-ready for another provider), then offers to fix findings. Use when you want to review your changes before pushing.
13