Team Task Tracker

Your agent manages tasks in a Google Sheet your team owns, with stage gates, blocker rules and confirmation before any delete. The backend is included.

Used by our operations team

What It Does

Gives your agent a shared task tracker. It can create, update, query, advance, block, close and delete tasks, one sheet tab per team. It checks every write against your lists of teams, stages, statuses and priorities. It applies two rules: a Done task needs evidence, and a Blocked task needs a reason.

The skill includes the backend: a small Google Apps Script web app that stores tasks in a Google Sheet you own. Nothing runs anywhere else.

This is the base skill. sprint-ops, reporting-ops and cross-team-ops all require it.

Who Uses It

Any team that wants one shared list of work, kept by an agent. Team leads use it to see what is moving, and owners use it to update their own tasks in plain language.

Setup

1. Copy the skill/ folder into your agent's skills folder as task-ops, for example .claude/skills/task-ops/. Or fetch it through the Thinqmesh MCP server.
2. Follow backend/SETUP.md inside the skill. In short: create a Google Sheet, paste in Code.gs and Setup.gs, run initializeWorkbook, set an API_KEY Script Property, and deploy as a web app.
3. Set two environment variables in the shell your agent uses: TASK_OPS_URL (the web app URL) and TASK_OPS_KEY (your key). The skill needs curl, which is included on macOS, Linux and current Windows. Do not write either value into a file.
4. Edit references/team-config.md to list your own teams, stages, capacity and escalation contact. Keep the lists identical to the top of Code.gs. The defaults are a generic example.

About the key. The key is sent in the body of a POST request, not in the URL, so it does not appear in URL logs. It is still a secret. If it may have leaked, change the API_KEY Script Property and update TASK_OPS_KEY. The old key stops working at once.

Deleting a task needs your explicit yes each time, and the backend refuses a delete without a confirm flag.

Example Result

Request: "Block task 12 on Engineering. We are waiting on the payment sandbox keys from Operations."

Task Engineering #12: Build checkout flow
  status   In Progress -> Blocked
  notes    + Blocked 2026-03-02: waiting on payment sandbox keys from Operations
Updated. Priority is P1, so it is worth raising with the Operations lead
within the day. Want a short message drafted?

How to Adapt

• Change teams, stages, statuses and priorities in references/team-config.md and in the block at the top of backend/Code.gs. Then update the gates in references/status-playbook.md.
• Add a column by adding it to COLUMNS in Code.gs and handling it in the create and update functions.
• Change the escalation contact and the stale and stuck thresholds in references/team-config.md.