Generate readable testing notes after a feature is complete. Compares spec against implementation to produce a concise list of what was built, how to test it, and any scope gaps. Writes testing-notes.md to .aw/greenfield-progress/. Part of the gf (greenfield) skill family.
Generate concise testing notes for the completed feature.
The audience is a person who needs to test this. They are busy. Every sentence should help them test or understand a decision — nothing else.
Read these sources (skip any that don't exist):
.aw/greenfield-progress/spec.xml — what was planned.aw/greenfield-progress/tasks.json — what tasks were defined.aw/greenfield-progress/progress.txt — decisions made along the waygit log --oneline — what was committedBuild testing notes. From the gathered context, produce a complete document covering:
Format:
# Testing Notes: [Feature Title]
## Setup
[How to get the project running — install, build, start commands]
## What to Test
1. [Feature or area]
a. [Specific testable behavior]
b. [Another behavior]
2. [Another feature or edge case]
## Scope Notes
[Anything intentionally not implemented, with reasons]
Write the digest immediately. Use the /create-digest skill to write the testing notes to .aw/digests/testing-digest.md. Also write to .aw/greenfield-progress/testing-notes.md.
No .draft file. No review loop. This is a final wrap-up step — produce the artifact in one pass.
Confirm: "Testing notes saved to .aw/greenfield-progress/testing-notes.md and .aw/digests/testing-digest.md"