claude-tag.md

Claude Tag (beta) — taskplane in your Slack channels

How taskplane runs governed work inside Claude Tag, Slack's shared @Claude identity — what changes in that environment and what stays enforced.

Claude Tag runs @Claude as your organization's shared identity in Slack (Team/Enterprise, public beta). taskplane adapts to that environment with three mechanisms:

• Repo-persisted store. Tag's sandbox is ephemeral — ~ is discarded when the conversation idles. Set TASKPLANE_STORE=repo and the knowledge store (decisions, requirements, loop state) lives at .taskplane-kb/ inside the repo, committed and pushed with the work. The next Tag session resumes the loop by cloning the branch.
• Attributable human gates. There is no PreToolUse hook layer in Tag, so gates are process + audit: at plan_approval and signoff the loop parks, the gate summary goes to the thread, and only a real person's reply unlocks it — recorded with tp loop approve --by "Dana — 'approved' in #platform-eng". The approver lands in the trace and the KB, so every gate pass is attributable. An approve without --by is detectable as a self-approval.
• The tp-tag skill carries the full thread protocol: compact status posts, the dashboard attached at every gate, scope restated before each execute step, and a hard rule the skill never breaks — it does not approve gates on its own, under any phrasing of urgency.

The approved flow contract is stored with the skill at skills/tp-tag/flow.json:

Slack thread goal → repo-persisted KB → governed loop → role dispatch + evidence → dashboard attached → human reply in thread → attributed approval → commit KB + resume state.

The dashboard is the engine-authored .taskplane/dashboard.html; it shows the workflow/gate state and dependency graph/blast radius. Tag attaches those bytes by reference at a human gate and waits. A request for changes leaves the loop parked; only an explicit approving reply advances it, with the person's identity and exact words recorded through --by.

To deploy: an Owner attaches the taskplane plugin to a scope (channel, workspace, or org) from the Access bundle's Plugins tab or a skills repository — see Customize Claude Tag. Honest limit: Tag's plugin surface today is skills-only, so enforcement is by process, visibility, and trace — not by mechanical interception. The hook layer remains fully active in Claude Code and Cowork. Individuals can work privately even on a team plan and publish selected decisions to the channel's shared store with tp share push — see the changelog's v1.5.0 entry.