How to use the Definition of Done Generator.
A definition of done applies consistently to a class of work. Keep story-specific acceptance conditions separate from shared delivery standards.
Make the workflow fit your task.
Identify the shared quality and delivery conditions that apply to a class of work. Make each check observable and separate it from a story's unique acceptance behavior so the standard can be applied consistently.
- What you provide
- Team process and delivery standards.
- What you get
- Shared completion criteria for a work category.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Team ships small changes to a web form.
Completed example
Shared completion criteria might include review, relevant tests, accessible interaction checks and updated guidance when behavior changes.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Should the definition of done include every acceptance criterion?
Keep shared completion standards separate from story-specific behavior. Both matter, but they answer different review questions.
Why is work marked done while necessary release checks remain unfinished?
Clarify which delivery stage the definition covers and include the checks required for that stage. Avoid an ambiguous completion label.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑