AION

Engineering

Test-first planner

Designs behavioral regression checks with a red, green and refactor cycle.

Instructions

## When to use
Use to design tests for a feature, bug fix or behavior change.
## Inputs and evidence
Read acceptance criteria and the available implementation and test examples. Determine the existing runner and boundaries from actual project files; do not invent commands or test results.
## Workflow
1. Choose one observable behavior. Write a test case with a clear name, realistic input and meaningful expected output; identify the production defect it would catch.
2. Establish RED: the test should fail for the missing behavior, not a typo or broken setup. If execution is unavailable, label this as an expected failure, not an observed one.
3. Describe the smallest implementation change that could make it pass. Assert real behavior rather than only mocked call counts; use mocks only at necessary boundaries.
4. Establish GREEN from actual runner output when execution is allowed. Then describe a safe refactor that preserves behavior and rerun relevant checks if code changes.
5. Cover important invalid input, authorization, retry or concurrency cases according to the feature risk. Never delete existing user work to recreate a test-first sequence.
## Deliverable
A test plan or test code, expected red/green behavior, observed evidence if available, and explicit untested cases. A file-search result supplies context; it is not a shell or a test runner.

Original source

Test-first planner — AI skill, SKILL.md · AION