Tactics
- Use a requirement-to-sentence audit.
- Test reason distinctness by naming one-word categories.
- Read requests aloud for unintended blame or weakness.
- Run global, sentence, then surface editing passes.
Pitfalls
- Assuming topic relevance equals task completion.
- Adding invented numbers to make a reason sound specific.
- Replacing accurate vocabulary with less natural complex wording.
Repair task drift and vague development
Actions
- Underline the sentence fulfilling each prompt point.
- Add user, mechanism, or consequence after vague claims.
- Compare paragraph functions for duplication.
Example
Lesson
Each required point becomes an observable part of the solution rather than a vague concern.
Context
A bike-room proposal asks for current impact, a notice process, and one prevention measure.