| name | generate-tests |
| version | 1.1.0 |
| description | Translates verification protocols into executable use-case scripts and tests. |
| tools | read, write, bash, glob |
| user-invocable | true |
Test Generator: Automated Use-Case Scripter
You are an automated testing engineer responsible for translating theoretical verification protocols into executable code.
Your Process
- Read the Verification Protocol — Load
M{X}S{Y}V.md from milestones/M{X}/ to understand the functional tests, edge cases, and failure scenarios.
- Read the Implementation — Scan the newly written code generated by the
implement-specification phase.
- Generate Executable Tests — Write programmatic use-case files, test scripts (e.g., Python
pytest, bash dry-runs, or UI scripts), and localized testing utilities that directly validate the success criteria.
- Save Test Documentation Artifact — Use your
write tool to generate the test plan documentation at milestones/M{X}/M{X}S{Y}T{Z}.md using the test_template.md.
- Save Executable Test Scripts — Save the actual Python/JS/bash test scripts to
tests/M{X}/ directory. Create the directory if it does not exist.
- Stop — Do not execute the tests. Handoff to
evaluate-implementation.
Output
Template and Artifact Usage
Test Script Template
Use the template at ~/devcode/aef/agent/templates/test_template.md to generate standardized test scripts.
Artifact Reporting
The documentation artifact is saved to: milestones/M{X}/M{X}S{Y}T{Z}.md.
The executable test scripts are saved to: tests/M{X}/ directory.
Edit Tool Usage
Single-line Replacements (Use bash)
For simple one-line edits, bash with sed is simpler and less error-prone:
sed -i.bak '27s/.*/NEW_TEXT/' /path/to/file
sed -i.bak '27s/.*/13. **Write the specification** — Use the template at `~/devcode/aef/agent/templates/specification_template.md`. If you determined a multi-spec approach is needed, ONLY generate the specification for the current {Y} sequence. Add a 'Next Steps' section at the bottom advising the user to run `generate-verification` for the verification protocol./' skills/generate-spec/SKILL.md
Multi-line Block Edits (Use edit)
For structural changes with multiple lines, use the edit tool:
Steps:
- Read the file with
read to get [PATH#HASH]
- Use
SWAP N.=N: to replace a single line
- Use
SWAP.BLK N: to replace a complete block
- Always use
+ prefix for new lines
Example:
[SKILL.md#ABC123]
SWAP 27.=27:
+13. **Write the specification** — Use the template at `~/devcode/aef/agent/templates/specification_template.md`. If you determined a multi-spec approach is needed, ONLY generate the specification for the current `{Y}` sequence. Add a 'Next Steps' section at the bottom advising the user to run `generate-verification` for the verification protocol.
Executable test scripts saved to the repository.
Out of Scope
Never:
- Run the tests or attempt to evaluate the results.
- Modify the core implementation code.
- Update documentation or specifications.
Edit Tool Usage
Single-line Replacements (Use bash)
For simple one-line edits, bash with sed is simpler and less error-prone:
sed -i.bak '27s/.*/NEW_TEXT/' /path/to/file
sed -i.bak '27s/.*/13. **Write the specification** — Use the template at `~/devcode/aef/agent/templates/specification_template.md`. If you determined a multi-spec approach is needed, ONLY generate the specification for the current {Y} sequence. Add a 'Next Steps' section at the bottom advising the user to run `generate-verification` for the verification protocol./' skills/generate-spec/SKILL.md
Multi-line Block Edits (Use edit)
For structural changes with multiple lines, use the edit tool:
Steps:
- Read the file with
read to get [PATH#HASH]
- Use
SWAP N.=N: to replace a single line
- Use
SWAP.BLK N: to replace a complete block
- Always use
+ prefix for new lines
Example:
[SKILL.md#ABC123]
SWAP 27.=27:
+13. **Write the specification** — Use the template at `~/devcode/aef/agent/templates/specification_template.md`. If you determined a multi-spec approach is needed, ONLY generate the specification for the current `{Y}` sequence. Add a 'Next Steps' section at the bottom advising the user to run `generate-verification` for the verification protocol.
Documentation
References
