Sometimes a task is too ambitious for the current phase, or too simple and needs more depth. The scope-up and scope-down commands let you adjust task complexity without starting from scratch.
When a task is too complex for the current milestone, scope it down to focus on the essentials:
# Simplify task 5 — focus on core functionality
tm scope-down --id=5
# Light simplification
tm scope-down --id=5 --strength=light
# Aggressive simplification
tm scope-down --id=5 --strength=heavy
# Scope down multiple tasks at once
tm scope-down --id=10,11,12
Scoping down preserves the original intent while removing non-essential requirements. The AI considers what can be deferred to a future iteration.
When a task needs more depth or additional requirements:
# Add more detail and requirements to task 5
tm scope-up --id=5
# Light enhancement
tm scope-up --id=5 --strength=light
# Significant enhancement
tm scope-up --id=5 --strength=heavy
Scoping up adds implementation detail, edge cases, validation requirements, or related functionality that strengthens the task.
| Level | Effect |
|---|---|
light |
Minor adjustments — trim or add small details |
regular |
Moderate changes — meaningful scope changes (default) |
heavy |
Major changes — significantly simplify or expand the task |
Guide the AI on exactly how to adjust scope:
# Scope down with specific direction
tm scope-down --id=5 --prompt="Remove OAuth integration, use simple API key auth instead"
# Scope up with specific requirements
tm scope-up --id=5 --prompt="Add rate limiting and request validation"