Tasks, Plans, And Review Flow

When To Use Tasks

Use tasks when work needs context beyond a single terminal prompt:

• A feature or bugfix that needs review.
• A Linear issue or team request.
• Work that may involve multiple agent sessions.
• Work that needs an implementation plan before coding.
• Work that should leave a useful record for teammates.

For quick local experiments, a plain terminal session may be enough.

Task Board Basics

The task board is the workspace surface for active product and engineering work. It can show tasks, labels, workflow state, assignees, and related details depending on the team configuration and integrations enabled.

Typical flow:

1. Open the tasks area in the workspace.
2. Create or select a task.
3. Add enough description for an agent or teammate to understand the intent.
4. Add labels or workflow state where useful.
5. Launch agent work from the task when you are ready.

Implementation Plans

Implementation plans capture intent before code changes. A useful plan should state:

• The goal.
• The files or subsystems likely involved.
• Key constraints.
• Expected tests or checks.
• Any out-of-scope work.

Plans are especially valuable when a teammate needs to review direction before an agent starts making changes.

Session Logs

Session logs connect terminal work back to the task. Use them to answer:

• Which agent worked on this?
• What prompt started the session?
• What did the agent do?
• What follow-up did the user give?
• What review context should a teammate see?

If a log looks incomplete, check whether the terminal session is still running or whether the work happened outside the selected task.

Launching Work From A Task

1. Select the task.
2. Choose the agent.
3. Choose the project path or worktree behavior.
4. Start the session.
5. Review the terminal output and resulting changes.
6. Update the task with the outcome, plan, or follow-up.

When launching multiple tasks, prefer isolated worktrees so sessions do not overwrite one another.

Reviewing Agent Work

Coldtea is designed to keep review close to the work:

• Use task details to understand intent.
• Use implementation plans to check proposed direction.
• Use session logs to see how the work unfolded.
• Use the editor to inspect changed files and annotations.
• Run the relevant test or lint command before considering the work done.

The review habit is simple: trust the workflow, verify the code.

Evolving Workflows

Coldtea will keep improving review and handoff workflows. Treat the visible app surfaces and your team's enabled features as the source of truth for what is available today.