SharklyTasks

One Task holds the work,the conversation, and the run

A Task is the system of record. It belongs to an Organization and a Space, can sit in a Project or Sprint, and can be assigned to people and to an Agent or Crew.

Get startedSee the Task system
Sharkly board of Tasks assigned to people and Agents

Used by teams at

  • Amazon
  • Intuit
  • Markel
  • AT&T
  • Veeam
  • Maersk

Record, assign, review

Stop splitting the work across prompts

Private sessions lose context. A Task keeps the goal, the people responsible, the Agent that executed, and the comments that followed.

Write work that can be acted on

Title the outcome. Put scope, constraints, and acceptance in the description. Status, priority, dates, type, and fields travel with the Task.

Assign people and execution separately

Human assignees record responsibility. An Agent or Crew is the execution assignee. Both use the noun Assignee. Never Delegate.

Keep dialogue on the Task

Comments are the record for on-task discussion. Activity logs state changes. Agent traces stay linked from the comment that produced them.

Everything the Task carries

Ownership, conversation, grouping, and attention

The Task is not a ticket that Agents happen to mention. It is where assignment, conversation, Workflow, Projects, and execution meet.

01Task

Put the whole record on one item

A Task can include title, description, Space, type, status, priority, dates, people, execution assignee, Project, Sprint, labels, custom fields, comments, and history.

  • One Organization, one Space, one Space-owned task type
  • Optional Project and Sprint without leaving the Task
  • Execution state and result stay attached to the same item
Task detail with description, assignees, status, and history
02Assignees

People own it. Agents execute.

A Space can allow one person or several people as human assignees. The execution slot is an Agent or a Crew. Mixed lists still say Assignee.

  • Assign from the same control used across the product
  • Keep a person accountable while an Agent runs the work
  • Crew assignment coordinates several Agents on one Task
Task assignee control with people, Crews, and Agents
03Types

Give each type its fields and Workflow

A Bug, a Feature, and a Request do not need the same form. Each Space-owned type binds custom fields and a bounded Workflow of statuses.

  • Exactly one active default type per Space
  • Statuses are selectable only when they belong to that type’s Workflow
  • Labels stay lightweight; types carry the process difference
Space task types with bound statuses and fields
04Conversation

Talk to the Agent on the Task, then let it run

Conversation is how you work with an Agent without leaving the Task. Send a comment, start a run, and keep the reply, trace, and result on the same record.

  • Talk to the assigned Agent in Task Conversation, not a private chat
  • An eligible comment can start or continue a run
  • The Agent’s reply and execution stay attached to the Task
Talking with an Agent on a Task and starting a run
05Project

Group related Tasks around one outcome

A Project is the larger goal. Tasks stay the place where people, Agents, comments, and runs live. The Project gives those Tasks a shared outcome, owner, and progress.

  • A Task belongs to one Project or none, and still belongs to one Space
  • Projects can include work from more than one Space
  • Keep ownership and status on the Tasks, not on a separate tracker
Project grouping related Tasks around one outcome
06Inbox

See the Tasks that need your attention

Inbox is a personal queue of Task activity, grouped by Task. It is not a second tracker and not the Space Triage queue. Open a row to open the Task.

  • Primary, Other, Later, and Cleared keep attention separate from the board
  • Snooze or clear a row without changing the underlying Task
  • Triage Notify still lands as an Inbox item for the people responsible
Inbox grouped by Task across Primary, Other, Later, and Cleared

The Task system

The primitives a work item actually needs

If a field, a comment, or a run cannot attach to the Task, it is not part of the work system yet.

Task

The unit of work: goal, type, status, people, execution assignee, and history.

Assignee

People for responsibility, Agent or Crew for execution. One noun for every handler type.

Task type & Workflow

Space-owned classification bound to custom fields and a bounded set of statuses.

Conversation

On-task dialogue with the assigned Agent. Eligible comments start or continue a run.

Project

Optional grouping for related Tasks around one outcome, owner, and progress.

Inbox

A personal queue of Task activity. Snooze or clear without changing the Task.

Bring the Task from where it started

Keep Jira, GitHub, or Slack. Make the Task executable.

Existing trackers can still create or sync work. Once it is a Task, people and Agents share the same record.

JiraGitHubSlack
See integrations

Connected features

A Task is the hub, not a silo

Plan, Triage, Agents, and Automations all write back to the same work item.

AgentsSaved Agents you assign like teammatesPlanBacklog, Sprints, Projects, and ViewsTriageIncoming work waits until someone decidesAutomationsRecurring Agent work without a pokeIntegrationsJira, GitHub, and Slack in the same system
DocsComing soonTeam knowledge Agents can use

Quality of life, built in

The details that keep a Task honest

Work only stays reviewable if the conversation and the run cannot leave the item.

Human assignees and an Agent or Crew on the same Task
Space-owned types with their own Workflow
Conversation that talks to the Agent and starts a run on the Task
Projects that group related Tasks around one outcome
Inbox grouped by Task, with snooze and clear
Follow a Task without becoming the assignee

Give every Agent run a Task to come home to

Write the outcome, assign people and an Agent, and keep the conversation on the same record.

Start with Sharkly

Start

Create a Task the team can actually run

Pick a Space, give the work a type, assign a person and an Agent, then keep review in comments.

01

Create the Task in a Space

Name the outcome, add enough context for a new person or Agent, and choose the type that owns the Workflow.

02

Assign people and execution

Put a person on the Task for responsibility. Assign an Agent or Crew when something should actually run.

03

Continue in comments

Ask follow-ups on the Task. Eligible comments continue the Agent. Results stay attached to the same item.

FAQ

Tasks, not another list next to the Agent

Can a Task have both a person and an Agent?

+

Yes. People are the human assignees. An Agent or Crew is the execution assignee. Responsibility and execution are both first-class, and both use the noun Assignee.

What belongs in a Task versus a comment?

+

Put the goal, scope, and acceptance criteria in the description. Use comments for decisions, follow-ups, and Agent dialogue as the work proceeds.

Is Inbox the same as Triage?

+

No. Triage is a Space intake queue for Accept, Decline, mark duplicate, or Snooze. Inbox is your personal queue of Task activity. Clearing Inbox does not change the Task.

Do Automations create a Task for every run?

+

No. Current Automations start an Agent or Crew run directly and keep history on the Automation. Use a Task when the request needs an owner, status, and review.

Where does Agent output go?

+

Onto the Task: comments, activity, and the execution trace. The team should not have to reconstruct what happened from a private session.

Can Tasks live outside a Space?

+

No. Every Task belongs to one Organization and one Space, and to one Space-owned task type. Sharkly does not use a separate personal inbox of unscoped work items.