Work items and channels

A work item is Tasuku's durable record for an engineering request. It keeps the request, source conversation, ticket, selected GitHub repository, plans, artifacts, agent tasks, and delivery links under one identifier.

Where work starts

Tasuku currently receives work from three channels:

• GitHub supplies pull requests, issues, review comments, repository content, and the identity used for trusted code publication.
• Slack supplies mentioned questions, research requests, implementation requests, plan decisions, recurring schedules, and thread delivery.
• Linear supplies ticket events and plan decisions. Linear is a ticket source; the code target remains an explicitly selected GitHub repository.

The channel records where a request came from. It does not give an agent credentials or permission to publish.

Slack thread lifecycle

Mention Tasuku in a channel the bot has joined. A question starts independent work. Research and implementation can continue in the same thread while their work item remains active. Questions, research, builds, and plan decisions all require a Slack identity linked to an active Tasuku member with the agent-operation capability (ADMIN or SUPER_USER).

An implementation request creates or binds the configured GitHub or Linear ticket, selects an eligible GitHub repository, and produces a plan. The work item lifecycle is OPEN, RUNNING, WAITING, COMPLETED, FAILED, or CANCELLED. Tasuku waits in WAITING with reason APPROVAL until an authorized user approves, revises, or declines that plan. Approval applies to the plan on the bound work item; it is not a general permission for later changes.

If repository or ticket context is ambiguous, Tasuku waits with reason CONTEXT and asks for the missing choice instead of allowing the agent to infer an authorization boundary.

A channel can opt into passive listening so non-mention messages in threads Tasuku already owns are routed too. Passive messages can receive a scoped conversational contribution but never start builds, research, or plan decisions.

Linear tickets and GitHub code

Administrators map each connected Linear team to eligible GitHub repositories and may choose a default. When several repositories are eligible and none is the default, the work item waits for an explicit repository selection.

Operate from Linear with comment commands: /tasuku plan, /tasuku approve, /tasuku revise, and /tasuku cancel. Adding the tasuku:plan label also starts planning.

Tasuku publishes plans and delivery results as Linear comments and attaches the resulting GitHub pull request. It does not change the Linear issue's workflow state.

Inspect and operate

Open Work items in the dashboard to see the current state, resources, artifacts, plan history, and related agent tasks. The same durable state backs GitHub, Slack, Linear, and dashboard actions, so a retry or workflow resume does not create a separate conversation.

In Slack, a linked administrator can ask Tasuku for the status of work in the current thread or name another work item by ID, title, requester, repository, or subject. Tasuku searches only that administrator's organization and reports the persisted lifecycle, phase, waiting or failure reason, and last update. When several work items match, Tasuku offers up to three choices instead of guessing. Status lookup is read-only and does not create another work item or workflow run. Models without function-calling support retain exact-ID and current-thread status lookup.

See Recurring workflows for scheduled work and Architecture for the credential and publication boundaries.