Use tzTrack #

View this page as Markdown

Work with your AI as usual. Once connected, tzTrack supplies instructions to read open issues at the start, record work that needs to survive the conversation, and update issues as work progresses. These prompts help you choose the project and focus; you do not need a separate reminder for every update.

Start or resume work #

Use tzTrack for this project. Read the open issues before we start, record new findings as we work, and tell me what needs my attention.

Pick up where we left off. Read the project's tzTrack space and tell me what is finished, what is still open, and what you can work on next.

Use the same space in each conversation. If you work in a project folder, you can save its space in a setting file. In a chat, name the space when needed. Connecting another AI tool does not copy your chat history; it gives that tool access to the recorded issues.

Coding #

Keep bugs, missing behavior, review findings, and follow-up work visible across coding sessions.

Review this change. Fix issues within the agreed scope, and record the remaining bugs, gaps, and follow-up tasks in tzTrack with evidence and a suggested next step. Search first so you do not duplicate an existing issue.

Find the open bugs for authentication. Check which are already claimed, then take one available issue and investigate it. Record the fix and how you checked it.

Before we finish, record unfinished coding work and any questions that need my decision. Leave enough context for another session to continue.

The issue's kind says what it is; you can use ordinary words and let your AI choose:

Kind Example
bug Saving a valid form returns an error.
gap A required validation check is missing.
task Update the callers after an API change.
question Decide whether archived projects should remain searchable.
docs The setup guide gives an outdated command.
friction The workflow works but requires unnecessary steps.
idea Consider adding a bulk-edit feature.
praise The new error message makes recovery clear.

Track issues while you code gives the full workflow. tzTrack also works inside tzTeam, whose issue tool follows the project's requirements and verification practices.

Research and writing #

As we research this question, record conflicting evidence, sources still to check, and unanswered questions in tzTrack. Add new evidence to existing issues.

Review this draft. Track unsupported claims, unclear passages, and missing examples. Mark editorial choices that need me, and close each issue as we resolve it.

Customer work and planning #

Track the unanswered questions and promised follow-ups from these customer conversations. Record the work without personal details, and show what is waiting for a reply.

Keep the outstanding tasks and decisions for this launch in tzTrack. Show what can move forward now and what needs my approval.

Several sessions or agents #

Read the shared space before starting. Claim an available issue, leave work claimed by another session alone, and return anything you cannot finish with a clear handoff.

Check progress #

What remains open, what is waiting for me, and what did we resolve?

Show the tzTrack issues you updated in this session, with their numbers and current status.

Your AI makes the updates; tzTrack keeps the shared record. The instructions guide the connected AI's behavior, so how reliably they are followed depends on the AI tool. tzTrack does not run an AI in the background or save every conversation.