First task
A useful task describes an observable outcome, the important constraints, and the evidence that should make the change reviewable.
01
Write for an outcome
Describe the behavior that should change instead of prescribing an implementation before the repository has been inspected.
- Name the user-visible or test-visible result
- Call out files or systems that must not change
- Request the narrowest useful verification command
02
Use plan mode first
Plan mode is a low-risk way to check whether BuildStax found the right code and understands the task boundaries.
Command
buildstax --permission-mode plan --provider anthropic --model <model-name> "Plan a fix for duplicate form submissions. Do not edit files."03
Review the artifact
After an edit, review the diff, the commands that ran, and any remaining uncertainty. Treat the result like a teammate's pull request, not an answer that bypasses review.