Create a Task
Create a task with the right title, ownership, and optional planning context from the start.
Use the CLI create command when you want a terminal-first creation flow.
- Use the right creation surface.
- Fill required fields first.
- Attach optional planning and ownership fields correctly.
Where this happens
Same Task, Other Interfaces
Use the version that matches where you are working now. The subject matter stays the same; the delivery changes by surface.
Do the work
- 1. Run `./backlog.sh tasks create --title "Ship public docs" --team-id team_123` as the minimum command.
- 2. Add optional flags such as `--description`, `--project-id`, `--assignee-id`, `--priority`, `--status`, or repeated `--tag` flags as needed.
- 3. Read the JSON response and keep the task id if a follow-up status or field change is coming next.
- 4. If the CLI is automation-backed, set the linked visible agent first when attribution matters.
Keep Going in Task Workflows
Stay in the same interface and move to the next closest task in this topic when needed.
Browse Tasks
Open the main task surface, narrow the visible list, and move from the collection view into the next task action.
Change Task Status
Move a task through its status lifecycle without losing the activity trail that explains what changed and why.
Update Task Details
Change ownership, deadlines, labels, project links, description, or other mutable task fields without conflating that work with a status transition.
Nearby Guides
These guides stay close to the current workflow so you can keep moving without restarting discovery.
Change Task Status
Move a task through its status lifecycle without losing the activity trail that explains what changed and why.
Update Task Details
Change ownership, deadlines, labels, project links, description, or other mutable task fields without conflating that work with a status transition.