Workflows

Get oriented first

Agents work best when they look before they act: list_projects, then get_board for the project at hand. The board shows columns in order with their tasks, so the agent learns the team's flow (for example To do → In progress → Review → Done) before moving anything.

Keep the task as the source of truth

A task can carry the whole state of a piece of work, so that anyone — a person or another agent session — can resume it from its key alone:

• the description holds the goal and the design;
• the checklist holds the steps, ticked as they are done; a step that comes up on the way (a fix, a missing piece) goes in with add_checklist_item and position: "next", right after the last done step, and is shown as added live;
• comments hold the evidence: what was changed, test results, links;
• attachments hold files: logs, screenshots, reports.

Taskgert itself is built this way: every change is a task in the TSKGT project, worked through a fixed checklist (plan → API → MCP → tests → local end-to-end → release → deploy → verify) by an agent that comments after each step.

Example prompts

• "Triage the To do column of TGT: set a priority on every task that has none, and comment why."
• "Pick the most urgent task assigned to me in TGT, move it to In progress and outline a plan as a checklist."
• "Summarise what changed on the TGT board today, from the tasks' comments."
• "Attach the test report in ./report.md to TGT-42 and move it to Review."

Refine Ideas sent by Telegram

Ideas people send to the Taskgert Telegram bot are marked origin: TELEGRAM (a "Telegram" badge on the board). Their description is the person's raw words, or a voice-note transcript. To refine them:

1. Run list_tasks with type: IDEA and origin: TELEGRAM.
2. Read each one for its intent and contrast it with the code. get_task reminds you in next.
3. Write the goal, design and checklist.
4. Set the type to TASK. The person is then told on Telegram that their idea is now a task.

"Refine the Telegram ideas of TGT against the code" is enough of a prompt.

Work alongside people

Everything an agent does appears live on the board and is signed with the bot's name. Assign tasks to the bot ("me" in tools) to make its work visible, and use comments to hand over: people can answer in the same thread.

Avoid overwriting

update_task takes the version that get_task returned. Pass it when editing something a person may be editing too: if the task changed in between, the tool fails and the agent can read it again instead of overwriting.