Documentation
Common Workflows
Tips for using Terragon effectively
Where Terragon works best
Here are a few examples of scenarios and tasks that Terragon excels at:
- Use voice to describe tasks for Terragon while on your commute, then pick up where it left off when you're back at your desk
- Delegate small or medium tasks from your task list so you can focus on higher-priority work
- Give Terragon backlog tasks that are hard to prioritize relative to other work
- Tag @terragon on GitHub issues to assign larger, well-scoped work to Terragon
- Terragon works well for exploring or prototyping ambiguous solutions iteratively. Give an ambiguous prompt to see how it approaches the problem, then use the Retry feature to refine the task
- If you know how to do a task but want to delegate it, describe the task to Terragon as if you were instructing another engineer
- Tasks that replicate existing patterns in your codebase work well. If you have an existing feature to replicate or adapt, send that task to Terragon
- Give Terragon tasks that can be verified with high confidence (e.g., if CI passes)
- If the task seems too large for one person, it may be too large for Terragon. Consider breaking it into smaller tasks, or asking Terragon to plan its own work first