Best Practices
How to author high-quality AEP packs.
Keep constraints specific
Use concrete rules that can be validated, not broad advice.
Prefer: "Do not modify routes outside /docs."
Avoid: "Be careful with routes."
Avoid overfitting
Do not encode temporary quirks as permanent defaults.
Capture failures
When tasks fail, update failure_traps so the same mistake is less likely.
Failure data is often more valuable than success summaries.
Keep workflows minimal
Use the fewest steps that still produce consistent outcomes.
Validate every pack
Ensure success_checks are objective and executable.
Review cadence
- task-level packs: after each completion
- project-level packs: weekly or bi-weekly
- team-level packs: monthly or quarterly
Last updated on