Tasuku
Workflows

Issue planning

Start an issue investigation, publish a plan, and approve implementation.

Issue planning gives the agent permission to investigate and propose work, not permission to change the repository.

Discover the command handle

Tasuku derives its bot handle from the configured GitHub App slug. If the App slug is acme-reviewer, the handle is @acme-reviewer.

Do not assume @tasuku. The current handle is visible through the GitHub configuration and on the App's GitHub profile.

Start a plan

Use either supported trigger:

  1. Assign the issue to the GitHub App bot when GitHub exposes the bot as an assignee.
  2. Add the tasuku:plan label as the fallback trigger.

Tasuku acknowledges accepted commands with an eyes reaction, persists a workflow, checks out repository context, and asks the configured agent for a structured plan.

What the plan contains

The plan is retained as a workflow artifact and published to the issue through the trusted worker. Tasuku resolves later approval to the latest applicable plan for the same repository and issue.

The plan may use:

  • the primary repository at a specific commit;
  • manually approved repository context;
  • configured read-only secondary repositories;
  • custom instructions, skills, and remote HTTPS MCP servers.

Repository context suggestions do not activate automatically and still require administrator approval. Learnings are different: an explicit durable preference in a trusted Tasuku-owned GitHub review thread is enabled immediately and can later be disabled from the dashboard.

Cancel, supersede, or retry

A new planning trigger can create a new run and plan. Approval must resolve to the current applicable plan for the same repository and issue. If the planning run fails, inspect its workflow and task attempts; retry only after addressing a configuration or transient provider failure.

Cancellation stops pending work when the workflow state still permits cancellation. It does not remove already published GitHub comments or undo completed external effects.

Approve the next step

Reply on the issue with:

@<app-handle> implement

If no current plan is available, Tasuku does not start implementation. See Approved implementation.

On this page